Xref: utzoo comp.protocols.nfs:717 comp.sys.ibm.pc.programmer:86
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!mips!apple!sun-barr!newstop!east!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc.programmer
Subject: Re: PC-NFS and 386SXs
Message-ID: <1615@east.East.Sun.COM>
Date: 22 Feb 90 20:46:07 GMT
References: <582@massey.ac.nz>
Sender: news@east.East.Sun.COM
Reply-To: geoff@East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Followup-To: comp.protocols.nfs
Organization: Sun Microsystems PC-NFS Engineering
Lines: 35

Quoth GEustace@massey.ac.nz (Glen Eustace) (in <582@massey.ac.nz>):
#Anyway another question about PC-NFS and 386 machines.
#
#We are playing with the Quarterdeck QEMM memory manager.  It suggests
#that various device drivers can be loaded high.  What governs the choice
#of suitable candidates.  Which of the PC-NFS drivers will run correctly
#when loaded high, if any ?

My standard PC is an NEC Powermate Portable SX, a nice little 386SX
which, though a tad slow, has the most accessible slots in the business :-)

I occasionally run with QEMM386 to save space, using a CONFIG.SYS of
the following form:

BUFFERS = 20
SHELL=C:\COMMAND.COM /P /E:800
FILES=20
DEVICE=C:\NFS\SOCKDRV.SYS
DEVICE=C:\NFS\<link-level-driver>.SYS
DEVICE=\QEMM386\QEMM.SYS FRAME=NONE RAM
DEVICE=\QEMM386\LOADHI.SYS C:\NFS\PCNFS.SYS  /M /S /R0 /F16
DEVICE=\QEMM386\LOADHI.SYS C:\GAMES\NANSI.SYS
LASTDRIVE=V

Note that you cannot load the link level driver or SOCKDRV.SYS high; these
bugs will be addressed in a future release of PC-NFS. (I know why the link
level drivers won't work; I haven't yet worked out why SOCKDRV.SYS doesn't.)

I have encountered one obscure glitch with a third-party board driver
in this configuration, but apart from this things look pretty solid.

Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM)
-----------
News software that enforces a four-line .signature limit is responsible for
the fact that these postings just go on and on and on and seem to end in mid-