>>>>The following error appears on occasion while starting up several Foxpro applications being run by my organisation - "Watcom win386 read error". I believe if the user re-boots, they can then get into the application. Not all users experience the error. Any help would be greatly appreciated.
>>>>
>>>Hi Sean,
>>>
>>>From what I understand, this is an issue with Novell 4.x. From what I've heard, this is supposed to be fixed in the next Novell release.
>>
>>It used to be that we passed the buck, now I think it is called passing the issue. I sure hope they fix this soon as I am getting really tired of closing all my open programs and restarting before I can do anything in 2.6 (we have quite a few existing apps in it). This is done to ensure that I dont get the error, because on my new Gateway that error locks my whole machine and the only recourse is a reboot. I am glad I do not get charged for scandisk.
>
>Careful Bret, you don't want to give anyone ideas < g >.
>
>As far as I'm concerned, Novell 4.x should be certified by the American Kennel Club. The Watcom error is one of a couple that I've run into. Another is a tendency to corrupt indexes. All of this didn't occur under 3.x. I also find it sluggish (on a 350 PII w/128 Mb), and overly agressive. It's also got the strange desire to want to map another drive to server I'm already connected to. grrr...
The AKC doesn't register mongrels...and my experiences with 4.11 parallel yours, unfortunately. Most of the problem I attribute to the Novell Client32 software; some problems (like those related to file compression) lie with the operating system itself, and some others relate to extended control packet formats used for the first time with 4.11. Since virually all of the problems go away if you use the MS Client rather than the Novell Client32, it seems to be survivable, but it's that much more push at my end to switch clients to an NT environment if they have to move off 3.12 (which, according to Novell, is not Y2K compliant without a whole load of patches that turn it into 3.20...)
