From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dz2sV-0005r6-Hj for qemu-devel@nongnu.org; Sat, 30 Jul 2005 21:44:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dz2sU-0005ql-OL for qemu-devel@nongnu.org; Sat, 30 Jul 2005 21:44:35 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dz2sU-0005qd-Ki for qemu-devel@nongnu.org; Sat, 30 Jul 2005 21:44:34 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1Dz30b-0002mg-Bk for qemu-devel@nongnu.org; Sat, 30 Jul 2005 21:52:57 -0400 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Dz2oe-0006vB-Os for qemu-devel@nongnu.org; Sun, 31 Jul 2005 03:40:36 +0200 Received: from liddicott.demon.co.uk ([80.177.221.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Jul 2005 03:40:36 +0200 Received: from sam by liddicott.demon.co.uk with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Jul 2005 03:40:36 +0200 From: Sam Liddicott Date: Sun, 31 Jul 2005 01:31:08 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: news Subject: [Qemu-devel] BIOS ESCD data Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I've tracked down guest winxp SP1 boot problems to bad ESCD bios data. A lot of talk here: http://www.hardwareanalysis.com/content/topic/31874/?o=0 But I think this is the key: http://www.hardwareanalysis.com/content/topic/31874/?o=50 I have had it freeze AT Mups.sys and just after when loading the AGP driver. So... what control havce we over what ESCD data the supplied BIOS provdes? Sam [QUOTE from http://www.hardwareanalysis.com/content/topic/31874/?o=50] Re: Windows xp freezes at mup.sys READ THIS POST FIRST, THIS IS THE OFFICIAL SOLUTION, INFO FROM MICROSOFT!! I spent a few hours reading through posts and forums on the net. I finally found that this seems to be a known Windows XP SP2 - motherboard issue. Mup.sys is not the culprate, it's just the last file before resources are alocated for WinXP. With the latest service pack there were some resource code rewritten (theoretically for security reasons). Due to this, mobos that have certain resource sets become invalid sometime after SP2 is installed (note: it may not be right away). All that needs to happen on most mobos is for this resource set (the ESCD) to be rewritten. Most "higher-end" motherboards have a setting in the BIOS to say "rewrite ESCD next startup", but not all do. My motherboard did have that option, but it didn't seem to work anyway. So the next step would be just to reset the BIOS. All motherboards have a way to do this. Most boards will have a jumper near the battery with which you can do this. Turn off the power on the power suply. Move the jumper over to bridge pin 2 and 3, turn on power suply for 10-15 seconds (if you hit the power button nothing should happen -- that is a good test to see if it is doing what it is supposed to be doing). Turn the power off, wait 10-15 seconds, switch the jumper back to bridge pin 1 and 2. Turn on power, hit power button, your problems should be fixed. If they are not, your ESCD may be hard coded somehow. The next step is to try to flash your BIOS with the newest version of your BIOS. Check your manual for all the instructions for that (or I'm sure there are plenty of forums that can describe how to do that).