Discussion Locked

PC auto starts after XP Pro install

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a PC that dual boots 98 and NT4 (SP6a). PC has operated in this environment for 3 years without problem. I have installed XP Pro on this PC so it now triple boots. All 3 o/s are installed on separate logical drives. XP also runs without problem. Only problems I have is PC now starts back up about 20 mins after power down. Also, when PC is powered down (via pwr switch on the box), the user has to engage the switch for 4 secs before power down occurs. The BIOS does have a setting Soft-off-by-Power-button, either instant-off or delay-4-secs, but this has always been set to instant-off. I initially thought these 2 issues were a result of ACPI incompatibility between XP and motherboard.

Motherboard is an MS-6153 and the BIOS does support ACPI (enable or disable). ACPI has always been enabled in BIOS as Win98 uses it. The board supports Wakeup on LAN, Power on by Ring and Resume by Alarm, these options have always been disabled in BIOS.

ACPI was enabled in the BIOS when I firstinstalled XP. The PC restarts itself after power down from an XP or NT session, but not from Win98 . This is understandable as XP install replaces NT4 versions of ntdetect and ntldr (and boot.ini) with it's own versions. I cannot boot to XP if I disable ACPI in the BIOS (PC hangs at XP startup).

Rolled back to pre-XP by replacing ntdetect, ntldr and boot.ini with the NT4 versions and formatted the drive where XP was installed. Then a fresh XP install, this time using F5 to specify PC as a standard PC (i.e. non ACPI). After this install both problems still exist. Rolled back to pre-XP again, disabled ACPI in the BIOS and another fresh XP install, again using F5 to specify standard PC. Same 2 problems exist after this install. This leads me to believe that ACPI is not the problem as I have disabled it in the BIOS and forced XP to ignore it during install. Anyone have any ideas on what might be the cause.

2 replies

by thechas

With a 20 minute delay, I have to wonder if the occurrence of the re-start problem is just coincidental to the XP installation.

Was any hardware added or changed when XP was installed?

Is there a new piece of equipment nearby that was installed about the same time?
(AC line spikes could cause an ATX system to power up.)

I have seen a number of systems where the ATX power turn-on circuit has failed.
My suspicion is that as dust and grime builds up inside the PC, you reach a point where a static charge can travel along the wires to the motherboard, and damages the circuitry.

I also have seen a few 'hardware' incompatibilities with XP installed that did not show up under 9X.

I had to swap out both my modem and sound card to get my XP box to shut down. Yet, they work fine on a different motherboard.

Chas

by dclayw

There was one other change that occurred about the same time as the initial XP install, the PC was connected to a Netgear RP614 router, (great little router by the way). Previously the PC was standalone. I thought the router might have been waking up the PC, but I discounted that by unplugging from the router and the problem still occurs.

I also thought the problem may be caused by a faulty power supply or something similar, but note that prior to XP install this problem never occurred, and if I roll back to pre XP installation (by booting to NT using the NT versions of ntdetect and ntldr) the problem does not occur. The problem only occurs when I boot to either NT4 or XP using the XP versions of ntdetect and ntldr.

I might have to simply put this problem down to a compatibility issue between XP Pro and my hardware, but any further suggestions would be appreciated.

This discussion is closed to new replies.