Mail Archives: djgpp/2000/07/18/04:44:42
On Mon, 17 Jul 2000, Charles Sandmann wrote:
> Complaints about pagetables usually means that there are DOS memory problems.
> It may be out of DOS memory or corrupted bitmaps.
I don't think this is the case.
> In any case, does the bad behavior get shown if you just run CWSDPMI itself
> before the PMODE/DJ image? If not, then the exec code and nesting seems to
> be contributing. If someone would post enough information to diagnose or
> reproduce it in a minimal environment I'd look at it.
I think I sent you all the relevant information back in November, and
you were eventually able to reproduce these problems on your machine.
I can dig out and resend the details, if you need them again.
Here's the last message you sent me about this:
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Subject: Re: Read Me Third: A Short FAQ List (fwd)
To: eliz AT gnu DOT org (Eli Zaretskii)
Date: Mon, 15 Nov 1999 19:29:39 -0600 (CST)
In-Reply-To: <199911152110 DOT QAA10559 AT mescaline DOT gnu DOT org> from "Eli Zaretskii" at Nov 15, 99 04:10:33 pm
Content-Type: text
Content-Length: 467
I can reproduce your error. After the error it is very interesting.
I see CWSDPMI loaded in memory, DPMI appears to be available,
cwsdpmi -u executes fine, but any djgpp image indicates there is no
DPMI memory.
So, it still thinks it's nested inside CWSDPMI, and no DPMI memory is
available. Fascinating.
- Raw text -