Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!linac!midway!DAN@wystan.bsd.uchicago.edu From: dan@wystan.bsd.uchicago.edu Newsgroups: comp.os.msdos.misc Subject: Re: DOS 5: Problem with EMM386.EXE and 1542B controller Message-ID: <0094A790.29746440@wystan.bsd.uchicago.edu> Date: 22 Jun 91 01:36:56 GMT References: <1991Jun17.114812.11279@jet.uk> <80495@eerie.acsu.Buffalo.EDU>,<1991Jun21.232638.482@mnemosyne.cs.du.edu> Sender: news@midway.uchicago.edu (NewsMistress) Reply-To: dan@wystan.bsd.uchicago.edu Organization: Dept.of Neurology, Univ.of Chicago, USA Lines: 38 >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. The problem with DOS 5 and SCSI controllers on my box seems to be with SMARTDRV. You can't DEVICEHIGH= either SMARTDRV or the SCSI driver unless the other driver is already loaded into _conventional_ memory. If I try to load either in the UMA before the other is active low it hangs the system on reboot. I guess it makes sense since they're both buffering devices and probaly try to compete with each other for memory. The config.sys has to go in one of these two orders: 1. DEVICE=your SCSI driver DEVICE=HIMEM.SYS DEVICE=EMM386.EXE DEVICEHIGH=SMARTDRV.SYS or, 2. DEVICE=HIMEM.SYS DEVICE=EMM386.EXE DEVICE=SMARTDRV.SYS DEVICEHIGH=your SCSI driver The SCSI driver for my card (a 1540A) is smaller than SMARTDRV so I've been using the first of these two, but I have done it the other way with no problems. Unfortunately, until Adaptec issues some new drivers it looks like we're stuck in lower memory. (P.S. - If anybody does know a way to get both drivers into the UMA or if Adaptec has issued new stuff, _please_ let us know!) Good Luck, Dan Rohwer-Nutter dan@wystan.bsd.uchicago.edu Univ. of Chicago - Neurology