boy hope you registry jocks know how to backup stuff. think virus jocks are winning when i see you ready to rip stuff out without knowing what it is. tease - i know you are trying to find out!
since you did not mention your os, make wild guess the soula of justice running win2k.
i searched http://support.microsoft.com for windows 2000-developer (wild guessing) and keyword shim and found this i thought looked interesting..
i can't believe you rejected Joesph Moores fine information. i wrote it down myself.
Microsoft Knowledge Base Article - 324452
16-Bit Program May Stop Responding While Calling GlobalAlloc
View products that this article applies to.
This article was previously published under Q324452
)>
SYMPTOMS
If a 16-bit program calls GlobalAlloc, the program may stop responding, and you may receive the following error message:
Program Name caused a General Protection Fault in module KRNL386.EXE at 0001:6382
Choose close. Program Name will close.
NOTE: The hexadecimal address where the problem occurs is exactly 0001:6382.
CAUSE
This issue may occur because in Windows 2000 Service Pack 2 (SP2) and later, a program compatibility shim loads in the Ntvdm.exe address space to propagate environment variables. This behavior may affect a 16-bit program, which is sensitive to 16-bit memory allocations.
RESOLUTION
To work around this problem, delete the following registry key, and then restart the computer:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\AppCompatibility\ntvdm.exe
The 16-Bit Windows Programming guidelines recommend that GlobalAlloc be called only when it is necessary. These guidelines recommend that you use LocalAlloc instead.
STATUS
The information in this article applies to:
Microsoft Windows 2000 Server SP2
Microsoft Windows 2000 Advanced Server SP2
Microsoft Windows 2000 Professional SP2