-
2
- #1
KevinIverson
Programmer
This problem has plagued me for some time and found that new dual processors /D models may be the clue. The challanges is the 2 processors appear to have problems with NTVDM.EXE. You can test for the problem using the following technique. Start your Foxpro compiled exe and use the CTRL+ALT+DEL to pull the task manager up and select NTVDM.EXE session you are running Right click and View the Affinity Setting on the session.
If the Affinity session does not appear this solution does not apply to this workstation. When checking the Affinity setting you will see 2 processors running. Remove the second CPU and save the session. This has prevented the lock up. To recreate the lock up I found you can pull up the foxpro session in a window and circle the mouse with a movable object like the command box for about 30 seconds. The challange appears to be something to do with a conflict bettween the processors sharing control.
The unfortunate problem is this does not save the changes to the session.
To fix this problem you must modify the NTVDM.EXE. To do this your are required to use IMAGECFG.EXE a utility that is availible on the internet
copy the imagecfg.exe into the C:\WINDOWS\SYSTEM32 directory
Step 1
Move into the
CD \WINDOWS\SYSTEM32
MD TEMP
MD SAVE
COPY NTVDM.EXE TEMP
* create a working temp dir
COPY NTVDM.EXE SAVE
* save the original ntvdm.exe
IMAGECFG -a 0X1 temp\ntvdm.exe
* modify the ntvdm in the temp dir
COPY TEMP\NTVDM.EXE
* copy the file to the system32 dir
COPY TEMP\NTVDM.EXE dllcache
* copy the file to the cache dir
NTVDM.EXE
* run the executable right away.
DIR NTVDM.EXE
* make sure the date has changed on the file.
The system will automatically recover this exe file when it notices a change to the file. If the process does not shut off the second process of the NTVDM it is because the system recovered the NTVDM from memory before you were able to run the NTVDM.EXE
If the Affinity session does not appear this solution does not apply to this workstation. When checking the Affinity setting you will see 2 processors running. Remove the second CPU and save the session. This has prevented the lock up. To recreate the lock up I found you can pull up the foxpro session in a window and circle the mouse with a movable object like the command box for about 30 seconds. The challange appears to be something to do with a conflict bettween the processors sharing control.
The unfortunate problem is this does not save the changes to the session.
To fix this problem you must modify the NTVDM.EXE. To do this your are required to use IMAGECFG.EXE a utility that is availible on the internet
copy the imagecfg.exe into the C:\WINDOWS\SYSTEM32 directory
Step 1
Move into the
CD \WINDOWS\SYSTEM32
MD TEMP
MD SAVE
COPY NTVDM.EXE TEMP
* create a working temp dir
COPY NTVDM.EXE SAVE
* save the original ntvdm.exe
IMAGECFG -a 0X1 temp\ntvdm.exe
* modify the ntvdm in the temp dir
COPY TEMP\NTVDM.EXE
* copy the file to the system32 dir
COPY TEMP\NTVDM.EXE dllcache
* copy the file to the cache dir
NTVDM.EXE
* run the executable right away.
DIR NTVDM.EXE
* make sure the date has changed on the file.
The system will automatically recover this exe file when it notices a change to the file. If the process does not shut off the second process of the NTVDM it is because the system recovered the NTVDM from memory before you were able to run the NTVDM.EXE
