Mail Archives: djgpp/1996/08/20/13:10:51
Xref: | news2.mv.net comp.os.msdos.djgpp:7670
|
From: | lehmann AT mathematik DOT th-darmstadt DOT de (Alexander Lehmann)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | rsxtndj and long filenames
|
Date: | 20 Aug 1996 13:33:00 GMT
|
Organization: | Technische Hochschule Darmstadt
|
Lines: | 31
|
Message-ID: | <4vceqc$p2i@rs18.hrz.th-darmstadt.de>
|
NNTP-Posting-Host: | fb0408.mathematik.th-darmstadt.de
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hello all,
I now gave rsxntdj a try and compiled my gif2png utility with it. This
seems to work rather well (though I had the impression the program ran
slower than with the djgpp libs in dpmi), I only noticed a strange
thing. I have compiled the program as a rsxio application which means
that is opens a window that acts as as console and it works with LFN
if I call the program from the command line (no wildcards, though),
but when I put the program's icon onto the desktop and drag a
selection of file onto it, it first opens a MSDOS console window with
gif2png as title and then the rsxio window. In this case, the
filenames are passed as munged names to the application (file~1.xxx),
so apparently Windows thinks that the application is for Windows 3.x
and doesn't recognize it as a LFN capable application.
I have no idea how to investigate this problem (and I'd rather not
learn Windows programming, the fact that djgpp is quite unixy is IMHO
the best part of it :-). But maybe someone has an idea. I think Win95
decides if an application is LFN capable by some kind of version
number that is in the executable header.
bye, Alexander
PS. I should mention that I have tested this in Win95, not in NT.
--
Alexander Lehmann, | "On the Internet,
alex AT hal DOT rhein-main DOT de (plain, MIME, NeXT) | nobody knows
lehmann AT mathematik DOT th-darmstadt DOT de (plain) | you're a dog."
<URL:http://www.mathematik.th-darmstadt.de/~lehmann/>
- Raw text -