Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <3E64E8DA.80601@yahoo.com>
Date: Tue, 04 Mar 2003 12:56:42 -0500
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: cygwin-developers AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin-developers AT cygwin DOT com
Subject: OT - But you need to know
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

I've found a bug in shlwapi.dll which causes cmd.exe to abort.  How it 
gets triggered I'm not sure; but during setup and removal of some 
features of IIS cmd.exe and therefore Cygwin stopped working.  Using 
depends on cmd.exe I found a reference in shlwapi.dll to 
WNetRestoreConnectionA which is not a valid reference. 
WNetRestoreConnectionW exists and RestoreConnectionA exists.  Modifying 
shlwapi.dll to subtitute WNetRestoreConnectionA to 
WNetRestoreConnectionW allows me to work again but obviously isn't a 
correct one.  Now to report this to MS.

Earnie.