X-Spam-Check-By: sourceware.org Message-ID: <4512077D.9050403@cygwin.com> Date: Wed, 20 Sep 2006 23:31:09 -0400 From: "Larry Hall (Cygwin)" Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060727 Fedora/1.5.0.5-1.fc4.remi Thunderbird/1.5.0.5 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: simply cygwin1.dll References: <20060921032007 DOT GA6790 AT ns1 DOT anodized DOT com> In-Reply-To: <20060921032007.GA6790@ns1.anodized.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Christopher Layne wrote: > May seem sort of newbish, but I just noticed that one cannot move cygwin1.dll > into place after removing the old one. For instance, if I download a snapshot > to some tmp directory, exit all cygwin related apps and use explorer to move > the new dll from the tmp to c:\cygwin\bin - I'll get the standard crop of > bad dll related failures. However if I *copy* the file (ctrl-drag) things > work fine. I presume this is some kind of windows dll manipulation thing or > is it just my system? Hard to say without seeing what you're seeing (insert standard plug for here ;-) ). The standard problem when doing what you're doing is forgetting to stop services. Other than that, your basic description fits my modus-operandi for replacing the DLL manually. So perhaps it is just your system. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/