From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Command line wildcard expansion under Win2K
Date:	Thu, 30 Jan 2003 10:28:40 CST
Organization:	Rice University, Houston TX
Lines:	29
Message-ID:	<3e3952b8.sandmann@clio.rice.edu>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1030130095126 DOT 2797A-100000 AT is> <b1bhk0$q4g$1 AT sass2141 DOT sandia DOT gov>
NNTP-Posting-Host:	clio.rice.edu
X-Trace:	joe.rice.edu 1043944466 9637 128.42.105.3 (30 Jan 2003 16:34:27 GMT)
X-Complaints-To:	abuse AT rice DOT edu
NNTP-Posting-Date:	30 Jan 2003 16:34:27 GMT
X-NewsEditor:	ED-1.5.9
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

> These are long
> filenames and are entirely a mixture of upper case letters and numbers.  My
> program's users were trying to access these files, using wildcards, with
> lower case letters.  

If you can provide an example with the input pattern all lower case 
characters (and wildcards) which doesn't match, it's a bug.  

A file name, and behavior from djecho would be great.

> Presumably this was simply to avoid using the shift
> key.  Of course, that would work for any native Microsoft provided program,
> such as dir.  The wildcard pattern matched no files at all.  Changing to
> upper case worked around that problem.

This is the exact opposite behavior of what I would expect - all lower
case should work - all upper case should fail (unless the file was all
upper case).

> It is possible that something else is going on here, like Microsoft
> attempting to provide 8.3 versions of the names as well when
> findfirst/findnext is executed.  I will have to experiment.

There is a known bug in V2.03 that some all uppercased files will not
be lowercased under Win2K due to bugs in the LFN to SFN API.  This
is fixed in the next release.  I'm not sure if this would cause this
problem.  Again, very anxious to see a file name and pattern  which
doesn't work right.

- Raw text -