🚀 go-pugleaf

>> [I said (not very eloquently) that DOS 5.0 used too much XMS] 
> What exactly is happening here? is it just that you didn't have
> enough XMS left over for 4DOS to load there or is there some
> serious conflict with memory management? (I'd hate to think that
> DOS 5 would, say take over all my XMS). Anyone out there have
> specific experiences with the DOS5/4DOS/QEMM combo?
> 
> -dh
The install program added a line to CONFIG.SYS that overrode my current  
HIMEM.SYS settings.  Once I took that line out, all was well again.

This goes back to something that all usoft packages  have ever seen do when  
they install: unintelligently edit CONFIG.SYS and AUTOXEC.BAT the poor user  
ends up with more than one PATH statement, or more than one line that says:
DEVICE=HIMEM.SYS

Also, DOS 5.0 install _DELETED_ the lines that said COMSPEC=...4DOS and  
SHELL=...4DOS on my system.  Once before (with QuickBasic (not so quick) ),  
Microsoft changed my path in my autoexec so that a later statement: MOUSE found  
the mouse driver that came with uSoft QB, and not my Logitech mouse driver.   
Sigh.  I have to wonder sometimes if uSoft sits around and thinks these things  
out.  Not whether they don't consider the effects of their own actions, but  
whether they try to come up with actions that will have the effect of  
disturbing systems that do not meet uSoft's ideal picture of uSoft-riden  
systems.

--
Heath Hunnicutt              | X-Wing Pilot: "Ahhh! I'm gonna die!"
heathh@pooh.cco.caltech.edu  | Rebel Command: "Stay on target..."
131.215.48.30                | ... my life at Caltech
---------------------------------------------------------------------------
In the unlikely event that I might seem to be representing Caltech's opinion on  
any matter, I am not.  In fact, if it is brought to my attention that I share  
any particular opinion with Caltech's administration and other assorted Yahoos,  
I will change that opinion of mine.