>>>>>>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...
>>>>
>>>>Could this all stem from a working relationship between Novell and Microsoft that is not exactly above board. Here you have an MS competitor that is trying to create something that if it worked wells as a network server would replace MS NT server or at least take market share. I wonder what programming would be like in an environment like that.
>>>
>>>Given the problems we currently have, I'm not so sure that I'd want to find out.
>>>
>>>As an aside, have you tried going to MS Client for Netware as Ed has suggested? I'm trying that now.
>>
>>I do use MS Client for Netware and I still am getting locked up, I got rid of my client32 when I got the new machine.
>
>Does the NW 4.11 server you work with use -any- compressed volumes? That's been a major problem that Novell admits to, and that isn't fixed by using the MS Client - the problems lie in resolving file addresses in files on compressed volumes - sometimes the cache seems to 'forget' or miscompute the file offsets, even with read-only files. We spent a good amount of time tracking down exactly this problem involving some large read-only files that were reporting file corruption errors (these files were being accessed from a COM object written in VC++) which would mysteriously vanish if the files were recopied to the server, or if the server were shut down and restarted. The files were never actually corrupted, but the server cache references were completely farkled...

I will check that out with our Network Staff, but I need to get my vacinations before I can go talk to them :)