Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!ccu.umanitoba.ca!herald.usask.ca!alberta!aunro!aupair.cs.athabascau.ca!atha!decwrl!elroy.jpl.nasa.gov!usc!jarthur!nntp-server.caltech.edu!nyet
From: nyet@nntp-server.caltech.edu (prof. n liu)
Newsgroups: comp.os.msdos.apps
Subject: Re: Can't reboot with QEMM 5.1
Message-ID: <1991Mar14.011755.539@nntp-server.caltech.edu>
Date: 14 Mar 91 01:17:55 GMT
References: <1991Mar6.184139.12767@tasha.poly.edu> <3022@bimacs.BITNET>
Organization: California Institute of Technology, Pasadena
Lines: 41

orenalex@bimacs.BITNET (oren alex) writes:

>In article <1991Mar6.184139.12767@tasha.poly.edu> ted@tasha.poly.edu (Theodore S. Kapela, Staff) writes:
>>Some time ago we purchased QEMM v5.1.  I am using it with the ROM
>>and RAM parameters, so the processor is forced into protected mode
>>all the time.  When using qemm this way, I am unable to do a
>>software reboot via CTL-ALT-DEL (or any other method).  All
>>reboots must a cold boots.  This does get somewhat anoying having
>>to reach over and hit the reset key all the time to reboot.

>>The machine has a 25MHz 386, no coproc, AMI BIOS with C&T chipset.

>Same thing happens on my machine
>(386/20 Micronics motherboard, Phoenix BIOS, unknown chipset - not
>C&T)

>The machine *does* reboot if I flip the dipswitch to use ROM
>relocation in hardware, but then I wind up with less memmory (384K go
>the relocation scheme) and the Video BIOS of my ATI V.W. is suddenly
>in two places at once... (weird? yes!)
>OK, you gurus out there - speak up

Boing, pfffft, gee wow. I too have been having difficulties with my 386/20
Micronics and QEMM.. I'd assumed earlier that i was just stupid or that 
strange things are supposed to happened with your video bios. Hell, even
now my video bios (paradise 512k SVGA) exists in two places, and loading
ANYTHING high seems to overwrite at least one of these, rendering graphics
impossible. Just what the hell is going on here? I actually have no problems
rebooting, except (and this is REAL weird) with the EMS drivers included
with the m-board - i get a rom error and have to run setup and then continue
to get that to even marginally work. So what i've done essentially is 
given up on EMS for loading high, and not worring about memory used by
random .sys and tsr's. I have had no problems with XMS drivers at all
so far...

Incidentally, flipping the dipswitch generally does what you'd expect
on mine, but loadhi with QEMM still don't work at all.

So, yes, i concur... help!

nyet@cobalt.caltech.edu