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 Message-ID: <00fe01c1cc79$e7afc5d0$0100a8c0@advent02> From: "Chris January" To: References: <4.3.1.2.20020315150903.0169bc60@pop.ma.ultranet.com> <3C927E56.2060909@Salira.com> Subject: Re: cygwin.com suggestions Date: Fri, 15 Mar 2002 23:34:07 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > >>>>2) Include in the FAQ (or somewhere) a section on "How to Safely Update the Cygwin dll". Probably just "shut down all cygwin apps, including daemons", but it would be useful to know for sure. > >>>> > >>>The next release of setup.exe automatically address's this and will > >>>replace in-use .dll's. > >>> > >>Really? How does it do that? Because I was under the impression that if a program was running you cannot replace it's .exe file (or .dll file) because it was opened exclusively by Windows. How do you get around that? > > > > Same way as Windows installers work. Just schedule the DLL to be moved in > > after reboot. > > But that doesn't really replace the current DLL. IOW the changes are not > effective until one reboots. Personally I find this a crummy way to do > things but perhaps that's all that can be done. 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. Regards Chris -- 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/