re: Re-Enabling ACPI in my bios fixed it for me.
Wednesday, March 10, 2004 at 8:28 pm
Windows XP Annoyances Discussion Forum
Posted by Dave Coyne
(1 messages posted)
I owe everyone who has taken the time to post a great big "THANKS"! This forum has
been invaluable in helping me with my problem. However, I'm still not convinced
anyone has it right. I don't know the answer yet either and am still in the midst
of a reinstall to see if it fixes it. Here's the background. Put a new Abit NF7
mobo and Athlon XP 2500 in my system. Have a 1394 board, Soundblaster audio/game
card, Radeon 9000 Pro 128 AGP, Adaptec SCSI board. Upon trying to boot after mobo
install, got the same boot loop hang up after MUP.SYS loaded. I tried all the hardware
and BIOS tricks here and none helped. I was REALLY frustratred by the fact that
I couldn't even boot from the XP CD! After hours of blown time, I finally noticed
that I had knocked the CD cable loose. DOH! IMPORTANT LESSON #1: check connections.
After fixing this, I booted to the repair console and disabled MUP.SYS. No luck.
I did c:\TYPE NTBTLOG.TXT and noticed that ACPI was the next thing trying to load.
I disabled that. Still no change. I ultimately caved and am now trying to reinstall
XP completely. With 13 minutes to go, I'm now gettign some install error message
about
"The procedure entry point Get(UMS could not be located in the dynamic link library
MSDART.DLL". Must be my lucky week. More news later...
On Sunday, March 7, 2004 at 5:08 pm, Ne1scott wrote:
>
>This happened to me last night. After trying every possible method of booting I
>googled "mup.sys" and started reading about it. I read through almost all of the
>posts on this particular thread and was about to try the recovery console...or replacing
>mup.sys...or removing all of my PCI cards....when I read a post that talked about
>ACPI. So I went into my BIOS and enabled ACPI in the power management screen.
The
>system then booted up normally without a hitch. I too am using an AMD Athlon XP
>2100...and Maxtor hard drives....but it sounds like the ACPI BIOS option may be
the
>solution...normally I would always disable anything to do with power management.
> BTW: Linux's ACPI driver may not be recognizing the ACPI version the BIOS is using
>which might explain why one user's Linux machine still worked fine. ACPI starts
>immediately after mup.sys. Maybe if you have some option set in the OS for win2K
>or winXP, then something is configured to rely on the ACPI driver starting. If
your
>BIOS isn't responding properly to the ACPI driver, then maybe this is causing all
>of the system hangs. Moving RAM modules would affect the BIOS detection configuration
>data so it might be forcing other re-detections ...that might be why moving the
RAM
>modules worked for some people and moving/removing PCI cards worked for other people.
> ALL I know is that I'm glad I turned ACPI back on before carving up my system with
>the recovery console or any other hack workarounds. My system is running Windows
>XP Pro on an Epox 8KHA+ (KT266A) motherboard (Award BIOS) with 512MB of PC2100 DDR
>(2 x 256) and an AMD AthlonXP 2100+ CPU. A 120 GB Maxtor 6Y120PO EIDE, 80 GB Maxtor
>6L080L4 EDIDE, a Toshiba DVD-ROM and a Memorex 52x24x52 burner.
>
>
>
>
|
All messages in this thread [show all]
 |  |  | re: Re-Enabling ACPI in my bios fixed it for me. (Dave Coyne: Wed, Mar 10, 2004, 8:28 pm) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
