osyjm@warp.mhd.montana.edu (Jaye Mathisen) (06/05/91)
In article <EFF7542F202034A0@brook.bitnet> PENTECOST@BROOK.BITNET (Gregg Pentecost X6228 IC44) writes: |>OK, I fold. Under 3.1 I had windows 3.0 running in enhanced mode with |>QEMM. When I upgrade to 4.0, no luck. Everything works fine when I use |>HIMEM.SYS, but not QEMM. I've tried QEMM 5.10, 5.11, and 5.12 with no |>luck. I've tried both Windows 3.0 and 3.0a... | |>I don't see enough information in your explanation to be precise about |>what may or may not be happening but I'll take a possible shot. Since The PC boots and runs fine, just windows won't start in enhanced mode. I'm doing local boots. I added the NX option to the QEMM line (No eXtended BIOS Data Area or somesuch), and it's working perfectly. My QEMM line is: device=c:\qemm5.12\qemm386.sys ram x=d000-dfff nx and it's working like a champ. Didn't need the ns nor nosh parameters like I think is suggested in the Memory Solutions book. For those of you still having problems, this is what was suggested to me by the QEMM technical support people as a place to start weeding out the problem. device=c:\qemm5.12\qemm386.sys ns ram x=1000-9fff fr=e000 x=d000-dfff nrh nt no nv nosh nx x=a000-afff x=b800-c7ff x=f000-ffff This line worked, but obviosly x'd out a lot that needed to be there... -- Jaye Mathisen,sysmgr 410 Roberts Hall,Dept. of Computer Science Montana State University,Bozeman MT 59717 PHONE: (406) 994-{4780,3931}