>I have had no success with this problem and appears to be fairly common. On machines (Pentium 100-200s) running Windows 95/NT and Novell 4.X, there appears to be a serious problem with memory management trying to run Foxpro 2.6 for Windows.
>
>If some applications are loaded before starting up Foxpro 2.6A for Windows, you will sometimes get a Watcom 386 Read Error. This will terminate the startup and even if you close the other applications you will still not be able to start Foxpro. The only way to recover is to reboot. If you start Foxpro first, you have no problem running these other applications.
>
>The only suggestion that seemed real was to rebuild the Foxuser.DBF and this did not work. This is occuring at more than one site and can be consistently reproduced.
>
>I have talked with Microsoft Fox Support extensively, checked Novell's Knowledge Base and run other queries. I have found other people reporting the problem but NO KNOWN SOLUTION.
>

The only thing I can think of that might help would be, under NT, to run FPW in a separate address space; by default, all Win16 apps under NT run in the same VDM, but this can be changed on an application by application basis. Isolating FPW in its own VDM might help since other apps wouldn't be visible to the FPW Win16 VDM and wouldn't interact with the Watcom memory manager.

Win95 does not offer this as an option.

If this only happens in a Novell 4.x environment and you're running the Novell Client32 or Client for IntraNetWare, I'd try using the Microsoft Client for NetWare instead; I've seen a number of problems with database apps (not this; I do not have any FPW apps still in use at this time) and NetWare 4.x with Novell's Client software. These problems, which manifest themselves in a number of different ways and are affected by several settings in the Novell Client and in the NetWare server configuration, do not appear with Microsoft's Client for NetWare and NDS Services.