Date: Wed, 11 Jan 1995 05:10:43 -0400 (AST)
From: Bill Davidson <bdavidson AT ra DOT isisnet DOT com>
Subject: Re: Ramdrive 
To: Stephen Turnbull <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu



On Wed, 11 Jan 1995, Stephen Turnbull wrote:

> 
> Well, QEMM *should* know about Hercules video, but maybe it doesn't.
> Or maybe that "Hercules-compatible" video isn't.  Maybe QEMM is trying
> to fill some high RAM with EMS, and it's conflicting with the card.

Quarterdeck Manifest correctly reports the video segment, so I am pretty 
sure that isn't the problem.  Also, no other EMS using programs generate 
problems.  Finally, I still don't see how this would interact with 
RAMDRIVE.SYS (or combi...).  I mean, without RAMDRIVE loaded a problem 
with EMS mapping should still show up.
I have decided I can live without RAMDRIVE (or combi) in my djgpp 
configuration (maybe try again with more RAM, but there is a lot of weird 
sh*t going on here...).
Incidentally, the docs for combi indicate that it can use HMA even if 
other programs (eg DOS) also use HMA, which is contrary to everything I 
have read, especially in QEMM docs.  I tried it, evem though I have
DOS=HIGH
in my config.sys, which puts DOS buffers in HMA.  There seems to be lots 
of room in the HMA, but booting in that config and using and PM prog 
either hangs my system or generates an exception 13.  I suggest you avoid 
this combination!
Thanks again for the help.
Bill Davidson
bdavidson AT ra DOT isisnet DOT com