Stewart Honsberger wrote in a message to All:
SH>     Hello all, (again.. {sigh}  ) I've come to some sort of a
SH> conclusion, and  was wondering if you could tell me if I'm right or
SH> not.. WHen I ran Max  3.01/DOS with QEMM 8.0, I got a "QEMM Error,
SH> program attempted to execute an  invalid instruction.. QEMM did not
SH> cause this error, it simply reported it..." blah blah blah.. Well, I
SH> switched to Microsoft Memtaker, I get less ram, and  when I load MAX
SH> I get a screen full of funny colored boxes and blinking HIGH  ASCII
SH> charachters. Now, the conclusion I think I have, does max REQUIRE an
SH> ANSI driver for DOS? I use ANSI.COM, and for some reason (well, on a
 Try Ansi.sys loaded via your config.sys file.
 I.e.  DEVICEHIGH=C:\DOS\ANSI.SYS /X
SH> 5 - 6  year old 386 SX-33 w/4 meg ram, it's likely age.. :<  ) when
 Max should work OK under that setup; that's close to what I used
 when I began.  Slow but it does the job.  Forget QEMM, though.  Tried
 it under my version of the same setup and had nothing but troubles.
 Real RAM is much more useful, IMO.
 For the most part Memmaker can do a decent enough job, especially
 with some manual pruning of loaded drivers. 
SH> it tries to load  my ANSI driver on startup, if I'm really paying
SH> attention, it says "Not Enough Memory"..(????) I have **NO** clue
 Not enough memory for Ansi?  What are you loading that's taking
 up so much???  Even with a full load of junk in Config.sys, I'd get
 595K conventional free... under Win95, it's gone to 630 something.  :)
SH> why it would say this, but alas, it does.  So, to make a long story
SH> longer , could this be my problem? Will I have to  either switch
SH> to ANSI.SYS or manually type ANSI.COM (yes, it loads from the 
SH> command line but not from AUTOEXEC.BAT.. Gotta LOVE computers.. :< 
SH> ) to make  MAX work?
 Definitely try Ansi.SYS in Config.sys.  It should take up a mere handful
 of K that way, and it can be loaded high. 
 Patrick
--- timEd 1.10
---------------