>We're getting the above error at startup of an FPW 2.6 EXE. It's
>not 100% of the time. For example, if the EXE is put in the startup
>as the first program to load, there's no problem; anywhere else, no
>go.
>
>The NOS is Novell 4.11; the clients are either W95 or WFWG, all
>running Client32.
>
>Help, anyone?

I responded to this watcom 386 question awhile back with the following:

>>>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.

Our users have since learned that Word Perfect or any Word Perfect Product seems to
conflict with FoxPro. I dont know why, but when I investigate word perfect is always around
or has been used when the foxpro app is run and errors.