Xref: utzoo comp.os.msdos.misc:2514 comp.periphs.scsi:2933
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!caen!zaphod.mps.ohio-state.edu!ub!acsu.buffalo.edu
From: dtw@acsu.buffalo.edu (daniel t wesolowski)
Newsgroups: comp.os.msdos.misc,comp.periphs.scsi
Subject: Re: DOS 5: Problem with EMM386.EXE and 1542B controller
Message-ID: <80495@eerie.acsu.Buffalo.EDU>
Date: 19 Jun 91 16:34:52 GMT
References: <1991Jun17.114812.11279@jet.uk>
Sender: news@acsu.Buffalo.EDU
Followup-To: comp.os.msdos.misc
Organization: SUNY Buffalo
Lines: 15
Nntp-Posting-Host: lictor.acsu.buffalo.edu

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.

I have the same problem. If you are using IBM Dos, there is
a readme file that says that you cannot load devices high, when
using a DMA controlled controller. If you are using MS-Dos
I'd assume the same cannot be done. If you are using the EMM386
you have to replace the NOEMS switch to RAM. Make sure
aspi4dos.sys is loaded before EMM386.

Dan