Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!decwrl!ucbvax!agate!monsoon.Berkeley.EDU!tdoi
From: tdoi@monsoon.Berkeley.EDU (Takeshi Doi)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: QEMM 5.0 & 3Com 3C503 Conflict
Message-ID: <1990Aug12.012142.14371@agate.berkeley.edu>
Date: 12 Aug 90 01:21:42 GMT
References: <1033@lehi3b15.csee.Lehigh.EDU> <20012.26c32cdd@oregon.uoregon.edu> <32691@cup.portal.com>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Distribution: usa
Organization: University of California, Berkeley
Lines: 20

In article <32691@cup.portal.com> rwp@cup.portal.com (Roger William
Preisendefer) writes:  
>The solution for us was to explicitely exclude the memory 
>that the card is mapped into.  On our configuration the line reads 
>     device=qemm.sys RAM exclude=cc00-ccff 
>The RAM line allows you to load drivers into high memory using LOADHI, and 
>the exclude tells QEMM not to use the ethernet card's DMA location.  

This works if your 3C503 is set to CC000.  There are 4 other memory 
locations where a 3C503's DMA could be located.  Whichever
jumper you have your card set to it'll need 16K (3E80h) of high memory to
be excluded from QEMM's space.  If it's set at C0000 then use:

device=c:\dv\qemm.sys EXCLUDE=C000-C3E8 

Note the last digit is left off of QEMM's config line.  It already knows 
the proper segment.  
Some versions of QEMM will take the ADAPTERROM= parameter, others
require EXCLUDE=.  This works with both Novell and Banyan networks.
PC-NFS on the other hand, only works with DMA disabled.