Date:	Tue, 3 Oct 2000 07:51:54 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Kris Price <k DOT price AT domainz DOT net DOT nz>
cc:	djgpp AT delorie DOT com
Subject:	Re: LFN wildcard expansion in NT
In-Reply-To:	<4FDF88457C99D31193C900A0C9B41A9F2AC5F5@SERVER>
Message-ID:	<Pine.SUN.3.91.1001003075128.10028D-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 3 Oct 2000, Kris Price wrote:

> Just new to using DJGPP, I'm finding the wildcard expansion extremely useful
> when passing arguements to programs I write, however they always get
> converted to the short 8.3 format (using WinNT)

Long file names are simply not visible to DJGPP applications running
on NT.  So there's no way wildcards can be expanded to long file
names: the OS doesn't let the program see them.

> as in I need to pass the wildcards as wildcards of the short
> versions, not of the long versions, I don't mind so much if they're
> converted from there into short versions

Sorry, I don't understand what are you saying here.

> but it'd really make things a lot easier if I could just pass them
> in the long version on the command line.

What good will it be to pass long file names if the DJGPP program
cannot access them?

Also, why is it important to pass the long names?  After all, the
short ones point to the same files, right?

> Is there a way to get around this?

No.

> A setting?  Or any trick or suggestions?

Complain to Bill Gates.  Or switch to Windows 2000, where long file
names are visible to DJGPP applications (but you get a problem with
nested DJGPP programs as a bonus).

- Raw text -