I tried the imagecfg patch. That worked ok on a temp copy of NTVDM.EXE but I can not get it to stick in the c:\\windows\\system32 folder. I turned of System Restore in the My Computer / System Restore page and rebooted but it still will not let me copy the patched file in the c:\\windows\\system32 folder.
I have solved the sticking problem without having to turn off system restore. I updated the c:\\i386\\ntvdm.exe with the patched version first, then i was able to update the c:\\windows\\system32\\ntvdm.exe and the patch sticks. When I checked my program in the task manager it shows it running on only one cpu.Thanks again for your help,Kent
FoxPro 2.6 for DOS and FoxPro 2.6 for Windows are simple 16 bit applications.They should work on most Window XP platforms. FoxPro 2.6 for Windows might haveproblems sending raw output to the printer (See FPW:Printing to XP). On my last Windows upgrade, Ididn't use the installation disks. Instead, I simply copied my c:\\foxpro26 andc:\\foxprow foldersto my new WindowsMachine.FYI: With FoxPro 2.6 for Windows, you might have to copy your foxfontfiletothe windows system directory containing fonts.
A patched FoxPro 2.6a for Windows should be pretty stable, but can be a memory hog athigh resolution. If you're video resolution, for example, is at 800x600x16million colors,lower it 800x600x256color. See if that helps.If you are unable to run FoxPro for windows, due to insufficient memory, add a MEMLIMITstatement to your CONFIG.FPW file. The syntax for this statement is MEMLIMIT=%,min,maxwhere % is a calculated amount based on available memory and min and max representactualminimum and maximum allocations. For example, specifying MEMLIMIT=40,1024,4096allocates 40 percent of your system's available memory to FoxPro with a minimum allocationof 1024K and a maximum of 4096K.FYI: SYS(2019) tells you exactly where your CONFIG.FPW is located. And remember thatchanges to the CONFIG.FPW don't go into effect into the next time you launch FoxPro.If you still have problems, I suggest posting your problem to the MicrosoftFoxPro forum. 153554b96e