Date:	Thu, 24 Oct 1996 14:31:31 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Dave Pearson <davep AT hagbard DOT demon DOT co DOT uk>
Cc:	djgpp AT delorie DOT com
Subject:	Re: Win95 LFNs With v2.01 (Changes?)
In-Reply-To:	<slrn56rmuq.41.davep@hagbard.demon.co.uk>
Message-Id:	<Pine.SUN.3.91.961024142248.9865K-100000@is>
Mime-Version:	1.0

On Wed, 23 Oct 1996, Dave Pearson wrote:

> I don't know that it's a "bug" as such, but I can't find anything that
> documents the change so I was wondering if somone could point me in
> the direction of any details, or perhaps clear up the "problem"?

Read the `_use_lfn' section of the libc reference (libc.inf).  Various 
other aspects of LFN support are explaned in the following sections of 
the libc reference:

	_crt0_startup_flags
	glob
	_preserve_fncase

Or just search the reference for "LFN".

> With 2.0, any of my code that I ran under Win95 would happily open
> long file names no matter what the setting of LFN was. With 2.01 it
> seems that the setting of LFN makes a big difference. Is this correct?

If LFN is set to N, it disables the LFN support on Windows 95.  That is 
how it should behave.  Why is it a bug to behave according to the what 
the user says?

> If I compile this with 2.0, and LFN is not in the environment and in
> ~djgpp/djgpp.env LFN is set to N (and DJGPP points to it) it will
> happily open a long file name. With 2.01 it won't,

That was a bug in v2.0.  Now it is corrected (I hope).

> I either have to
> set LFN to 'y' in the environment, set LFN to 'y' in ~djgpp/djgpp.env
> or unset DJGPP.

You can also delete the line in DJGPP.ENV which sets LFN, then you will 
have LFN support, because DJGPP will query the filesystem to see whether 
LFN is supported and enable it by default if it is.

- Raw text -