Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!keithe
From: keithe@tekgvs.LABS.TEK.COM (Keith Ericson)
Newsgroups: comp.protocols.nfs
Subject: Re: putting PCNFS drivers in extended/expanded memory
Message-ID: <5917@tekgvs.LABS.TEK.COM>
Date: 11 Sep 89 21:18:24 GMT
References: <8909101827.aa05973@ICS.UCI.EDU>
Reply-To: keithe@tekgvs.LABS.TEK.COM (Keith Ericson)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 23

In article <8909101827.aa05973@ICS.UCI.EDU> milne@ICS.UCI.EDU (Alastair Milne) writes:
>
>   We are working with some development software on Tandy 4000's that are on
>   an NFS net, using PC-NFS.  Between the Norton Commander (overlayable
>   version), the development software, and the net drivers, memory is getting
>   very tight -- and these machines have almost 2 meg each.  So what I'd like
>   to do is get the network drivers into extended or expanded (anybody know
>   the difference?) memory, where they won't compete for primary memory.  But
>   I haven't seen a way of doing this.

I know of two ways around the problem:

	1) with 386 amchines use 386*MAX to load PCNFSD.SYS and WD8003E.SYS
into "High DOS Memory" (the region between 640k and 1Meg). Note: the SOCKDRV.SYS
won't load up there - it tries to occupy more memory than is available, even
though it isn't all that big.

	2) use on of the "machine re-configuration schemes" (multiple config.sys
and autoexec.bat files; or a fancier config- and autoexec-construction programs
that rebuilds config.sys and autoexec.bat files for you) teamed with a reboot
program.  Only load the networking software when you have to have it.

kEITHe