Xref: utzoo comp.protocols.nfs:723 comp.sys.ibm.pc.programmer:127
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!mailrus!iuvax!maytag!mks.com!eric
From: eric@mks.com (Eric Gisin)
Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc.programmer
Subject: Re: QEMM 386 and PC-NFS
Summary: exclude WD8003 shared memory
Message-ID: <1990Feb26.182603.3049@mks.com>
Date: 26 Feb 90 18:26:03 GMT
References: <587@massey.ac.nz>
Organization: Mortice Kern Systems Inc., Waterloo, Ontario, CANADA
Lines: 17

In article <587@massey.ac.nz>, GEustace@massey.ac.nz (Glen Eustace) writes:
> [...]
> Case 2.
>     Put system disk in A: with QEMM, turn power on, boot machine.
>     System locks up immediately after running the NET START command.
>     must reboot with Hard-Reset.

The WD8003 has shared memory that is mapped somewhere above 640K.
This memory does not appear after power up, but does survive reboots.
QEMM automatically determines whether memory above 640K
is RW, ROM, or unused.  This explains why you get different
behaviour in case 1 and 2.
In case 1 after the reboot, QEMM sees the WD8003 shared memory.
In case 2 after power up, QEMM does not see it, and maps in some high memory
which conficts with the shared memory the WD driver later tries to map in.
All you need to do is add an EXCLUDE statement to the QEMM.SYS line,
for example ...\QEMM.SYS MEM EXCLUDE=CC00-CDFF.