home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!hri.com!snorkelwacker.mit.edu!bloom-beacon!eru.mt.luth.se!lunic!sunic!news.funet.fi!hydra!klaava!jliukkon
- From: jliukkon@klaava.Helsinki.FI (Juha-Matti Liukkonen)
- Newsgroups: comp.os.msdos.misc
- Subject: Re: Windows Enhanced Mode + UMB_DRVR
- Message-ID: <1992Sep4.211641.20262@klaava.Helsinki.FI>
- Date: 4 Sep 92 21:16:41 GMT
- References: <2016.2AA50535@catpe.alt.za> <1992Sep3.151506.6510@klaava.Helsinki.FI> <1992Sep3.235619.7142@rei.com>
- Organization: University of Helsinki
- Lines: 21
-
- In <1992Sep3.235619.7142@rei.com> fox@rei.com (Fuzzy Fox) writes:
-
- >I run UMB_DRVR 5.21 with Windows 3.1, with no EMMExclude at all, and 2
- >megs of memory. No MONOUMB either. Works fine. However, I do tell
- >UMB_DRVR not to use the area from B000-B7FF, because SmartDrive crashed
- >when loaded there. MONOUMB[2].386 did not fix this.
-
- Yes, you can run Windows 386 mode without the EMMExclude, BUT: I don't
- know what actually causes it, but sometimes Windows won't boot, and
- complains it can't load kernel386.exe. This is fixed by the EMMExclude.
-
- With B000-B7FF, the area can either be excluded, or MONOUMB'd. The
- former removes the area from use altogether, while the latter gives
- Windows 32K more room. MONOUMB.386 works in my setup. I'd suggest you
- try the EMMExclude AND MONOUMB, the Exclude might be a prerequisite. Or
- why bother, it's only 32K... (I did it out of curiosity...)
-
- --
- Juha Liukkonen, aka jliukkon@cc.helsinki.fi
- University of Helsinki, Dept. of Paranormal Investigations
- "Trust me, I know what I'm doing." - Sledge Hammer
-