Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Gary R Van Sickle" To: "Cygwin Mailing List (E-mail)" Subject: Re: tar 'mini'-bug Date: Thu, 9 Aug 2001 13:13:54 -0500 Message-ID: <000801c120ff$0d62e9a0$2101a8c0@nomad> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Importance: Normal >On Wed, Aug 08, 2001 at 04:40:28PM -0500, Gary R Van Sickle wrote: >> Mmmm, I think you're wrong on that. I believe ME, crappy as it is, gets >> this one thing right and behaves the same as Why2K in that respect, in that >> you can't write to an executable file that's in use by the OS. I'm not at a > >Excerpt from MSDN: > > Windows 95/98/Me: The DeleteFile function deletes a file even if it > is open for normal I/O or as a memory-mapped file. To prevent loss > of data, close files before attempting to delete them. > > Windows NT/2000 or later: The DeleteFile function fails if an > application attempts to delete a file that is open for normal I/O > or as a memory-mapped file. Jesus Cobble-job Christ. Just when you think Win9x can't get any worse. I suppose one could try a CreateFile() with write access before the delete, assuming THAT would fail (which is of course a nebulous assumption). Or simply wait for the XP forced upgrade to deliver its whole new bag of oddball behavior in a few months. Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 -- 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/