WinXPpro and P4P800-E-Deluxe: how to get hyperthreading to work?

  • Thread starter Thread starter Peter Wagner
  • Start date Start date
P

Peter Wagner

Hi

I've changed my PIII MB to a P4P800-E Deluxe.
But I don't will re-install WinXP _and_ all my dozens of other programms.
:-(

W/o a re-installation WinXPpro can't recognize, that my P4 or the MB can
Hyper-threading.
So the Device Manager under Computer doesn't says 'ACPI Multiprocessor PC',
it says ACPI-PC.

There's a way to change the HAL (DLLs) to 'ACPI Multiprocessor PC'?
I know it exists a KB article to do this for Win2000, but there's no article
who describes the same for WinXP.

TIA
p
 
If you really don not want to reinstall XP after having changed your
motherboard, then I can safely say that you can look forward to loads of
Registry errors on your system in the years ahead.
 
Peter Wagner said:
Hi

I've changed my PIII MB to a P4P800-E Deluxe.
But I don't will re-install WinXP _and_ all my dozens of other programms.
:-(

W/o a re-installation WinXPpro can't recognize, that my P4 or the MB can
Hyper-threading.
So the Device Manager under Computer doesn't says 'ACPI Multiprocessor
PC',
it says ACPI-PC.

There's a way to change the HAL (DLLs) to 'ACPI Multiprocessor PC'?
I know it exists a KB article to do this for Win2000, but there's no
article
who describes the same for WinXP.

Boot from the XP CD and choose the second repair option. It will re-install
Windows, but leave your programs, etc installed. You'll have to re-install
any third party drivers and run Windows Update to get all the latest
updates.
 
Op Tue, 28 Sep 2004 16:10:15 +0200 schreef Peter Wagner:
I can't boot from the XP CD any more. :-(
There's an other way to repair?

'Not any more' implies you could boot from the cd before - if so, you
should still be able to do so. Just make sure the cd-rom drive is listed
before the hard drive in the list of boot devices in the BIOS.

If you can't boot from the cd at all, you can simply install the repair
console on the hard disc. Put the XP cd in the drive, select Start, Run and
type
X:\i386\winnt32.exe /cmdcons
where X is the cd-rom drive letter.
The next time you start the computer (and every time from now on, or until
you remove the repair console), you will be asked what you want to do:
start Windows XP or start the Repair console.

Wim
 
Wim said:
Op Tue, 28 Sep 2004 16:10:15 +0200 schreef Peter Wagner:

Hi Wim
If you can't boot from the cd at all, you can simply install the
repair console on the hard disc. Put the XP cd in the drive, select
Start, Run and type
X:\i386\winnt32.exe /cmdcons
where X is the cd-rom drive letter.
The next time you start the computer (and every time from now on, or
until you remove the repair console), you will be asked what you want
to do: start Windows XP or start the Repair console.

Wim

Thank you for your help.

But it doesn't helps.
The result is the same, as if I'll make:
-Secure mode booting
-Booting from the XP cd
-X:\setup.exe

Blue screen ->Shut down the system!
Error code 0x0000007B (0xF7C8263C, 0xC0000034, 0, 0)

But chkdsk/f doesn't solves the problem, I haven't changed the hard drive or
the IDE adapter, there no viruses?!

Fortunately I've backuped the 1-st partition before I've called
X:\i386\winnt32.exe /cmdcons :-)

The only solution will be to change the HAL manually, but I can't find a
description for WinXP.

p
 
Op Thu, 30 Sep 2004 16:56:56 +0200 schreef Peter Wagner:
Hi Wim


Thank you for your help.

But it doesn't helps.
The result is the same, as if I'll make:
-Secure mode booting
-Booting from the XP cd
-X:\setup.exe

Blue screen ->Shut down the system!
Error code 0x0000007B (0xF7C8263C, 0xC0000034, 0, 0)

But chkdsk/f doesn't solves the problem, I haven't changed the hard drive or
the IDE adapter, there no viruses?!

When you installed the new motherboard, you also changed the IDE-adapter
(along with just about everything else). Check in Device Manager under IDE
ATA/ATAPI controllers to make sure XP is using the right drivers (2 x
Intel(r) 8280 1EB Ultra ATA Storage Controllers and/or the Promise RAID
controller - don't know what it shows exactly for the Promise-controller,
as I don't use it, so it doesn't show up in Device Manager). It might still
use the driver for the IDE-adapter on your old motherboard.
Fortunately I've backuped the 1-st partition before I've called
X:\i386\winnt32.exe /cmdcons :-)

The only solution will be to change the HAL manually, but I can't find a
description for WinXP.

p

Sorry, neither can I.
For Stop 0x0000007B errors, see also:

http://support.microsoft.com/default.aspx?kbid=314082

One other thing I can think of: did you turn on the Boot Sector Virus
Protection under Boot in the BIOS? If so, turn it off. This setting
prevents the boot sector from being changed, which is normally a good
thing, but not if you want to run Windows Setup.

Wim
 
Wim said:
Op Thu, 30 Sep 2004 16:56:56 +0200 schreef Peter Wagner:
Thank you very much for your constant help.
When you installed the new motherboard, you also changed the
IDE-adapter (along with just about everything else).

Yes and no.
The new mb has an other integrated IDE-adapter.
Check in Device
Manager under IDE ATA/ATAPI controllers to make sure XP is using the
right drivers (2 x Intel(r) 8280 1EB Ultra ATA Storage Controllers

Not 2x only 1x
Intel(r) 82801EB Ultra ATA Storage Controllers
and/or the Promise RAID controller - don't know what it shows exactly
for the Promise-controller, as I don't use it, so it doesn't show up
in Device Manager).

No, I haven't installed the Promise RAID driver.
It might still use the driver for the IDE-adapter
on your old motherboard.

No, that isn't possible.
With the IDE-adapter driver for the old mb installed, WinXP wouldn't boot.
For this reason I've made a Recovery installation after the installation of
the new mb.
But at this time, I've only 1 DDR-RAM installed, because the dealer couldn't
delivers 2.
I've installed the 2nd DDR-RAM about 2 weeks later.
Perhaps this can be the cause of my problems?!

[...]
Sorry, neither can I.
For Stop 0x0000007B errors, see also:

http://support.microsoft.com/default.aspx?kbid=314082

Thank you for the hint.
I'll read it.
One other thing I can think of: did you turn on the Boot Sector Virus
Protection under Boot in the BIOS? If so, turn it off.

It's off.
This setting
prevents the boot sector from being changed, which is normally a good
thing, but not if you want to run Windows Setup.

Wim

An other possibility is, that the software on the WinXP cd can't recognize
my CD-ROM, a Lite-on burner?!
I've made the recovery installation with an other CD-ROM device, it wasn't a
burner.
So I should change the CD-ROM device (install the old again). :-(

p
 
Peter said:
Wim Zefat wrote:
An other possibility is, that the software on the WinXP cd can't
recognize my CD-ROM, a Lite-on burner?!
I've made the recovery installation with an other CD-ROM device, it
wasn't a burner.
So I should change the CD-ROM device (install the old again). :-(

I've changed the CD-ROM device by 2 others.
It doesn't helps. :-(

The boot sector should be ok.
Virus scanners doesn't found any boot sector virus.
chkdsk or scandisk says it's all ok.

Why can WinXP access the hd drive but at booting from the winxp cd rom it
can't?!
Or doesn't knows the winxp cd the new IDE chipset from Intel ->ICH5R?

Re-formatting the hd drive?
In 1 or 2 month I'll buy a new drive, than I'll have a new formatted drive.

p
 
Back
Top