Xref: utzoo comp.protocols.nfs:721 comp.sys.ibm.pc.programmer:119
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!wuarchive!rex!ames!uhccux!munnari.oz.au!kaukau.comp.vuw.ac.nz!comp.vuw.ac.nz!massey!GEustace
From: GEustace@massey.ac.nz (Glen Eustace)
Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc.programmer
Subject: QEMM 386 and PC-NFS
Message-ID: <587@massey.ac.nz>
Date: 26 Feb 90 01:45:04 GMT
Organization: Massey University, Palmerston North, New Zealand
Lines: 54
X-Reader: NETNEWS/PC Version 2.1

I am beginning to wonder if I will ever get anything right!  I have been
fighting a room full of 386SX machines for over a week and seem to be
losing every round.

Can anybody throw some light on the following behaviour.  I have no idea
what components are part of the problem, my only clues are as follows.

1.  I am using the Quarterdeck QEMM.SYS 386 memory manager v4.23,
    I have version 3.0.1 of PC-NFS.
    The machines have an AMI BIOS and MS-DOS 3.3

Case 1.
    Put system disk in A: without QEMM, turn power on, boot machine.
    Everything is OK.
    Put system disk in A: with QEMM, reboot with Alt-Ctrl-Del.
    Everything is OK,  System goes beautifully in fact.

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 above is 100% reproducable.
The config.sys file is;

BUFFERS=30
FILES=70
DEVICE=A:\QEMM\QEMM.SYS RAM
DEVICE=A:\NFS\PCNFS.SYS /I0 /F70 /S
DEVICE=A:\NFS\WD8003E.SYS /i3 /p280 /md0000A
DEVICE=A:\NFS\SOCKDRV.SYS
DEVICE=A:\QEMM\LOADHI.SYS A:\ANSI.SYS
DEVICE=A:\QEMM\LOADHI.SYS A:\GENIUS\GMOUSE.SYS /11
DEVICE=A:\QEMM\LOADHI.SYS A:\CCNET\NETINFO.SYS
LASTDRIVE=V

I don't understand why it works in case 1 and not case 2......

This is how things happened.
I built my usually A:boot disk with no QEMM. I installed QEMM on the
disk, editted the config file and rebooted with Alt-Ctrl-Del.  Wow!! All
of a sudden I have lots of memory.  Everything worked great.  Boy are our
users going to love this new environment.  Turn machine off, go home for a
well earned sleep.  Come in the next day and turn the machine on.  Things
seem OK until it gets to the network startup and it hangs???.  Who's been
fiddling with my machine, nobody. Edit out QEMM from CONFIG.SYS, reboot
and all is fixed.

-- 
-----------------------------------------------------------------------
  Glen Eustace, Software Manager, Computer Centre, Massey University,
   Palmerston North, New Zealand. Phone: +64 63 69099 x7440 GMT+12
             E-Mail via Internet: G.Eustace@massey.ac.nz
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>