dj delorie

Since DJGPP's programs *are* DJGPP programs (makes sense, yes?) the
TSR (if any) would affect both.

If your friends need LFN support, they'd need the TSR installed also.

charles sandmann

This is probably a feature of the drag/drop interface. It sees the image
is a DOS image, and assumes it doesn't support short names, so helpfully
sends the short name.

If you really want the long name you can try to call one of the LFN
API calls to try and expand it.

LFN TSRs are not required under Windows 2000 or Windows XP if you have
upgraded to the V2.03 refresh or V2.04 alpha test.

eli zaretskii

Yes, this is a misfeature of Windows' interface with DOS programs.

kenton w. mellott

Is the LFN TSR needed if you can access the DOS interrupts with assembly
language? Hans Lunsing wrote some PowerBASIC code for handling long file
names, filed as PBlfn322.zip on web page
http://www.basicguru.com/dikkenberg/dos/pbsrca.html
It is mainly assembly code for getting the DOS interrupts.

Sincerely,

Gregory D. MELLOTT

charles sandmann

The built-in C run-time functions (fopen, etc) work directly with long
names under all platforms which support the long file name DOS interrupts.


This type of code has been available in DJGPP since Windows 95 was released
(about 8 years ago).

kenton w. mellott

Is the TSR to allow one to run in the just DOS (not in a DOS window), and
still have long filename functionality?
<snip>

charles sandmann

There are TSRs for regular DOS which provide long filename functionality
(file system may have long names when booted under Windows 95, for example).

There is a TSR designed to support long names under Windows NT - which
has a native file system that supports long names - but the DOS Window
does not support the long name DOS API.

So in general, if you aren't under DOS or Windows NT you don't need a
TSR for long names.