From: "Stephen Howe" <SPAMGUARDstephen DOT howe AT dial DOT pipex DOT co DOT uk>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: LFN wildcard expansion in NT
Date: Tue, 3 Oct 2000 19:59:59 +0100
Organization: UUNET WorldCom server (post doesn't reflect views of UUNET WorldCom
Lines: 20
Message-ID: <8rdabe$t5f$1@soap.pipex.net>
References: <4FDF88457C99D31193C900A0C9B41A9F2AC5F5 AT SERVER>
NNTP-Posting-Host: tns254.uk.tnsofres.com
X-Trace: soap.pipex.net 970599598 29871 194.202.213.254 (3 Oct 2000 18:59:58 GMT)
X-Complaints-To: abuse AT uk DOT uu DOT net
NNTP-Posting-Date: 3 Oct 2000 18:59:58 GMT
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com


Kris Price <k DOT price AT domainz DOT net DOT nz> wrote in message
news:4FDF88457C99D31193C900A0C9B41A9F2AC5F5 AT SERVER...

Is there a way to get around this? A setting?
> Or any trick or suggestions?

No. Microsoft has an API for dealing with long filenames so that you can do
similar int 21h calls to those that take short filenames.

But this API only works under Windows 95 and 98 not NT.

So your stuck.

As time matches on, the more Microsoft add new filing systems to Windows,
the less likely you will be able to access advanced features within.

Stephen Howe