Fatal Errors on 32-bit clients (AREV Specific)
At 27 AUG 1998 03:47:58PM David Plass wrote:
I have two different clients. One with a Novell 4.10 network and
NT 4.0 clients, and the other with NT 4.0 network and Win95 clients.
They both have recently added new pc's, which have created Fatal
Errors when using the previously stable environment.
I'm convinced it's configuration issues on the client machines, but I
can't locate any problems in their configs. I have discovered that
they both created the machines with some sort of a workstation
duplication method, so that they are keeping their workstations
standardized.
We've played with the memory configs: EMS 4096, EXT none, Auto
everything else. We've checked drive mappings, the temp dir and
COMMSPEC settings. They are using ARev 3.12 and NPP 1.3.
Thanks in advance.
At 27 AUG 1998 06:32PM Steve Smith wrote:
There is a chance that the video arrays are big, conflicting with either (a) BIOS shadow RAM addresses or (b) your expanded memory page frame addressing.
Check your config.sys for device=EMM386… and for the /X= parameters being set, then go into AREV, type at TCL WHO, and page down to check the page frame regions - ensure that these are excluded in config.sys. Then go into the PC's BIOS and disable all caching & shadowing at these addresses. Turn it all back on one step at a time, taking care to avoid switching on the addresses reported by WHO in AREV.
Also in your AREV directories under Novell 4.x, using FLAG.EXE
FLAG *.* -T
(disable transaction tracking
FLAG *.* SRW
(shareable read write)
FLAG AREV.EXE SRO
(shareable read only)
Set your protocol to NDS BIND, and ensure all your Novell files have valid owners.
Steve