Message-ID: <3600B149.E9C8C9B7@mailexcite.com>
Date: Thu, 17 Sep 1998 02:50:50 -0400
From: Doug Gale <dgale AT mailexcite DOT com>
MIME-Version: 1.0
Newsgroups: comp.os.msdos.djgpp
Subject: Re: LFNS: A newbie like question.
References: <35FFEC7A DOT 65F8E9D4 AT net DOT netunlimited> <36004344 DOT 35C894B1 AT unb DOT ca>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: oshawappp11.idirect.com
Organization: "Usenet User"
Lines: 23
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk



Endlisnis wrote:

> IMJ wrote:
> > Hello all,
> > New to this NG and about the same with DJGPP. My question is about
> > getting programs compiled in DJGPP to support long file names as in W95.
> > Some time ago I wrote a small command line based hex dumping program
> > using mainly the Stdio/Standard C functions. This worked great under
> > DOS, but now I need the LFN support. Could anyone point me in the right
> > direction?. Will I have to completely re-write this program?. I rather
> > liked the formatted output from fprintf()...
>         As long as it uses the standard libraries it should work perfectly under
> DJGPP, and it fully supports long filenames with all of the standard library
> functions. (remember to "SET LFN=y" in your autoexec.bat

Hmm. Just use standard libraries. Ok, so what happens if I DON'T set LFN=Y, like
say, I send the program to someone that isn't a DJGPP programmer, with a nice
autoexec, with LFN=Y?
Maybe load an environment file with that in it or something? I don't really want
users to have to mess with their autoexec.