From:	"Gary Hubbard" <me AT sandia DOT gov>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Command line wildcard expansion under Win2K
Date:	Tue, 28 Jan 2003 08:18:09 -0800
Organization:	Sandia National Laboratories, Albuquerque, NM USA
Lines:	21
Message-ID:	<b16aeu$ilk$1@sass2141.sandia.gov>
NNTP-Posting-Host:	hubbardpc.ran.sandia.gov
X-Trace:	sass2141.sandia.gov 1043770654 19124 134.252.7.230 (28 Jan 2003 16:17:34 GMT)
X-Complaints-To:	usenet AT sass2141 DOT sandia DOT gov
NNTP-Posting-Date:	Tue, 28 Jan 2003 16:17:34 +0000 (UTC)
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 6.00.2600.0000
X-MIMEOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi,
I am running a DJGPP development system under Win2K.  Now that most of the
Win2K problems have been resolved I am quite happy, but there is one problem
I can't seem to find a reference to anywhere.  I just downloaded everything
recently, so it should be reasonably up to date.

Comman line filename expansions (any presumably others) seem to be case
sensitive.  Thus running a program
    prog *.vec
will fail with a memory access exception (before main() is started) if the
files were written as upper case, say A.VEC and B.VEC.  Running with
   prog *.VEC
will work.

Is this a known problem?  I have not even looked in the library routines
yet.  Do I need NTLFN?

TIA
Gary

- Raw text -