PLEASE HELP w/ uninstalling ACPI MPS support

[lordlee 0]

HELP!!!!

 

I was attempting to fix random lockups on my W2K Pro retail running in MPS with a BP6 board. I installed the latest QQ BIOS and updated my computer driver from MPS Computer to ACPI MPS Computer (and enable ACPI/disable APM in the BIOS). Then my W2K will NOT boot up and will only give me a BSOD!!!

 

HELP.. How can I revert to my original configuration (MPS computer)? Or help solve the BSOD problem? PLEASE....I am BEGGING you....I tried the Safe mode, and it still gave a BSOD...PLEASE

[simonroockley 0]

You can try removing any cards that are not needed i.e. sound cards, network cards etc and then trying to boot the computer up again and then changing it. If this doesnt work then you may have to reinstall win2k from scratch.

Unless you have you rescue disk then there may be a way of returning you system to the original confiuration.

[euankirkhope 0]

Try just removing the Pci card next to your agp card then in the bios enabling "reset configuration data" Sometimes the agp card demands that another card is not using the same irq. In this configuration that is garanteed not to happen.

[r0cko 0]

YOU HAVE TO REINSTALL thats all. not a change so great be done post isntall. with all that is good come to who waits.

[Dragon-Lord 0]

yes, I was able to do the "upgrade" option of a reinstall and it worked perfectly (keeping all installed software, drivers, and settings).

 

:}

[BlaZeR2 0]

I just installed a BP6 MB with dual celery 366 o/ced to 550

 

I then installed 2000, and the computer driver used is MPS multiprocessor PC

 

what are the differences between this driver and the ACPI Multiprocessor driver?

Which is better?

 

Do i need to select ACPI to gain performance?

 

thanks for help

 

BlaZeR2

[W Clay Reeves 0]

Lordlee,

Install Recovery Console. Then manually set the HAL back to MPS Multiprocessor PC.

OR

Boot from the Cd and do an UPGRADE.

 

It is a no-no to try to go Std to ACPI. The standard MPS install omits all of the ACPI support such as IRQ Steering stuff. MS has numerous KB papers on this subject.

 

In point of fact, enabling ACPI doesn't really buy you anything except just that, advanced power management. So what?? If you've a desktop box are you all that concerned over a few watts of AC Mains power??

 

ACPI certainly does not provide any speed or other performance advantage.

 

BFN

 

WCR

[lordlee 0]

THanks for all help guys! I really appreciate it...I did a "reinstall" and "repair" and everything is back to normal. Thanks for all the info and help..especially AcidSpray who sent me a long and detailed email that really helped me out...I will post his detailed answer when I boot my Win98 partiion...

[acidspray 0]

Right on, Lord. Glad it helped, sorry you had the difficulty.

 

Quote:

Originally posted by lordlee:

THanks for all help guys! I really appreciate it...I did a "reinstall" and "repair" and everything is back to normal. Thanks for all the info and help..especially AcidSpray who sent me a long and detailed email that really helped me out...I will post his detailed answer when I boot my Win98 partiion...

[lordlee 0]

Here was the detailed answers sent to me from AcidSpray...it really helped!

To be clear, there are a few

> things you need to have ACPI work:

>

> 1) the latest (QQ beta) bios flashed

> 2) the latest 1.231(?) UDMA66 beta drivers installed or on floppy

> 3) MPS set to 1.4 in bios

> 4) bios set up corretly for ACPI (ACPI enabled, PM disbaled, etc)

>

> Now, there are two routes you cantake to get a working system from here...

>

> Route A: Still going for ACPI

> 1) You must have the above conditions met, particularly have the latest

> UDMA66 beta drivers on floppy and ready to go.

> 2) Start the computer, put your windows2000 cdrom in, get into bios and

set

> it up to boot from cd (cdrom first in boot order). You are going to

> reinstall windows over itself (all you files will still be intact, you

will

> just have to re-apply and windows updates you performed, and reinstall any

> drivers that were not resident on the windows CD).

> 3) When prompted, hit F6 and also hit F5. You will get a menu to select

> computer type...select ACPI multiprocessor. A bit after, you will be

> prompted for your UDMA66 drivers...make sure to install the newest betas.

> 4) Select install windows2000, not repair...it will then detect windows

2000

> is already on your system and you should get another option to repair the

> installation. Repair it, windows will refresh/reinstall all of its

> files...leaving all your previously installed files intact.

> 5) If everything is in order, Windows2000 will boot up properly under

ACPI.

>

> Route B: Forget the ACPI crap

> 1) If you are going to go this route, I would suggest going back to NJ

bios,

> no sense in running a beta if you don't need it.

> 2) I wouldn't go with the beta UDMA drivers on this path either, just the

> previous Windows 2000 compatible drivers will be fine.

> 3) Start the computer, put your windows2000 cdrom in, get into bios and

set

> it up to boot from cd (cdrom first in boot order). You are going to

> reinstall windows over itself (all you files will still be intact, you

will

> just have to re-apply and windows updates you performed, and reinstall any

> drivers that were not resident on the windows CD).

> 4) Hit F6 when prompted and install the non-beta (older) Win2k compatible

> UDMA66 drivers.

> 4) Select install windows2000, not repair...it will then detect windows

2000

> is already on your system and you should get a second option to repair

the

> installation. Repair it, windows will refresh/reinstall all of its

> files...leaving all your previously installed files intact.

> 5) If everything is in order, Windows2000 will boot up properly under MPS.

>

>

> Good luck! All I can say is that my method of switching to ACPI worked

for

> me, your mileage may vary. It is important to mention however than while

> ACPI is nice, it did nothing aboutn the random lockups. In fact, I have

> clean installed Windows 2000 twice since then, and am still having the

> problem. Once was to get back to MPS and make sure ACPI wasn't the

problem.

> The other was...hmmm...I forget...chasing another possible crash issue,

> that didn't pan out...

>

> -AciD

>

>

>