From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BaKuD-00056K-KO for qemu-devel@nongnu.org; Tue, 15 Jun 2004 16:51:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BaKuC-000568-2H for qemu-devel@nongnu.org; Tue, 15 Jun 2004 16:51:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BaKuB-000565-Vk for qemu-devel@nongnu.org; Tue, 15 Jun 2004 16:51:40 -0400 Received: from [204.127.202.55] (helo=sccrmhc11.comcast.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BaKtB-0003U9-BZ for qemu-devel@nongnu.org; Tue, 15 Jun 2004 16:50:37 -0400 Date: Tue, 15 Jun 2004 16:50:35 -0400 From: Christopher Nehren Subject: Re: [Qemu-devel] Windows XP status Message-ID: <20040615205035.GA86626@prophecy.dyndns.org> References: <40CF5BA1.9020500@witch.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <40CF5BA1.9020500@witch.dyndns.org> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hetz Ben Hamo Cc: qemu devel Mailing list --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 15, 2004 at 16:27:13 EDT, Hetz Ben Hamo scribbled these curious markings: > Hi, >=20 > It seems that few people had succsess stories while installing XP while= =20 > other had various crashes (in guest OS)... >=20 > To those who had those problems, could you please try to describe in=20 > much details the problems? It just segfaults, leaving a hefty 100-200 MB core file in its wake. Running said core through gdb invariably gives a 'cannot access memory at 0x$foo' error. Since I don't know gdb too well, and since the only manual is in GNU info format, which I abhor (replacing man pages? What was RMS smoking / sniffing / injecting? Er, never mind. I don't want to know), I doubt that I'll be able to provide any more information than that. > What I would like to know: >=20 > * Which Windows XP version is it (MSDN, XP Volume CD, OEM, Home, Pro, etc) XP Pro. > * If you managed to install XP, have you managed to run the wordpad=20 > program? (the "word processor" which is included in XP). Not yet. > * Where exactly did the crash happend Various places, mostly after the "Installing drivers" stage. > * Did you create users? if so, how many? Never got the chance to do so. > I understood that using the -pci or -pci -cirrusvga parameters makes any= =20 > XP installation crashes. Does it happend to you if you install XP from= =20 > scratch? Again, I haven't been able to successfully install with any options in order to make a comparison. --=20 I abhor a system designed for the "user", if that word is a coded pejorative meaning "stupid and unsophisticated". -- Ken Thompson - Unix is user friendly. However, it isn't idiot friendly. --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAz2Ebk/lo7zvzJioRAsXWAJ4jF+dbX4KXPB3wKZA+86aT0VD1uQCgis9S Mmv/AZ/SZrowYxxYLE7KHp4= =kbPE -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--