X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: Rugxulo <rugxulo AT gmail DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Bug in findfirst/findnext: mangles certain characters.
Date: Wed, 3 Mar 2010 13:26:56 -0800 (PST)
Organization: http://groups.google.com
Lines: 18
Message-ID: <eb282920-3da3-4a18-b88f-8f985d714873@q21g2000yqm.googlegroups.com>
References: <2PydnQe72P4H_BrWnZ2dnUVZ_vmdnZ2d AT giganews DOT com> 
	<hmbvg7$ieq$1 AT speranza DOT aioe DOT org> <Br-dnQ3aTcaMsRfWnZ2dnUVZ_uSdnZ2d AT giganews DOT com> 
	<4b8ba6a1 AT news DOT x-privat DOT org> <OKSdnaHEbqHx8BPWnZ2dnUVZ_h2dnZ2d AT giganews DOT com> 
	<3efa6f5b-92ae-4e91-b4f7-cb3e8cb9f772 AT f35g2000yqd DOT googlegroups DOT com> 
	<83ocj52mcr DOT fsf AT gnu DOT org>
NNTP-Posting-Host: 65.13.115.246
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Trace: posting.google.com 1267651616 14408 127.0.0.1 (3 Mar 2010 21:26:56 GMT)
X-Complaints-To: groups-abuse AT google DOT com
NNTP-Posting-Date: Wed, 3 Mar 2010 21:26:56 +0000 (UTC)
Complaints-To: groups-abuse AT google DOT com
Injection-Info: q21g2000yqm.googlegroups.com; posting-host=65.13.115.246; 
	posting-account=p5rsXQoAAAB8KPnVlgg9E_vlm2dvVhfO
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) 
	Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729),gzip(gfe),gzip(gfe)
Bytes: 2291
X-Original-Bytes: 2248
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Hi,

On Mar 3, 2:15=A0pm, Eli Zaretskii <e DOT  DOT  DOT  AT gnu DOT org> wrote:
> > From: Rugxulo <rugx DOT  DOT  DOT  AT gmail DOT com>
> > Date: Wed, 3 Mar 2010 11:12:09 -0800 (PST)
>
> > "cmd /c dir /x" will show
> > a completely random (and different but *valid* "7CE5~1.TXT" in my
> > case ...) SFN unlike what DOS apps show ("command /c dir").
>
> SFNs are something entirely different, and unrelated. =A0findfirst
> returns the _long_ file name (by default, unless you disable LFNs by
> setting USE_LFN=3Dn in the environment).

I think you mean "set LFN=3Dn" here. And either way, it doesn't work.
The SFN as returned by 4E,4F is incorrect, "a.txt" doesn't exist. So
NTVDM is returning the wrong thing, but CMD (as a native Win32 app) is
able to know the true SFN (which doesn't help us).