public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gary R Van Sickle" <tiberius@braemarinc.com>
To: "Cygwin Mailing List (E-mail)" <cygwin@sourceware.cygnus.com>
Subject: Re: tar 'mini'-bug
Date: Thu, 09 Aug 2001 11:14:00 -0000	[thread overview]
Message-ID: <000801c120ff$0d62e9a0$2101a8c0@nomad> (raw)

>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/

             reply	other threads:[~2001-08-09 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 11:14 Gary R Van Sickle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-08 12:27 Troy Noble
2001-08-08 14:41 ` Gary R Van Sickle
2001-08-08 15:32   ` Corinna Vinschen
2001-08-09  1:49   ` David Starks-Browning
2001-08-08 12:01 Gary R Van Sickle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000801c120ff$0d62e9a0$2101a8c0@nomad' \
    --to=tiberius@braemarinc.com \
    --cc=cygwin@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).