I have a client who is running OS2 warp version 3 clients, which connect to a Novell 4.12 SFT3 server (will all current patches). running over a Token Ring network.

The Arev database sits on the Novell server and uses the Novell netware driver.

The Novell server is accesed via the Novell Client for OS2

The Novell server was upgraded 2-3 months ago from Novell v4.10 and since then the system has become unstable.

I do not know if OS2 can have the "Source Route Cache" set, and the Client's IT department has been unable to find out about this at this time.

I have also tries running the Revelation NLM v1.5 to see if this will bring greater stability. but it just makes things worse.

The sort of problems that are occuring with the normaol netware driver are:-

1. Fatal read errors on any files, but when you try accessing them again, the problem does not exist.

2. GFE's

Problems with the NLM are as follows:-

1. The arev DOS session being dropped with no warning

2. DOS divide-by-zero errors and then the DOS session trys to unload the LHIPXTSR and freezes soild.

3. The OS2 version of General Protection faults.

Has anybody got any ideas on how I can make this system stable under this environment?

I have tried the Arev DOS 3.1 network drivers and this did not work at all.

Many Thanks

Ian Lord, Liss Systems.

Sounds like a caching and a time-out problem for part of it. Could just be bugs in the Novell client. Is there another version you can try?

[email protected]

Sprezzatura Group

View this thread on the forum...