Nick,

The "Watcom Win32 Read Error" (assuming that's what you're getting) comes from apps that grab all the available memory and don't share. Once this happens, only powercycle will release the memory.For us the worst offender is Lotus Notes.

The work around is to open the FoxPro@x app first, and then the other stuff. Keep the Fox app open all day.

Welcome to the UT!



>Excuse me if I sound a little new to this ... but thats because I have only just signed up to universal thread. I am a network manager at a UK based production company which uses a product written by Pegasus in FoxPro 2.6. For a while now we have been seeing errors intermittently on most of our Windows98/95 PC's during normal operation. Sometimes the application displays a watcom error when loading the initial exe into memory, but mainly PC's can be thrown out of the application with a simple FOXPRO error. The PC's sometimes need to be rebooted and they can then continue normally.
>
>There are a significant number of FOXPRO errors when attempting to print suggesting a driver problem, but after a reboot this is fine and the same item can be printer without issue.
>
>Can anyone advise me how to look into this more deeply. I am convinced the network configuration is correct as our suppliers have been very helpful in checking the network for problems over the last 6 months and can come up with no problems at this level.
>
>Regards Nick