Reply 60 of 76, by johnsonlam
- Rank
- Newbie
wrote:That's because /B is meant for use with UMBPCI. Good to know XDVD seems to be ok now, but try it with some disc based games. That's also where shsucdx seems to have issues.
I'm Johnson Lam post the following for Jack R. Ellis, since he can't access the Vogons forum:
I am the author of the XMGR/XHDD/XDV2 drivers. I am totally dismayed and upset
by the IGNORANT posts of 17-Sep-2019 on VOGONS about XMGR and XHDD.
First, if you had read the drivers' README file, you would know that the XMGR /B
switch is not for UMBPCI usage. It applies to "booting" XMGR into upper memory
when used with an "EMM" driver like JEMM386 or Microsoft EMM386. Using /B also
requires loading XMGR a second time after the "EMM" driver enables upper-memory,
like I show in CONFIG.SYS example C (Section 5 of the drivers' README). If you
do not load XMGR again, which deactivates its "boot" code in "temporary" memory,
the still-active "boot" is overrun by other programs. THAT is why you CRASHED!
Second, XHDD does not work the same as wretched SMARTDRV. SMARTDRV "eats" many
times more memory for a maximum 20-MB cache, too small to be of any value with a
Terabyte disk of today. XHDD uses a maximum 2848 bytes of upper/DOS memory (or
720 if most of it loads in the HMA via its /H switch), offers XMS caches up to 4
GIGABYTES, and is far faster than SMARTDRV, given XHDD's Read-Ahead, DMA/caching
overlap, and other improved logic. Also, XHDD uses no C+ /N /U or /? switches!
Finally, I spend hours writing clear and concise README files, as a lot of XMGR/
XHDD/XDVD2 users reside in countries other than the U.S.A. You should actually
READ the drivers' README file before saying I'm "not the best at documentation".
Might also help you avoid making IDIOTIC posts which prove you paid NO attention
to information you MUST know, before using XMGR/XHDD/XDVD2!
If you cannot (or will not) read their README file, FIND YOURSELF OTHER DRIVERS,
and do not try to fault ME over your own miserable IGNORANCE!!
Jack R. Ellis