>>>>I sent my application (written in 2.6 Windows) to
>>>>a client running Windows 95 on a Novell LAN. He
>>>>says he installed the app on the LAN using my setup
>>>>program but when he attempts to run it from a
>>>>workstation he gets a WATCOM ERROR #. The app runs
>>>>from his workstation but not from other users.
>>>>Anyone ever seen a Watcom error? I'm stumped.
>>>
>>>We are on a Novell network and we get the error:
>>>
>>>WATCOM 386
>>>
>>>READ ERROR
>>>
>>>I posted questions here a while back and the only response I recieved was it
>>>was a memory conflict and to try reducing the amount of memory needed in the
>>>config.fpw (MEMLIMIT). Since then I have observed our user activity when
>>>they experience the error and have found that Word Perfect was being run at
>>>the time or around the time they tried to fire off our application and received the
>>>error. The users have been instructed to restart their computer when the error
>>>occurs (they first try the win 95 shutdown of close all programs and log on as
>>>a different user, if that does not work then they try the good old restart).
>>>
>>>Hope this helps you, at least knowing that others are getting the same error. I hope
>>>someone does respond who has better luck that I have.
>>>
>>>Believe it our not users do not get that error all the time, it seems to attach itself for
>>>a while then go away.
>>>
>>>Bret
>>
>>
>>We have the same situation here, FoxPro and Novell, and every once in a while one of our user get this
>>same error when starting a FPW26 exe. They are running Win95. They try shutting down all other
>>applications but that doesn't help. If they restart Win95, that works but is not what they want to do.
>>
>>I don't think it has anything to do with other apps running at the same time. One thing I was going
>>to try was placing the FPW2600.ESL in the C:\WINDOWS directory. Right now, everybody here runs
>>the FPW exes amd esl from a network drive
>>
>>However, all my VFP3 apps run on their machines without a problem.
>>

Our computers are using Win 95 and Novell


>>Jerryt
>If you are still using Win3.1, one thing I would look at is to see if the user is using Smartdrive caching. If so, make sure that it is using at most 512k. I have had problems (confirmed by MS Techs) which were fixed when I modified the Smartdrive parameters.