Hello Mike,

    Responding to a post in the 4DOS area:
    On Thursday January 20 2005 at 20:54,
    Mike Powell [1:2320/105] wrote to Gerald Miller,
    about: DV/X

 >> When I installed the Qemm97, it detected my WfW3.11 system and made
 >> some changes to some of the WfW files.  Now, when I try to run WfW,
 >> I get the following error message:
 MP> Oh, yeah.  Quarterdeck was getting pressure to make their memory
 MP> manager Windows compatable.  So they did, and unfortunately, I think
 MP> it was their downfall.  It was just as bloated & bad as all other
 MP> Win3.x software. However, most folks swear that it is better if you
 MP> are running DOS-only, or one of the DV flavors, than what was
 MP> available before it.

Okay.  I have a 4DOS configuration that was memory managed by the previous
version of QEMM; I'll set it up and change all the pathnames to see if
there is any improvement...

 MP> I did not remember it ever corrupting anything here, but I somehow am
 MP> not surprised that it did.

 MP> I used to use separate config.sys and autoexec.bat files to call WfWG
 MP> (without QEMM) and DV & DV/X, in order to keep everything as separate
 MP> as possible.  Later, I started to use the MS-DOS multiple config
 MP> option.

I used to use the MS-DOS multiple config file but have since gone back to
separate Config.sys and Autoexec.bat system.  I found a nice (old) program
called BootIt that permits multiple (matching pairs) Config / Autoexec in
one large configuration file.  Very easy and much simpler to use than the
MS-DOS multiple config file.  It can be used on the command line and you
get presented with a menu of configuration choices _or_ you can pass a
configuration variable name to the command line executable.  The only thing
that you have to do is boot the system before they take effect.

Remind me in a couple of weeks to tell you what happened.  

           Cheers ... Gerald

... You know you're getting old when the candles cost more than the cake.
--- GoldED+/DPMI32 v1.1.5-040330