>>>I have a foxpro2.6a app running on a Novell version 4 server. The app ran fine until the users got new 333Mhz computers (Win 95 workstations), at which time they began to experience problems running the fox app. If they re-boot and go straight in, there is no problem, however if they go into other programs, after a while they try to go into the app, they will get a WATCOM Win386 read error. We have another app (same place and server) and when they got new P-166 to P-233, the same behavior occurs. I have heard this is a Novell problem, but then why did it run fine on the old P-75,90,100's and 486's? Of course it was also concurrent with upgrading to Win 95. So there are a lot of variables here. Please help!!! Need a solution, unhappy users!
>>Try using slowstart.exe. It should be in files section and at MS site.
>>Cetin
>FYI
>I patched a similar problem after a series of open file statements by inserting
>CLEAR TYPE
>=INKEY(3)
>before the line of code that generated the error.
>
>I think that the CPU I/O operations are so much faster than the bus can handle that the buffers are over-running. I put in the pause to let the system 'catch up' and it worked.
>HTH
>//:^)
This has nothing to do with the thread but whatever happened to Watcom and Borland compilers. I remember Watcom being the only non-Microsoft C++ compiler that supported MFC.

Mark A. Struck