Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
Subject: open-file replacements with win9x
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Sun, 21 Apr 2002 15:24:20 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5EA7@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Cygwin-Apps" <cygwin-apps AT sources DOT redhat DOT com>, <cygwin-xfree AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3L5OPK23437

We've got a problem folks:

From MSDN

===
To rename or delete a file on Windows 95/98/Me 

Check for the existence of the WININIT.INI file in the Windows
directory. 
If WININIT.INI exists, open it and add new entries to the existing
[rename] section. If the file does not exist, create the file and create
a [rename] section. 
Add lines of the following format to the [rename] section: 
DestinationFileName=SourceFileName
Both DestinationFileName and SourceFileName must be short file names. To
delete a file, use NUL as the value for DestinationFileName. 
===

Note that both files must be shortnames. I had _assumed_ that the OS
would preserve the attached long file name. But (as the list records
show)... I had not been able to test it to see that this was indeed the
behaviour we would get.

If anyone with a 16 bit windows box out there has the time to do some
test cases and see if my assumption was wrong, or if the current
reported case was a fluke that went wrong, that would be great.

As to _why_ 600 odd files needed replacing, I've yet to look closely at
that aspect.

Rob