From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EEkC0-0006Zr-8t
	for qemu-devel@nongnu.org; Mon, 12 Sep 2005 05:01:36 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EEkBg-0006P3-6j
	for qemu-devel@nongnu.org; Mon, 12 Sep 2005 05:01:22 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EEkB0-0005YZ-EZ
	for qemu-devel@nongnu.org; Mon, 12 Sep 2005 05:00:34 -0400
Received: from [211.5.2.69] (helo=nm01omta015.dion.ne.jp)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1EEkBa-0003k2-2H
	for qemu-devel@nongnu.org; Mon, 12 Sep 2005 05:01:10 -0400
Message-ID: <000c01c5b778$71804f40$0464a8c0@athlon>
From: "Kazu" <kazoo@r3.dion.ne.jp>
References: <43248CCD.600@free.fr>
Subject: Re: [Qemu-devel] [patch] TAP and piix4-udma resyncs against
	0.7.2release
Date: Mon, 12 Sep 2005 18:00:37 +0900
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="ISO-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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