Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!darkstar!ucscb.UCSC.EDU!funkstr
From: funkstr@ucscb.UCSC.EDU (Larry Hastings)
Newsgroups: comp.os.msdos.misc
Subject: Re: QEMM 5.1, Windows 3.0 and SUN PCNFS 3.0.1a
Keywords: QEMM, windows, PCNFS loading high memory.
Message-ID: <6907@darkstar.ucsc.edu>
Date: 15 Sep 90 01:53:22 GMT
References: <5077@mit-caf.MIT.EDU>
Sender: usenet@darkstar.ucsc.edu
Distribution: na
Organization: Knowledge Dynamics Corporation
Lines: 48


+-In article <5077@mit-caf.MIT.EDU>,
| gavin@mit-caf.UUCP (Gavin C. H. Zau) wrote:
|
| I am thinking of getting QEMM 5.1 for our PCs and am wondering
| if version 5.1 can loadhi SUN PCNFS 3.0.1 drivers and run 
| windows 3.0.  This is very important as our systems (Dell 310 -
| 20Mhz 386 and 3C501 ethernet card) is very low on conventional
| memory.
|
+----------

(Gee, I always thought you MIT guys were on top of the game!)

When I worked at MetaWare, we used PC-NFS all over the place, and it
was one of my jobs to figure out how to get PC-NFS to work optimally
with QEMM and DESQview.  After months of experimenting, and spending time
on the phone with Sun and Quarterdeck, I (and my successor) have come up with
the following:

1) The only PC-NFS driver you can load "high" is PCNFS.SYS -- any of the
   other drivers loaded high will eventually crash.
2) You can use (I believe) any of the PC-NFS applications inside of a
   DESQview window reliably except for telnet -- if you run telnet, you
   are _guaranteed_ to crash.  (You might be able to get away with running
   telnet if you _never_ change out of the window, and don't let it share
   CPU time... but this isn't terribly useful.)
3) PC-NFS could certainly be better behaved.

I should also warn you that Windows 3.0 doesn't like QEMM.  I'm not sure,
but I've been told that Windows (at one time) had specific code to detect
the presence of QEMM, and would only run in real mode... the workaround was
to _rename_ QEMM.SYS to something else.

Also, if your main problem is lack of conventional memory, you should consider
upgrading from the 3C501 to the 3C505 card.  The 3C505 is a "smart" card that
actually has an 80186 on-board, and comes standard with (I believe) 256k of
RAM (upgradable to 512k).  You then upload your 3Com drivers onto the card
instead of into conventional memory -- you only need to load enough drivers
to communicate with the card in conventional memory.  Of course, the 3C505
is quite a bit more expensive...
--
larry hastings, the galactic funkster, funkstr@ucscb.ucsc.edu

I don't speak for Knowledge Dynamics or UC Santa Cruz, nor do they speak for me

"You may remember I died suffocating on my own vomit.  That was a bummer of a
 way to go." --Keith Moon (ex-Who drummer) through a "channeler" from the "Sun"