Xref: utzoo comp.protocols.nfs:719 comp.sys.ibm.pc.programmer:99
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!deimos!unmvax!intvax!bryan
From: bryan@intvax.UUCP (Jon R Bryan)
Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc.programmer
Subject: Re: PC-NFS and 386SXs
Message-ID: <2604@intvax.UUCP>
Date: 23 Feb 90 15:19:02 GMT
References: <582@massey.ac.nz>
Organization: Sandia National Labs, Org. 1411, Albq, NM
Lines: 21

From article <582@massey.ac.nz>, by GEustace@massey.ac.nz (Glen Eustace):
> 
> 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 ?
> 
I load PCNFS.SYS and VECIE6.SYS high with no problems.  I load
VECIE6.SYS with option /i2 so that it uses interrupt 2.  If I don't
change the interrupt then Telnet won't run from Desqview reliably.  It's
still dangerous to push Telnet to the background.  My experience has
been that it crashes the machine within a minute or so, and I assume the
problem is with the "keep-alive" ping from the net generating an
interrupt that Desqview can't handle.  Desqview doesn't like interrupts
unless they're from the COM ports.

-- 
Jon R. Bryan	<=>	bryan@intvax.UUCP
Sandia National Laboratories
Intelligent Machine Principles Division
Albuquerque, New Mexico