Mail Archives: djgpp/2003/08/29/09:00:03
"Charles Sandmann" <sandmann AT clio DOT rice DOT edu> wrote in message
news:3f4c17b2 DOT sandmann AT clio DOT rice DOT edu...
> > I have written a utility that operates on a source file and creates a
new
> > target file in the same directory. My OS is Win2K.
> > To use my program, I choose the source file with Disk Explorer, drag it
onto
> > the desktop, and drop it onto a link to my DJGPP-compiled program. The
> > program operates and creates a new file with the same path and file name
as
> > the source, but with a different extension - only the file name gets
> > shortened from
>
> > PathName\MyLongFileName.EFT to
> > PathName\MyLong~1.EFT
>
> 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.
>
> > I also read the installation notes, and I see that long file name
support
> > requires a TSR to be running, but it was not clear to me whether this
was
> > only to allow the files of the DJGPP distribution to have long file
names,
> > or whether it would give LFN support to programs compiled under DJGPP.
>
> 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.
>
>
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
- Raw text -