Harry,

This sounds like the WATCOM WIN 386 Read Error, except that you don't get that message.

The WATCOM error happens when the users have opened some memory hog first and the memory is not freed up properly afterwards.

I tell my users to open the Fox app first and keep it open all day, then everything runs fine.

You may never find out what your real problem is, but this approach may help avoid it.


>During a busy day, and after launching and closing many apps, I go to launch FPW 2.6 and my system freezes. It's the ONLY program I have that does that???? One of my associates has the very same problem. Has anyone else experienced that? Are there any known fixes?
>Thanks
>Harry Marks