From: Brad Campbell <brad@wasp.net.au>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Win2k disk full message
Date: Wed, 16 Jun 2004 09:00:24 +0400 [thread overview]
Message-ID: <40CFD3E8.3090608@wasp.net.au> (raw)
In-Reply-To: <Pine.GSO.3.96.1040615185611.11071B-100000@beach.silcom.com>
Chad Page wrote:
> What messages wind up in the log? Perhaps it's related to the
> very long hardware detection times... we'd be lucky to kill both birds
> with one stone.
>
> - Chad
How do I read the log? I passed a couple of the files through strings but they pretty much came up
blank.
Regards,
Brad
next prev parent reply other threads:[~2004-06-16 5:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 17:49 [Qemu-devel] Win2k disk full message Brad Campbell
2004-06-16 1:56 ` Chad Page
2004-06-16 5:00 ` Brad Campbell [this message]
2004-06-16 22:58 ` Jason Gress
-- strict thread matches above, loose matches on Subject: below --
2004-06-16 7:44 Vladimir N. Oleynik
2004-06-16 7:51 ` Brad Campbell
2004-06-16 8:20 ` Jean-Michel POURE
2004-06-16 8:23 ` Brad Campbell
2004-06-16 8:47 ` Vladimir N. Oleynik
2004-06-16 9:07 ` Jean-Michel POURE
2004-06-16 9:29 ` Vladimir N. Oleynik
2004-06-30 15:00 ` Sebastien Bechet
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=40CFD3E8.3090608@wasp.net.au \
--to=brad@wasp.net.au \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).