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 X-Injected-Via-Gmane: http://gmane.org/ To: cygwin AT cygwin DOT com From: =?ISO-8859-1?Q?Sven_K=F6hler?= Subject: Re: setup.exe and "in-use-file" Date: Mon, 14 Apr 2003 03:27:10 +0200 Lines: 42 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT main DOT gmane DOT org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: de, en In-Reply-To: > Sven- > Sven- Martin- Martin- > To put in your new DLL to replace the DLL which is currently running you > will have to find the Cygwin task that is using the DLL and kill it so the > process will release it's lock on resources that it is using... I already know that, i hopefully didn't write anything, that lead people to the conclusion, that i want setup.exe to do that. > Make Sense? Sure, but that's still not what i'm talking about! setup.exe currently does the follwoing to write a file: 1. open destination.file successful: jump to 2 error: jump to 3 2. write content, close file and jump to 4 3. write content to another file, and tell windows to replace the destination-file on next reboot. 4. process next file all i want setup.exe to do, is the following 1. same as step 1 above 2. same as step 2 above 3a. inform user, that file cannot be opened for writing because it is in use and ask the user, if setup.exe should retry user chooses YES: goto step 1 user chooses NO: goto step 3b 3b. same as step 3 above 4. same as step 4 above of course it would be nice to know which process is using the file, but that's not what i'm talking about! i'm just want setup.exe to avoid reboots by __interacting__ with the __user__!!! -- 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/