Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!waikato.ac.nz!canterbury!phys169
From: phys169@csc.canterbury.ac.nz
Newsgroups: comp.protocols.nfs
Subject: Re: PCNFS & QEMM5.11 & DOS5.0
Message-ID: <1991Mar20.132233.279@csc.canterbury.ac.nz>
Date: 20 Mar 91 01:22:32 GMT
References: <285@mailgzrz.tu-berlin.de>
Organization: University of Canterbury, Christchurch, New Zealand
Lines: 21

In article <285@mailgzrz.tu-berlin.de>, behrends@tubife.ee.tu-berlin.de (Behrends) writes:
> 
> On a 386SX, connected to a network via SUN PC-NFS ( Ni5210, Ethernet ), the
> nfsconf command does not work anymore. I suppose the problem is the "dos=high"
> option of DOS5.0, but I'm not sure about that. Nfsconf says 'packed file
> corrupt', but the network itself works correctly. 

I had some problems with memory above 640K being used both by an ethernet card
and by DRDOS5.0. The problem seems to be that when DRDOS (and, probably, other
386 memory managers) look to see what addresses are available to remap RAM
into, quiet often ethernet cards with on-board RAM don't have their RAM enabled
at the time. To check this, try changing your config.sys line that refers to
EMM386.sys to (a) not use it at all, or (b) /Exclude lots of address space
where their is the slightest possibility of a clash. I use /Auto to include
from D000 up, that might be good enough for you, but possibly not. I use a
variety of software with the network card I have, which all seem to insist on
moving the onboard RAM around, which causes problems. I also use /BDOS=FFFF.

Hope this helps,

Mark Aitchison, Physics, University of Canterbury, New Zealand.