Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 15 Mar 2002 18:38:47 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: cygwin.com suggestions Message-ID: <20020315233847.GB11405@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4.3.1.2.20020315150903.0169bc60@pop.ma.ultranet.com> <3C927E56.2060909@Salira.com> <00fe01c1cc79$e7afc5d0$0100a8c0@advent02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00fe01c1cc79$e7afc5d0$0100a8c0@advent02> User-Agent: Mutt/1.3.23.1i On Fri, Mar 15, 2002 at 11:34:07PM -0000, Chris January wrote: >Under Win NT/2k/XP it is actually possible to replace a DLL file that's >currently in use without rebooting. You rename the existing file to >something else, then copy the new file in its place. Then add the old file >to the MoveFileEx list of files to delete on reboot. That way the new file >is installed straight away. it's possible to install a new version of the cygwin DLL over an in-use version in some cases. However, you'll cause problems for all running cygwin apps if you use this method. It's safer to reboot. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/