>>We have a client that wants to upgrade his PC's from Win 3.1 on a Netware network to Win NT Workstation peer-to-peer network. He is running SBT Pro 3.0 right now, which is a Foxw 2.6 application, but the network is unstable and must be replaced soon. He can only afford a hardware upgrade right now, and the upgrade to VFP will come later.
>>
>>My question is, has anyone run a heavy Foxprow 2.6 application on a Windows NT machine reliably?
>
>The only problem that we have had is the known problem that FPW 2.6 will not run on faster Pent PC's. Faster being 300 up MHz. That is a patch that has worked very well for us. You can find it at http://www.abri.com/foxpro.html under FPW fast CPU Fix. You may also find that print preview's look like crap. The only work around that we have found is
>1. Dont do previews
>2. Do two forms one with bigger fonts for previews.
>
>Some one else may have had other problems, but this is all we have had.
>
>HTH
>Jeff

Depends on what you mean by "heavy". :)

I've run one FPW2.6 app on an NT 4.0 (SP3) workstation without much trouble. The only problem I ran into is that it used the old IsDiskIn.bin file to check for a floppy disk in drive A:, which doesn't work on an NT 4.0 workstation. I had to rewrite the function which checked for a floppy disk. (And also make the Y2K mods for which I was there in the first place.) Then it worked.

By the way, that's a short statement for a long process. It took me some effort to figure out how to reliably check for the disk on NT workstation. I started from KB article Q125372, but the code used in that article relied on the existence of a "NUL" file on a formatted floppy, which doesn't necessarily exist any more (I formatted a floppy in Win 3.1, Win95 and NT, and in none of these cases did it put the NUL file there). But I figured out how to rewrite the code from the article. I was thinking of sending my solution to FoxTalk and/or Advisor...

Of course you may have no use for that information. I'm just telling you that's the only snag I ran into which had to do with moving the FPW2.6 app from a Windows 3.1 computer to NT 4.0 workstation.

HTH,
Rich.