Date:	Mon, 24 Nov 1997 14:54:45 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: Possible enhancements on v2.02
In-Reply-To:	<347972A6.4162@rug.ac.be>
Message-ID:	<Pine.SUN.3.91.971124144623.23713o-100000@is>
MIME-Version:	1.0

On Mon, 24 Nov 1997, Vik Heyndrickx wrote:

> >      1) Is it a good idea to turn LFN support on Windows 95 *before*
> >         DJGPP.ENV is read. 
> 
> How are you going to do that from within v2.02?

I thought about setting the flag that makes libc use LFN API right from 
the start.  Then LFN=n in the environment, if present, will turn it off, 
but by that time we had already processed DJGPP.ENV.

> >                                            The changes in dosexec are
> >         minor, but I wonder whether they could break anything.
> 
> Make sure you make them right

That's what you, and the rest of beta-testers, are for ;-).

> take the following names in mind:
> 
> .netsc.vik
> vik.netsc.

I'm missing something here.  What's so special about these?

What I thought about (and almost finished writing) is that given a 
program name, first try appending all the known executable extensions
and look for a file with those names.  If none is found, try without
appending the extensions.

So, in your example, it will look for these, in the order shown:

	.netsc.vik.com
	.netsc.vik.exe
	.netsc.vik.bat
	.netsc.vik.btm
	.netsc.vik.sh
	.netsc.vik.ksh
	.netsc.vik.pl
	.netsc.vik.sed
	.netsc.vik

Okay?

> BTW the later is equivalent to 'vik.netsc' under W95

Only with LFN=n.  When LFN is supported, you get .netsc.vik as on Unix.

- Raw text -