>Does anyone know how to prevent Foxpro for DOS (FOXR.EXE) from running out of memory? The program being used is a large DOS app that it is not convenient to rewrite, so the DOS emulator in Windows XP would be ideal. The program will not run in Win 98/ XP or Me. Two things occur: 'Insufficient memory' and 'Not enough File Handles'. One message stated that there was not enough memory below 640K available. This is being run on a Novell network - perhaps memory is chewed up there. (All aspects of the program work fine under Win95 but the client does not want to keep using that platform and they have a new, faster computer anyway).

The odds are that the FILES= setting in 98's CONFIG.SYS or XP's CONFIG.NT for the DOS session needs to be set; the PerVMFiles= entry needs to be added to ME in order to increase the number of file handles available to the VDM session hosting the DOS app. As to the 'Out of Memory' condition under 98/ME, the odds are that, because of screen resolution, color depth and the number of icons on the desktop and fonts installed, you're exhausting the GDO resource heap, which is limited to a total of 64KB under all Win9x variant - NT variants, including XP, allow for 64KB per individual VDM (still an issue when running Win16 apps under a common VDM rather than in separate memory spaces.)

Depending on the version of FPDOS, you may also need to adjust the DOS session PIF to offer different forms of extended/enhanced memory to the VDM - FPDOS 2.5 and all FPDOS standard editions can only use EMS, and FPDOS 2.6 extended edition uses DPMI memory or XMS. In either case, no more than a total of 16MB of combined conventional memory and extended/enhanced memory should be given to the VDM, because the DOS Extenders in use get confused and wrap around memory addresses above the 16MB mark.