Mail Archives: djgpp/1998/07/08/06:00:36
From: | Endlisnis <s257m AT unb DOT ca>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: Long Filenames - can they always be on?
|
Date: | Tue, 7 Jul 1998 20:14:18 -0300
|
Organization: | University of New Brunswick
|
Lines: | 17
|
Message-ID: | <Pine.SOL.3.96.980707201114.12449A-100000@sol.sun.csd.unb.ca>
|
References: | <199807060130 DOT CAA09445 AT sable DOT ox DOT ac DOT uk>
|
NNTP-Posting-Host: | sol-alt1.unb.ca
|
Mime-Version: | 1.0
|
In-Reply-To: | <199807060130.CAA09445@sable.ox.ac.uk>
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
On Mon, 6 Jul 1998, George Foot wrote:
->
->DJGPP functions will use LFNs if possible. You have to be running on
->automatically sets `LFN' to `n' unless you set it otherwise, so put
->"set lfn=y" in your `autoexec.bat' file.
->When you've done that, djgpp's library functions should be able to
->see the long filenames.
I made a program (under djgpp) that took 2 filenames as
commandline parameters. It opens and reads one file, then writes the 2nd
file. If I ask it to open a file and I specify a long-filename, it works,
but if I ask it to write a long-filename, it just truncates it to 8.3
format. This is running without LFN set at all as an environmental
variable. Shouldn't it be able to make long-filenames?
Endlisnis
[I have a pyramid of wingyness]
- Raw text -