Date:	Mon, 23 Jul 2001 14:42:44 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: Sabotage!
In-Reply-To:	<3b5bc11d.87603499@news.primus.ca>
Message-ID:	<Pine.SUN.3.91.1010723144049.18357D-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 23 Jul 2001, Graaagh the Mighty wrote:

> >This message comes from the stub loader.  It means that a call to the
> >PM entry procedure failed.  Every DJGPP program calls the PM entry
> >procedure during startup to switch to protected mode.  The PM entry
> >procedure's address is returned by the DPMI host in response to a call
> >to function 1687h of Int 2Fh.
> 
> You're saying whatever he did made PM *unavailable*?

Something like that: it made the function called to enter PM fail.  But 
that function is only used by DPMI programs, so it's not like PM is 
disabled for all the programs (which would be a much larger disaster).

The problem is that such a failure could be caused by a number of
reasons, and the PM entry call doesn't return enough information to
tell what exactly was wrong.

> What could possibly cause that?

I have no idea.  This is the first time I hear about such a problem on
Windows 9X.

> >It can also be that the selectors in that DOS box were all exhausted,
> >due to the fact that Windows 9X leaks selectors like a sieve.  Or
> >maybe some other resource required for DPMI was exhausted.
> 
> Surely it doesn't leak when it's *idle*?

No, of course not.  I was thinking about something that person did
which exhausted the resources while you were away.

It's very strange, either way.

- Raw text -