🚀 go-pugleaf

In article <reichert.714863265@aloe1> reichert@rtsg.mot.com (Charles H. Reichert) writes:

>>EMM386 is apparently forced - perhaps because of SSTOR being in use, so QEMM
>>refuses to load, telling me another memory manager is already resident. If
>>someone from novell.com can clarify this for me, I'd appreciate hearing from
>>them, as I would indeed rather use QEMM...

>Any memory manager should be loaded first (if possible) and by itself.
>EMM386.SYS or QEMM.SYS, but not both
>HIMEM.SYS or HIDOS.SYS, but not both

One more time - EMM386.SYS loads _by itself_, without config.sys entry, but
I can't find out why, although I assume it's because of the SSTOR drives.. I
can't get rid of it...

(I may have to wipe the disk and reboot with QEMM.SYS, and THEN try using
SSTOR, but it's more work than I want to take on right now.)

-- 
"Walter Dejaco, of Reutte, a town in the Austrian Tyrol, who designed and
constructed the Auschwitz crematoria had no trouble in continuing to fulfil
building commissions. In 1963 he won warm praise from Bishop Rusk of
Innsbruck for the fine Presbytery he had built..." [Abram L. Sachar]