*-* In a message dated 02 Nov 97  02:13:14, Patrick said this to Stewart 
Honsberger *-*
*-* about Max *-*
 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
 PM> Try Ansi.sys loaded via your config.sys file.
 PM> I.e.  DEVICEHIGH=C:\DOS\ANSI.SYS /X
I'll try that. (Rather - I'll switch back to that)
 SH> 5 - 6  year old 386 SX-33 w/4 meg ram, it's likely age.. :<  ) when
 PM> Max should work OK under that setup; that's close to what I used
 PM> when I began.  Slow but it does the job.  Forget QEMM, though.  Tried
 PM> it under my version of the same setup and had nothing but troubles.
 PM> Real RAM is much more useful, IMO.
Hmm.. I've noticed that it reports a lot of problems that it "didn't cause" 
but when I don't run it, I don't get nearly as many errors.. Curious Eh?
 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
 PM> Not enough memory for Ansi?  What are you loading that's taking
 PM> up so much???  Even with a full load of junk in Config.sys, I'd get
 PM> 595K conventional free... under Win95, it's gone to 630 something.
I don't know. It loads from the command line, but it refuses to load from 
Autoexec.Bat, if anyone can figure out WHY, I'd really love to know. 
ctually,
it might be because it loads high (via Memmaker's settings) in Autoexec, and 
from the command-line it loads into conventional. Maybe Memmaker's already 
used up all my High RAM?
E-Mail - blackdeath@tinys.oix.com  ICQ# 3484915
... Confucius say: He who sniffs Coke, drowns
-!- Tag-O-Matic V.13 [20139 Taglines] [Quoted 41%]
--- Blue Wave/DOS v2.30 [NR]
---------------