Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!munnari.oz.au!bruce!trlluna!titan!craick From: craick@titan.trl.oz (John Craick) Newsgroups: comp.windows.ms Subject: Re: 386 Enhanced Problem. Message-ID: <2849@trlluna.trl.oz> Date: 22 Mar 91 07:26:31 GMT References: <77.27DF83E0@bohemia.metronet.org> <13479@helios.TAMU.EDU> Sender: news@trlluna.trl.oz Lines: 42 jadam@cs.tamu.edu (James P Adam) writes: > BE> Why is it that I can run Windows in Real and Standard Mode, but not 386 > BE> Enhanced? My system is a 25MHz 386, 84MB SCSI HD, 2 MB Ram, QEMM 5.11. > BE> Every time I try to run in Enhanced Mode, I get Disk Read Error, Abort > BE> Ignore Retry Fail. The other modes work just fine! Also, anybody out > BE> there have docs on the Seagate ST-01 card? Mine didn't come with them. > BE> -Brian > I've had a similar problem. The answer for me was : Windows does not >like QEMM. If I tried to force windows into 386 mode (using the /3 switch), >it would start to load && will then drop out, leaving a message like: > "To run in 386 mode, remove the protected mode software from your >environment." > The protected mode software, in this case, was QEMM. The "solution" >was to use the HIMEM and emm386 drivers instead. I chose not to do that, >since it meant losing an extra 70K of low memory, since QEMM was loading >half a dozen disk drivers into high memory, something which the windows' >(standard-DOS) drivers are too stupid to know how to do. > So, anyway, another thing for you to try is to get rid of QEMM && >see if the error goes away then. Sorry but this answer is VERY wrong. QEMM versions 5.11 and above is definitely compatible with Windows - the best thing since sliced bread & I use it all the time, as do many others. The most likely problem is with your SCSII disk drive. There has been quite a bit of talk about this on the net but, sorry, I don't have the problem so I didn't keep the references. You might solve the problem by getting rid of QEMM but you'll lose an awful lot of memory in the process. I think this problem is partly addressed in the frequently asked questions posting for ms windows. I _think_ the answer is to exclude from QEMMs processing that portion of upper memory which is used by the SCSII adapter for data transfer. Sorry I can't be more definite - but don't give up on QEMM John Craick (j.craick@trl.oz.au)