>I have a new 1.2gig W2K Prof development machine. I support a bunch of FPD 2.5/2.6 apps that have been running for years on W95 & W98 boxes.
>
>After working with a FoxPro (DOS) application (in a development mode - no exe or runtine - just .prgs) for 5-30 minutes, the FPD window locks up tight. End Task is the only way out.
>
>I can also deliberately create the lock up in a fresh instance of FPD by running a large report and previewing it. The report preview works by writing the report to a disk file and then
>"modify command (ReptName) window Preview NoEdit"
>The report (disk) file is approx. 1.3 meg and the lockup will occur as I page up and down through the report. This has led me to believe the problem is memory related, but nothing I've tried with memory configuration (in config.fp and/or config.nt) seems to have any effect on the problem. The same test on W95 and W98 run as expected.
>
>Anyone have an idea how I can fix this problem(s) ?

First, make sure you're not being bitten by the problem described in one of Fred Taylor's messages:

http://www.levelextreme.com/wconnect/wc.dll?FournierTransformation~?2,15,527906

Second, in my experience FPDOS seems to get confused if it has a lot of RAM to work with. When FPDOS was developed 16 or 32MB of RAM was a lot. Who knows what it will do if it's offered 256 or 512MB?

Set up a shortcut to start FPDOS; on its Memory page leave Conventional memory at "Auto", set EMS and DPMI to 0, and limit XMS memory to 16MB. You could also try DPMI but no XMS.