Xref: utzoo comp.os.msdos.misc:2511 comp.periphs.scsi:2932 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!mips!zaphod.mps.ohio-state.edu!usc!trwind!venice!press From: press@venice.SEDD.TRW.COM (Barry Press) Newsgroups: comp.os.msdos.misc,comp.periphs.scsi Subject: Re: DOS 5: Problem with EMM386.EXE and 1542B controller Message-ID: <1127@venice.SEDD.TRW.COM> Date: 19 Jun 91 16:06:11 GMT References: <1991Jun17.114812.11279@jet.uk> Reply-To: press@venice.sedd.trw.com (Barry Press) Organization: TRW Systems Engineering & Development Division, Redondo Beach, CA Lines: 34 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. It must be something in your setup. I have a 486 with a 1542B and have been running DOS 5 with the UMB's for quite some time now. I don't have the config.sys here to simply post, but (roughly) the order of loading things goes like this. The following are loaded normally (device=) adaptec.sys (moves the configuration tables) himem.sys emm386.sys aspi4dos.sys then these get loaded high (devicehigh=: smartdrv.sys ramdrive.sys etc. Be sure you use the versions provided with DOS 5 and not older ones. The adaptec.sys is very old (but small and apparently doesn't do much after it loads); the aspi4dos.sys I have is 2.1B (beta) -- See Roy Neese's offer posted in another article if you don't have it. I also have the obligatory VirtualHDIRQ=False in the [386enh] section for Windows, the net resulting setup has been extremely stable. A sequential file I/O test on 8MB files (4MB cache, so it gets defeated) and 16384 byte blocks shows in excess of 500K bytes/sec write and > 450K bytes/sec read. -- Barry Press Internet: press@venice.sedd.trw.com