Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!uunet!mnemosyne.cs.du.edu!isis.cs.du.edu!marmbrus
From: marmbrus@isis.cs.du.edu (Mark Armbrust)
Newsgroups: comp.os.msdos.misc
Subject: Re: DOS 5: Problem with EMM386.EXE and 1542B controller
Message-ID: <1991Jun21.232638.482@mnemosyne.cs.du.edu>
Date: 21 Jun 91 23:26:38 GMT
References: <1991Jun17.114812.11279@jet.uk> <80495@eerie.acsu.Buffalo.EDU>
Sender: usenet@mnemosyne.cs.du.edu (netnews admin account)
Reply-To: marmbrus@isis.UUCP (Mark Armbrust)
Organization: Nyx, Public Access Unix (sponsored by U. of Denver Math/CS dept.)
Lines: 15
Disclaimer1: Nyx is a public access Unix system run by the University of
Disclaimer2: Denver for the Denver community.  The University has neither
Disclaimer3: control over nor responsibility for the opinions of users.

>In article <1991Jun17.114812.11279@jet.uk> cm@jet.uk (colin manning) writes:
>>Installing DOS 5 on a machine with a 1542B SCSI controller,
>>I have a problem with EMM386.EXE. It doesnt work. System
>>crashes as soon as you try to put something in a UMB, such
>>as loading RAMDRIVE using devicehigh. Similar problem also
>>seen with a 1740 EISA SCSI.

When I first tried this, I had some flakey things happen, too.  One time the
driver managed to tell me that it needed a DMA=128 option (something similar
to that, at least -- I'm not at work at the moment so this is from memory).
I added this to the EMM386.SYS line and the system seems to run OK now.  I 
didn't bother to learn what this is really doing--something about reserving
some memory for a DMA buffer.

--Mark