X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,TW_RW,TW_WX,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: sourceware.org Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes To: cygwin@cygwin.com Subject: Re: Setup 2.693 unable to replace files through reboot References: <4BBB8CE6.2090203@gmail.com> <4BBC44B9.3000505@gmx.de> Date: Wed, 07 Apr 2010 12:46:57 +0300 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Matthias Andree" Message-ID: In-Reply-To: <4BBC44B9.3000505@gmx.de> User-Agent: Opera Mail/10.51 (Win32) X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com >> a) can't work on network drives >> b) needs write access to the registry key: >> "HKLM\SYSTEM\CurrentControlSet\Control\Session >> Manager\PendingFileRenameOperations" >> c) may fail if "the System volume is a basic volume [ ... and ... ] the >> destination drive or the source drive is located on a dynamic volume" Further information, this Key appears to exist only if such operations are actually pending. I triggered a re-install of cygwin 1.7.3-1 again, and got this in the key: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager] ... "PendingFileRenameOperations"=hex(7):5c,00,3f,00,3f,00,5c,00,43,00,3a,00,5c,00,\ 63,00,79,00,67,00,77,00,69,00,6e,00,5c,00,62,00,69,00,6e,00,5c,00,63,00,79,\ 00,67,00,77,00,69,00,6e,00,31,00,2e,00,64,00,6c,00,6c,00,2e,00,6e,00,65,00,\ 77,00,00,00,21,00,5c,00,3f,00,3f,00,5c,00,43,00,3a,00,5c,00,63,00,79,00,67,\ 00,77,00,69,00,6e,00,5c,00,62,00,69,00,6e,00,5c,00,63,00,79,00,67,00,77,00,\ 69,00,6e,00,31,00,2e,00,64,00,6c,00,6c,00,00,00,5c,00,3f,00,3f,00,5c,00,43,\ 00,3a,00,5c,00,63,00,79,00,67,00,77,00,69,00,6e,00,5c,00,75,00,73,00,72,00,\ 5c,00,73,00,62,00,69,00,6e,00,5c,00,63,00,79,00,67,00,73,00,65,00,72,00,76,\ 00,65,00,72,00,2e,00,65,00,78,00,65,00,2e,00,6e,00,65,00,77,00,00,00,21,00,\ 5c,00,3f,00,3f,00,5c,00,43,00,3a,00,5c,00,63,00,79,00,67,00,77,00,69,00,6e,\ 00,5c,00,75,00,73,00,72,00,5c,00,73,00,62,00,69,00,6e,00,5c,00,63,00,79,00,\ 67,00,73,00,65,00,72,00,76,00,65,00,72,00,2e,00,65,00,78,00,65,00,00,00,00,\ 00 Or, more readably: \??\C:\cygwin\bin\cygwin1.dll.new !\??\C:\cygwin\bin\cygwin1.dll \??\C:\cygwin\usr\sbin\cygserver.exe.new !\??\C:\cygwin\usr\sbin\cygserver.exe However, after a reboot I still have these files: $ ls -l /bin/cygwin1.dll* -rwxr-xr-x 1 Administratoren None 2.5M 2010-04-03 11:29 /bin/cygwin1.dll* -rwxr-xr-x 1 mandree root 2.5M 2010-04-03 11:29 /bin/cygwin1.dll.new* $ ls -l /usr/sbin/cygserver.exe* -rwxr-xr-x 1 mandree root 150K 2010-04-03 11:29 /usr/sbin/cygserver.exe* -rwxr-xr-x 1 mandree root 150K 2010-04-03 11:29 /usr/sbin/cygserver.exe.new* I would have thought that the .new files were gone after the reboot, or these got somewhat more appropriate owners (I always run setup.exe as Administrator, and have it install "for all users")... -- Matthias Andree -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple