Update-
We were never able to completely fix our NT systems. Two seeminglyt identical machines, same software, same service packs - one runs Windows 3 apps, the other doesn't. There was only one FPW2.6 app left that I support, and this problem let me push it up to VFP a year early.
This problem still effects us whenever we run WIN16 apps or WIN32 apps with 16 bit headers (Like OutLook, and many installation programs). We have had some luck with reformatting and reinstalling Windows NT and its service packs, but it is not a 100% solution.

Good luck,
David.


>
>More ideas Paul,
>
>[FoxPro Windows 2.6] Re: Can't run FPW under NT Thread #305206 Message #306794
>From 12/21/1999 13:01:38
>David Fluker To Adam Davis
>
>>What Version of NT ?? What Service Pack?
>Adam,
>
>Synopsis:
>Problem - NTVDM hangs up running 16 bit apps
>OS - NT 4.0 Build 1381: Service Pack 5
>NetWare - don't know which version, but it is very recent
>
>The problem started after installing NT Service Pack 5 and updated NetWare drivers. I tried uninstalling them, but it had no effect. I had to set up a computer without SP5 for FPW development. Computers that haven't been upgraded run fime. I've not tried NT Service Pack 6, so I don't know if that changes anything.
>
>It's not just FPW, but any Win 3 app, indeed any 16 bit code. Though we don't often run Win 3 apps, it is surprising how many new 32 bit apps still run 16 bit code! FoxPro 2.6 for DOS runs, but sluggishly.
>
>When the app doesn't run, you will find the NTVDM process is running, taking all the processor time it can. On some of our computers computers you see the app start, some don't get that far, some pause then the app runs.
>
>If I try to start FPW multiple times I can bring Windows NT to its knees. 3 or 4 instances of NTVDM fighting for all of the processor time will crash the NT.
>
>David.