Date: Fri, 6 Jan 1995 04:57:18 -0400 (AST)
From: Bill Davidson <bdavidson AT ra DOT isisnet DOT com>
Subject: Ramdrive
To: djgpp AT sun DOT soe DOT clarkson DOT edu

I recently got djgpp off the net and I love it, but the texinfo reader 
that allows me to read the docs crashes if I have the MSDOS RAMDRIVE.SYS 
loaded.  I tried loading it high (with QEMM) and loading it low; I set it 
up to use EMS for the ramdisk.  The funny part is that (so far as I know) 
the info reader doesn't use the ramdrive!  I want to use a ramdrive for 
the compiler intermediate files, and that seems to work OK, but it is a 
pain to have two different environments, one for compiling and one to 
read the docs.  Does anyone know hat gives?  The errors I get are 
protection faults from go32, or if I have QDPMI loaded I get memory 
errors from that.  I use MSDOS 6.2 (no windoze).  Any help would be 
appreciated.
Also, just as an aside, I am in the habit of using the Norton Commander 
file viewer to "look inside" executables before I run them for the first 
time.  This often lets me see potential error messages, expected command 
lines, etc., and just get an idea of what a file is going to do.  Many of 
the djgpp files contain, in their data segment, an image of a portion of 
someone's QEMM directory.  I mean, it is a perfect image; the Norton 
Utilities sector editor/viewer, when pointed at that part of the file, 
displays a directory listing with attributes, file names, starting 
cluster numbers, etc.  Does anyone know why this junk is in those files?  
I got them from the oak AT oakland DOT edu site.