Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!vax1.cc.lehigh.edu!lehi3b15!flash
From: flash@lehi3b15.csee.Lehigh.EDU (Stephen Corbesero)
Newsgroups: comp.sys.ibm.pc.misc
Subject: QEMM 5.0 & 3Com 3C503 Conflict
Message-ID: <1033@lehi3b15.csee.Lehigh.EDU>
Date: 9 Aug 90 19:37:59 GMT
Organization: CSEE Dept. Lehigh University, Bethlehem, PA
Lines: 18

I was installing my new 386 machine (Gateway-2000 33Mhz, 150MB ESDI,
4MB, Micronics Motherboard) and I ran into a serious snag.  I was able
to get QEMM up and running quite nicely until I installed my ethernet
card, a 3Com 3C503.  If the card is installed, the machine will cold
boot itself almost immediately after QEMM displays its signon
message.  I played with several command line options, even the ones
not in the documentation.  The best results were obtained by not
connecting my ethernet card to the net, and setting the QEMM flags
NOTOKENRING, LOCKDMA, NOSORT.  With this configuration, some of the
time the machine would sucessfully boot and I could then attach the
network cable and everything worked fine.  Even in a DesqView Window!

Does anyone know of any such conflicts and/or workarounds.  I was
really looking forward to QEMM+DV, but I need the networking too.

Thanks in advance.