*BSD News Article 85503


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!newsfeed.direct.ca!portc01.blue.aol.com!cliffs.rs.itd.umich.edu!newsxfer2.itd.umich.edu!www.nntp.primenet.com!nntp.primenet.com!news-feed.inet.tele.dk!not-for-mail
From: Ronnie Bloch Hansen <ronnie@post4.tele.dk>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Problem with EMM386 and 3com etherlink III
Date: Mon, 23 Dec 1996 23:29:33 +0100
Lines: 14
Message-ID: <32BF07CD.2394@post4.tele.dk>
NNTP-Posting-Host: ppp76.kbh.tele.dk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.02E-TDK12  (Win95; I)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:33026

I have a MS Windows NT 4.0 server.
The PC's are connected to the NT server as Windows for workgroups clients.
(I'm using 3com etherlink III cards)
My problem is that the clients hang or reboot when the driver for EMM386 is loaded and 
net initializing begins. 

If I remove the DEVICE=C:\WINDOWS\EMM386.exe from CONFIG.SYS the net initializes and 
starts ok. But some of my programs requires EMM386.

Could it be an IRQ problem ? How do I find the problem ?
I've tried to use MSD, but I can't find any conflicts !


ronnie@post4.tele.dk