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
Message-ID: <3C9F8EA6.5080404@ece.gatech.edu>
Date: Mon, 25 Mar 2002 15:55:02 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: Michael A Chase <mchase AT ix DOT netcom DOT com>,
   CygWin-Apps <cygwin-apps AT cygwin DOT com>
Subject: Re: release setup now?
References: <FC169E059D1A0442A04C40F86D9BA7600AFDED AT itdomain003 DOT itdomain DOT net DOT au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Michael's script works for me.  One caveat:

I had to manually run 'clean_lst.pl ./a*.lst' 26 times (using different 
starting letters).  However, that was because I got a BSOD when running 
it fullbore -- where it tried to fixup all files.

Now, a perl script should never ever be able to cause a BSOD on W2K. 
Neither should a user-mode program (like setup.exe)  However, on my 
machines, both do on rare occasions.  The error is down deep in ntoskrnl 
  and/or the ntfs file system driver -- I even did a full reinstall of 
the OS, yet I still get the BSOD sometimes.  It's an MS bug, I am sure 
-- and I've noticed that it only happens when there are a lot of files 
being opened and closed rapidly. (For instance, when uninstalling lots 
of files in an old package, and installing lots of files in the new 
replacement package.  Or when opening each .lst and rewriting them 
without \000 chars.)

So, I don't blame Michael's script for my BSOD.  I blame MS.  But, once 
I limited the number of open/modified files per run (by running the 
script by hand on each letter of the alphabet) Michael's script DID 
successfully remove the \000 chars.

--Chuck

Robert Collins wrote:

> I'd already done a reinstall... can someone here validate Michael's
> script? (someone that tried the beta and has not reinstall those
> packages..)
> 
> Rob