Date: Mon, 16 Sep 1996 10:45:09 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Cc: i DOT ahmed AT postoffice DOT worldnet DOT att DOT net, djgpp AT delorie DOT com
Subject: Re: DPMI ERROR OMPT: CAN NOT OPEN FILE
In-Reply-To: <9609131406.AA13238@clio.rice.edu>
Message-Id: <Pine.SUN.3.91.960916104019.21681G-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Fri, 13 Sep 1996, Charles Sandmann wrote:

> This error message does not come out of DJGPP or CWSDPMI, so it's a 
> machine configuration error (probably mixed 16-bit/32-bit DPMI with
> some other DPMI provider).

I think it comes from the stub.  The actual text of the error message 
should be this:

	OMPT=: cannot open

It happened to me a few days ago when I tried to run a v2 program on a 
system that has to be booted from a floppy with no CONFIG.SYS and no 
AUTOEXEC.BAT.  I might be wrong in my analysis, but it seemed to me at 
the time that if the environment defines an empty PATH and PROMPT after 
the PATH, that is exactly the message that will come out of the stub.
To reproduce, try to boot a system from a floppy.