qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] TAP and piix4-udma resyncs against 0.7.2release
Date: Mon, 12 Sep 2005 18:00:37 +0900	[thread overview]
Message-ID: <000c01c5b778$71804f40$0464a8c0@athlon> (raw)
In-Reply-To: 43248CCD.600@free.fr

Monday, September 12, 2005 5:00 AM Mad Monkey wrote:

> 2/ Attached are the resyncs against 0.7.2 release for :
> - the TAP device support 
> (http://www.h6.dion.ne.jp/~kazuw/qemu-win/qemu-0.7.1-tap.zip)
> - the PIIX4 BusMaster ATA (UltraDMA/33) support 
> (http://ebisa.hp.infoseek.co.jp/qemu/arcs/qemu-piix4-udma-20050514.zip)

I will update them. But the DMA patch has a problem.

Monday, August 29, 2005 3:56 PM Brad Campbell wrote:

> Interesting.. after applying that patch both my win2k and winxp installs
> refused to boot.
> Winxp gets as far as the safe mode selection screen, select safe mode and
> it goes straight back to the selection screen. Win2k just bluescreens
> during the boot process mumbling something about being unable to access
> the boot disk.
>

For WinXP, it was the same state I have experienced when I installed WinXP
without a patch. I don't think it is related to the patch.

For Win2k, I also see the same blue screen. It says that 
INACCESSIBLE_BOOT_DEVICE. I couldn't find why.

Regards,
Kazu

      parent reply	other threads:[~2005-09-12  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 20:00 [Qemu-devel] [patch] TAP and piix4-udma resyncs against 0.7.2 release Mad Monkey
2005-09-12  6:28 ` Mad Monkey
2005-09-12  9:00 ` Kazu [this message]

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='000c01c5b778$71804f40$0464a8c0@athlon' \
    --to=kazoo@r3.dion.ne.jp \
    --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).