Mail Archives: djgpp/2000/12/12/04:31:21
On Mon, 11 Dec 2000, George Snyder wrote:
> The Windows executables available from ftp.simtel.net
> /pub/simtelnet/gnu/djgpp/v2gnu look like 16-bit programs on Windows NT.
> If I load one into DEPENDS.EXE, I get an error message:
>
> No PE signature found. This file appears to be a 16-bit DOS
> module.
DJGPP programs are _not_ Windows executables. They are DOS programs,
albeit 32-bit protected-mode ones.
> One result of running a 16-bit program (even COMMAND.COM) on NT is that
> the command process' current directory gets converted to short filename
> format. Note the directory name in the prompts in the following
> example:
>
> E:\Program Files> \gnu\bin\ls
>
> AverStar Microsoft Visual Studio seti
> Java RadView
> Jikes Visigenic
>
> E:\PROGRA~1>
Why is it important what does the shell prompt display? What's
important is what do library functions such as `getcwd' report. Can
you check what does `getcwd' return when you have ntlfn loaded?
> After this, programs which read the current directory name can go
> wrong. For example, a licensed CM program which gets the current
> directory name and looks that up in a database fails, because the
> database lists the long filename format.
If this indeed happens, it might be a bug in ntlfn, so please provide
a short test program which exhibits the problem.
> Are 32-bit executable versions of the v2gnu programs available?
The FAQ has a pointer to the Cygwin ports in section 3.6.
- Raw text -