Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: "Robert C. Paulsen, Jr." <paulsen AT imailbox DOT com>, djgpp AT delorie DOT com
From: Nate Eldredge <nate AT cartsys DOT com>
Subject: Re: LFN=N???
Date: Thu, 21 May 1998 22:51:06 -0700
Message-ID: <19980522055054.AAE29314@ppp112.cartsys.com>
Precedence: bulk

At 01:35  5/21/1998 GMT, Robert C. Paulsen, Jr. wrote:
>BrianR3572 wrote:
>> 
>> Can someone answer why in the ^*^)&%$^!* LFN is set to N by default??!?!!?
>> That seems like the dumbest thing I've ever seen.
>
>That had me going for a while, too! That and calling out the wrong file
>name for some library file.  The answers are in the readme (somewhere),
>but there is a *lot* of readme-like info with the package so it doesn't
>jump out at you. 
>
>Why is is set "wrong"? -- Some people are using DOS w/o Win95 or are
>using NT which doesn't support long file names for DOS programs so the
>LFN setting will be wrong for someone no matter which way it is set. (My
>guess is that the people w/o LFN support are in the minority and perhaps
>the shipped setting should be changed but I don't really know.)

Actually, LFN=Y will simply allow the library to check for an LFN interface
and use it if it's available. Vanilla MS-DOS will fail this test, so you'll
be left with good old 8+3 there.

You have probably seen from other threads that LFN was not considered
sufficiently well-tested to be enabled by default when 2.01 was released.

Nate Eldredge
nate AT cartsys DOT com