Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!news From: smsmith@hpuxa.acs.ohio-state.edu (Stephen M. Smith) Newsgroups: comp.windows.ms Subject: Re: 386 Enhanced Problem. (Consider your problem solved!) Message-ID: <1991Mar23.033141.19433@magnus.acs.ohio-state.edu> Date: 23 Mar 91 03:31:41 GMT References: <13479@helios.TAMU.EDU> <2849@trlluna.trl.oz> <1991Mar22.212858.22878@cs.mcgill.ca> Sender: news@magnus.acs.ohio-state.edu Organization: The Ohio State University Lines: 65 Nntp-Posting-Host: hpuxa.acs.ohio-state.edu In article <1991Mar22.212858.22878@cs.mcgill.ca> gerardis@cs.mcgill.ca (Tony GERARDIS) writes: >In article <2849@trlluna.trl.oz> craick@titan.trl.oz (John Craick) writes: >> >>> I've had a similar problem. The answer for me was : Windows does not >>>like QEMM... >> >>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. > >Listen QEMM just doesn't behave properly with certain machines, mine >wouldn't crash but it felt so slow that It would be criminal for anyone >to use it! A whole bunch of my friends have had the same problem (all >with different 386 machines) If you don't have one problem with QEMM you >usually have another!... Sorry for the presumptuous subject line. I've just spent a week trying to configure my system and I've found out some helpful procedures to follow... The key I think here is to make sure that you know exactly what your HARDWARE is doing with the memory between 640k and 1024k. For example, I've just figured out how to make QEMM, Desqview, and Windows to work correctly on my new 386 system (Micronics MB). I found out that my hardware was shadowing 128k of BIOS from ROM into E000-FFFF; this happened to be used as Desqview's PAGE FRAME address!!! Plus QEMM had found a couple of supposed "holes" in the shadowed system BIOS, so it decided to use those too...but there were no holes as was confirmed when I ran QEMM's Analysis procedure. Here's a couple of suggestions: 1) Run QEMM's Analysis procedure. That's how I found the bogus "hole". To keep QEMM from disturbing my hardware's shadowed BIOS I just put NOHS as a parameter after QEMM386.SYS. 2) Write a nearly empty CONFIG.SYS file with only SHARE.EXE and MOUSE.SYS in it (with no QEMM or anything else). Reboot, and then examine your high memory with Manifest. Look closely at all the areas of high memory to see what your hardware did with them. Manifest does NOT (I repeat--NOT) see everything that's there. It missed 64k on my system. But it's worth a look. 3) Get your motherboard manual out and read everything in it that smells of memory. That how I found out that my hardware was shadowing 128k of its ROM instead of just 64k. It seems that QEMM never heard of shadowed BIOS that big, and so it only recognized HALF of it. 4) If you're still having problems, try switching the page frame address. If Manifest says that it's located at E000-EFFF, switch if to D000 by including "FR=D000-DFFF" as a parameter after QEMM386.SYS. I hope that helps someone--I've been totally frustrated, so I know what a lot of you are going through. Right now I'm trying to figure out how I can run Desqview since there's no high memory left on my computer for it to load into! I can't multitask if my DOS programs are limited to 475k. Stephen M. Smith \ + / ,,@ ircc.ohio-state. \ + / {7%*@,..":27g)-=,#*:.#,/6&1*.4-,l@#9:-) " edu> \ + / BTW, WYSInaWYG \ + / --witty.saying.ARC