[comp.protocols.nfs] putting PCNFS drivers in extended/expanded memory

milne@ICS.UCI.EDU (Alastair Milne) (09/11/89)

   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.  Does anybody have one -- presumably a
   set of switch settings that can be added to the DEVICE= statements in
   CONFIG.SYS?  The drivers we're using are PCNFS.SYS, WD3008E.SYS, and
   SOCKDRV.SYS .

   In case anybody thinks of it, I've already removed the RAMDISK that the
   Tandy's used to have.


   Thanks for any help.

   Alastair Milne

keithe@tekgvs.LABS.TEK.COM (Keith Ericson) (09/12/89)

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

jwc@bdrc.UUCP (Joan Curry) (09/12/89)

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. [...]  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.  Does anybody have one -- presumably a
>   set of switch settings that can be added to the DEVICE= statements in
>   CONFIG.SYS? [...]
>

We've been successful in putting two out of three PC-NFS drivers (pcnfs.sys
and sockdrv.sys) into expanded memory on a Compaq 386 by using the memory
management software product 386 Max.  Let me know if you want any details.

(I have no connection with Qualitas Inc., the folks who provide 386 Max.)

-----
Joan Curry  bdrc!jwc@mcnc.org