>At one installation of the application software, I am getting a Watcom 386 Read Error at startup. They are running Windows 95, the application is FPW 2.6A. This only occurs if several other applications have been opened. If the user reboots, the application starts normally.
>
>Thanks,
>
>Pete Berlowitz
This may be related to the known problem with FPW2.x and new fast (>=300MHz) machines. It is my guess that the CPUs are so fast now that they overwhelm the bus' capablities causing buffer overflows. Check out http://www.vss-inc.com/slowstart.html. This utility 'busies' the CPU for a determined period of time. FYI, I have also corrected a similar problem by inserting a =INKEY(3) immediately preceeding the line of code that generated an I/O error, and one of my clients says that they don't get the I/O errors if a user puts in a CD and has it playing in the background. In your case I might try putting an =INKEY(1) in a statement before I open a file.
HTH
//:^)