Date: Sat, 30 Sep 2000 00:17:04 +0200 From: "Eli Zaretskii" Sender: halo1 AT inter DOT net DOT il To: cat AT animal DOT u-net DOT com Message-Id: <6137-Sat30Sep2000001704+0300-eliz@is.elta.co.il> X-Mailer: Emacs 20.6 (via feedmail 8.2.emacs20_6 I) and Blat ver 1.8.5h CC: djgpp AT delorie DOT com In-reply-to: <39d4ad49$1@news.gemsoft.net> (cat@animal.u-net.com) Subject: Re: Running DJGPP binaries on Ramdisk References: <39d4ad49$1 AT news DOT gemsoft DOT net> 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 Precedence: bulk > From: cat AT animal DOT u-net DOT com > Newsgroups: comp.os.msdos.djgpp > Date: 29 Sep 2000 15:55:05 GMT > > D:\D4>d4x test.afn x=ada#tab_b50 > > OMPT=: cannot open cryptic error message. [snip] > D:\D4>go32-v2 > > OMPT=: cannot open What version of DJGPP do you have installed? For example, what does go32-v2.exe print when invoked with no arguments from a hard disk? > Yes. It's the same error message. Luckily I got the CSDPMI > source so at least I could grep all of the source files for bits of > the message. Nothing to do with the dpmi server. The message comes from the stub loader, a small 2KB DOS program that gets prepended to each DJGPP program. The stub is required because DOS doesn't know how to run COFF executables produced by DJGPP port of the GNU linker. The code which prints this message is looking for the full path of the program's executable file, which is stored in the program's PSP after the environment block. The stub needs the program's pathname because it has to read its code and data into memory, before it passes control to the program's entry point. As someone told you, setting PATH in the environment should work around the problem, but I think that this bug is corrected in the latest versions of DJGPP.