To: Bill Davidson <bdavidson AT ra DOT isisnet DOT com>
Cc: Stephen Turnbull    <turnbull AT shako DOT sk DOT tsukuba DOT ac DOT jp>,
        djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Ramdrive 
Date: Mon, 09 Jan 95 15:25:27 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>

> GO32=ansi nodpmi

Do you also have ANSI.SYS or its substitute installed?  If you
do, try running Info without it, or with another ANSI.SYS
work-alike.  If you don't, remove ``ansi'' from GO32 environment
variable, and run Info then.

Btw, you don't have to use ``nodpmi'' if you don't install
QDPMI.

> SHELL=C:\QEMM\LOADHI.COM /RF C:\COMMAND.COM C:\ /E1024 /P
                                                  ^^^^^^
This should be /E:1024.  Is it a typo?  If not, try running Info
after correcting it.  Also try enlarging this value to, say, 1536.

Another thing to try is to set the topline parameter, like this:

	set GO32=topline

(if you need ``ansi'', just add it, like this:

	set GO32=ansi topline
), then rin Info until it crashes, while looking at the far right corner
of the screen.  The seconds and the third items from the right are the
remaining and the used physical memory, respectively.  Check if the
program crashes when the physical memory is exhausted, and tell us if
it is indeed so.  Do the same when RAMDRIVE is not loaded and tell us
about the results.

> Unsupported INT 0x0d
> General Protection Fault at eip:4e14
> (regs and call traceback)

Failing all the above, post that regs and call traceback you
get, and I will try to see where does the program bomb.  If
you know how to run symify, and have the Info sources installed,
you might want doing it yourself.

> I know this problem is not earth-shattering, but it is annoying!

Don't hesitate to press for a solution: as long as you use standard
DOS tools, this is a bug that should be found and solved.