From:	"Kris Price" <k DOT price AT domainz DOT net DOT nz>
Newsgroups:	comp.os.msdos.djgpp
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1001003075128 DOT 10028D-100000 AT is>
Subject:	Re: LFN wildcard expansion in NT
Date:	Wed, 4 Oct 2000 09:44:00 +1300
Lines:	33
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
NNTP-Posting-Host:	202.49.152.2
X-Original-NNTP-Posting-Host:	202.49.152.2
Message-ID:	<39da48ab@news.actrix.gen.nz>
X-Trace:	4 Oct 2000 09:59:23 NZST, 202.49.152.2
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Ahh, thanks for clearing that up. A sad thing to live with, but oh well. =)

Thanks
Kris

> > 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.

[snip]

> 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 -