public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: cygwin@cygwin.com
Subject: Re: Fork errors
Date: Thu, 7 Sep 2023 22:02:04 -0700	[thread overview]
Message-ID: <d73c10eb-cf43-a0d0-1246-3ea6eebd927e@maxrnd.com> (raw)
In-Reply-To: <CANV9t=SwU2cmxWxfKvgfb7eFL0CwgWnq60TmgPmSatGJvAcwTw@mail.gmail.com>

Bill Stewart via Cygwin wrote:
> On Wed, Sep 6, 2023 at 5:32 PM Mark Geisert wrote:
> Speculation: The specific exit code 0xC0000142 may or may not have
>> something to do
>> with Windows error 142, which is ERROR_BUSY_DRIVE.  I cannot help further
>> on this.
> 
> Correction: The low word of 0xC0000142 = hex 142 = decimal 322 =
> ERROR_DEVICE_NO_RESOURCES ("The target device has insufficient resources to
> complete the operation").

D'oh! Tnx for correction.

..mark

  reply	other threads:[~2023-09-08  5:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 18:51 Dale Lobb
2023-09-06 21:00 ` Jose Isaias Cabrera
2023-09-06 21:03   ` Jose Isaias Cabrera
2023-09-08 21:35     ` EXTERNAL SENDER: " Dale Lobb
2023-09-08 21:30   ` Dale Lobb
2023-09-06 23:32 ` Mark Geisert
2023-09-07 15:20   ` Bill Stewart
2023-09-08  5:02     ` Mark Geisert [this message]
2023-09-08 22:02   ` EXTERNAL SENDER: " Dale Lobb
2023-09-09  7:26     ` Mark Geisert
  -- strict thread matches above, loose matches on Subject: below --
2018-04-03 15:20 fork errors Simon Matthews
2018-04-03 20:40 ` Marco Atzeri
2018-04-03 21:12   ` Jürgen Wagner
2018-04-04  3:06     ` Simon Matthews
2018-04-04  5:28       ` Simon Matthews
2018-04-03 23:09 ` Tatsuro MATSUOKA
2000-04-07  5:28 Earnie Boyd
2000-04-06 14:28 Ron Huber
2000-04-06 13:32 Ron Huber

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=d73c10eb-cf43-a0d0-1246-3ea6eebd927e@maxrnd.com \
    --to=mark@maxrnd.com \
    --cc=cygwin@cygwin.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).