[Date Prev][Date Next][Subject Prev][Subject Next][
Date Index][
Subject Index]
Re: RE Which Computer
- Subject: Re: RE Which Computer
- From: "Robert Holmgren" holmgren@xxxxxxxx
- Date: Sat, 8 Oct 2005 07:56:13 -0400
** Reply to message from "Patricia M. Godfrey" on Fri, 07
Oct 2005 17:09:50 -0400
> Robert reports that (under W2K?)
> on many mobos the USB drivers usurp the memory area that should be used
> for EMS (expanded memory; that's the kind that Xy officially uses
This is motherboard based -- nothing to do with the OpSys. Note Well: This is
**not** about "USB drivers", it is about the USB BIOS!! A much narrower issue
than you suggest, and two very different beasts. The USB BIOS is what allows
you to BOOT an operating system from a USB device, such as a USB CD or a memory
key or diskette. Boot! Not drive a USB device -- you can have EMS enabled and
simultaneously load USB drivers and operate a USB mouse or keyboard or
whatever, no problem whatsoever, no conflict.
> though I suspect that some XMS [extended] memory is also used, certainly
> during "installation"--which is why you cannot "install" under 32-bit
> Windows, but have to copy an existing setup).
No XMS is used anywhere. There are several reasons why installs (sometimes)
don't work, including printer initialization, which is completely different in
DOS and Win32.
You don't need EMS to run XyWrite. It only assists the Speller. And only the
non-U.S.English Microlytics dictionaries really *require* EMS. Learn how to
spell.
The reason dBase and XyWrite occupy the same memory addresses in a MEM report
is that they are running in different VDMs. The first executable would always
launch at the same memory address in any VDM, assuming identical CONFIG &
AUTOEXEC.
EMS is NOT virtualized in Win32. It really does occupy a 64Kb window at a
specific memory location. If it was virtualized, there wouldn't be any
conflict with USB BIOS.
-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------