Where's my second CPU?

New install of WinXP x64 edition.

The first couple of times I booted the system, Windows detected a
multiprocessor system, and asked me to restart to finish the installation.
I restarted. It detected a multiprocessor system, and asked me to restart
to finish the installation. I restarted. It detected a multiprocessor
system, and asked me to restart....

It eventually gave up, and now I'm stuck with half a computer. :o(

Anyone know how to fix this? (Preferably without reinstalling Windows and
praying.)

Andre
Wed Mar 15 07:10:53 CST 2006

Its possible you might need to a BIOS update for your mother board to
support the additional CPU. Have you done this?
--
--
Andre
Windows Connect | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta

"James Robertson" <jamesr@funcom.com> wrote in message
news:ehcZD5CSGHA.4608@tk2msftngp13.phx.gbl...
> New install of WinXP x64 edition.
>
> The first couple of times I booted the system, Windows detected a
> multiprocessor system, and asked me to restart to finish the installation.
> I restarted. It detected a multiprocessor system, and asked me to restart
> to finish the installation. I restarted. It detected a multiprocessor
> system, and asked me to restart....
>
> It eventually gave up, and now I'm stuck with half a computer. :o(
>
> Anyone know how to fix this? (Preferably without reinstalling Windows and
> praying.)
>
>

James
Wed Mar 15 07:22:27 CST 2006

That's one thing I haven't tried yet. (Was going to look into that sometime
this afternoon.)

However, seeing as Windows initially detected a multiprocessor system, but
failed to install it, I'm not convinced that that is the problem.

Looking in the device manager I can see:

ACPI Uniprocessor x64 based PC
Microsoft ACPI-Compliant System
AMD Athlon 64 X2 Dual Core Processor 3800+

I can uninstall the Processor which then makes Windows jump through the 'hey
I've found a multiprocessor...' hoops for a while, and then it gives up
again. I can't uninstall the Uniprocessor item though.

Let me check the BIOS and see whether that helps though.



"Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message
news:OLxtoHDSGHA.4956@TK2MSFTNGP09.phx.gbl...
> Its possible you might need to a BIOS update for your mother board to
> support the additional CPU. Have you done this?
> --
> --
> Andre
> Windows Connect | http://www.windowsconnected.com
> Extended64 | http://www.extended64.com
> Blog | http://www.extended64.com/blogs/andre
> http://spaces.msn.com/members/adacosta
>
> "James Robertson" <jamesr@funcom.com> wrote in message
> news:ehcZD5CSGHA.4608@tk2msftngp13.phx.gbl...
>> New install of WinXP x64 edition.
>>
>> The first couple of times I booted the system, Windows detected a
>> multiprocessor system, and asked me to restart to finish the
>> installation. I restarted. It detected a multiprocessor system, and
>> asked me to restart to finish the installation. I restarted. It
>> detected a multiprocessor system, and asked me to restart....
>>
>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>
>> Anyone know how to fix this? (Preferably without reinstalling Windows
>> and praying.)
>>
>>
>
>

churin
Wed Mar 15 07:55:04 CST 2006

I agree that updating BIOS if available is a thing to try. Another thing
you can try is to manually update CPU driver for multiprocessor at the
Device Manager.

James Robertson wrote:
> New install of WinXP x64 edition.
>
> The first couple of times I booted the system, Windows detected a
> multiprocessor system, and asked me to restart to finish the installation.
> I restarted. It detected a multiprocessor system, and asked me to restart
> to finish the installation. I restarted. It detected a multiprocessor
> system, and asked me to restart....
>
> It eventually gave up, and now I'm stuck with half a computer. :o(
>
> Anyone know how to fix this? (Preferably without reinstalling Windows and
> praying.)
>
>

Rick
Wed Mar 15 08:00:57 CST 2006

I seriously doubt that Win x64 is the problem. This is a hardware BIOS
problem and you should be talking to the vendor of your motherboard to
resolve the situation.

I installed Win x64 on my motherboard with all the updates to the BIOS
and my Athlon 64 x2 was properly detected immediately.


James Robertson wrote:
> New install of WinXP x64 edition.
>
> The first couple of times I booted the system, Windows detected a
> multiprocessor system, and asked me to restart to finish the installation.
> I restarted. It detected a multiprocessor system, and asked me to restart
> to finish the installation. I restarted. It detected a multiprocessor
> system, and asked me to restart....
>
> It eventually gave up, and now I'm stuck with half a computer. :o(
>
> Anyone know how to fix this? (Preferably without reinstalling Windows and
> praying.)
>
>

James
Wed Mar 15 08:34:56 CST 2006

Yep, flashing the BIOS solved the problem. (Although that was a job and
half. I had to find a floppy disk first. Do you have any idea how scarce
those things are now? I'm glad I wasn't at home. I've not owned a PC with
a floppy drive in at least 5 years.)

Thanks guys. :o)


"Rick" <Rick@discussions.microsoft.com> wrote in message
news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>problem and you should be talking to the vendor of your motherboard to
>resolve the situation.
>
> I installed Win x64 on my motherboard with all the updates to the BIOS and
> my Athlon 64 x2 was properly detected immediately.
>
>
> James Robertson wrote:
>> New install of WinXP x64 edition.
>>
>> The first couple of times I booted the system, Windows detected a
>> multiprocessor system, and asked me to restart to finish the
>> installation. I restarted. It detected a multiprocessor system, and
>> asked me to restart to finish the installation. I restarted. It
>> detected a multiprocessor system, and asked me to restart....
>>
>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>
>> Anyone know how to fix this? (Preferably without reinstalling Windows
>> and praying.)
>>

Steve
Wed Mar 15 09:30:45 CST 2006

James Robertson wrote:

>Yep, flashing the BIOS solved the problem. (Although that was a job and
>half. I had to find a floppy disk first. Do you have any idea how scarce
>those things are now? I'm glad I wasn't at home. I've not owned a PC
>with a floppy drive in at least 5 years.)
>
>Thanks guys. :o)
>
>
>"Rick" <Rick@discussions.microsoft.com> wrote in message
>news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>problem and you should be talking to the vendor of your motherboard to
>>resolve the situation.
>>
>>I installed Win x64 on my motherboard with all the updates to the BIOS and
>> my Athlon 64 x2 was properly detected immediately.
>>
>>
>>James Robertson wrote:
>>>New install of WinXP x64 edition.
>>>
>>>The first couple of times I booted the system, Windows detected a
>>>multiprocessor system, and asked me to restart to finish the
>>>installation. I restarted. It detected a multiprocessor system, and
>>>asked me to restart to finish the installation. I restarted. It
>>>detected a multiprocessor system, and asked me to restart....
>>>
>>>It eventually gave up, and now I'm stuck with half a computer. :o(
>>>
>>>Anyone know how to fix this? (Preferably without reinstalling Windows
>>>and praying.)
>>>

I use bootable CDs or even USB memory sticks for flashing BIOSs these
days. Can't remember the last time I actually used a floppy drive to do so.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Andre
Wed Mar 15 09:43:17 CST 2006

Charlie recommends using a USB Floppy if you can get one, so the options are
out there if you don't have a built in one.
--
--
Andre
Windows Connect | http://www.windowsconnected.com
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta

"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:xn0ejrhee3toblz00z@msnews.microsoft.com...
> James Robertson wrote:
>
>>Yep, flashing the BIOS solved the problem. (Although that was a job and
>>half. I had to find a floppy disk first. Do you have any idea how scarce
>>those things are now? I'm glad I wasn't at home. I've not owned a PC
>>with a floppy drive in at least 5 years.)
>>
>>Thanks guys. :o)
>>
>>
>>"Rick" <Rick@discussions.microsoft.com> wrote in message
>>news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>>problem and you should be talking to the vendor of your motherboard to
>>>resolve the situation.
>>>
>>>I installed Win x64 on my motherboard with all the updates to the BIOS
>>>and my Athlon 64 x2 was properly detected immediately.
>>>
>>>
>>>James Robertson wrote:
>>>>New install of WinXP x64 edition.
>>>>
>>>>The first couple of times I booted the system, Windows detected a
>>>>multiprocessor system, and asked me to restart to finish the
>>>>installation. I restarted. It detected a multiprocessor system, and
>>>>asked me to restart to finish the installation. I restarted. It
>>>>detected a multiprocessor system, and asked me to restart....
>>>>
>>>>It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>
>>>>Anyone know how to fix this? (Preferably without reinstalling Windows
>>>>and praying.)
>>>>
>
> I use bootable CDs or even USB memory sticks for flashing BIOSs these
> days. Can't remember the last time I actually used a floppy drive to do
> so.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.

Steve
Wed Mar 15 10:06:38 CST 2006

Andre Da Costa [Extended64] wrote:

>Charlie recommends using a USB Floppy if you can get one, so the options
>are out there if you don't have a built in one.

If the PC will boot from USB floppy, it'll almost certainly boot from a
USB memory stick too. So that's what I use.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

Charlie
Wed Mar 15 10:17:33 CST 2006

Hmmm. I've been able to get it to boot from a USB floppy when a memory stick
wouldn't work. And, of course, a memory stick won't solve the common F6
problem that we still have to live with. I find that old USB floppy drive
that came with a Toshiba laptop I had years ago is a useful thing to have
around.

And, of course, the last time I junked an old system, I pulled the floppy
out of it first, and I keep that on the back of the shelf, with a standard
flat floppy cable wrapped around it. When I run into a problem, I yank it
out and plug it in, sort of hanging out the side of the machine that needs
it. Do the F6, and pull it out and toss on the back of the shelf till the
next time.


--
Charlie.
http://msmvps.com/xperts64

Steve Foster [SBS MVP] wrote:
> Andre Da Costa [Extended64] wrote:
>
>> Charlie recommends using a USB Floppy if you can get one, so the options
>> are out there if you don't have a built in one.
>
> If the PC will boot from USB floppy, it'll almost certainly boot from a
> USB memory stick too. So that's what I use.

DP
Wed Mar 15 19:46:18 CST 2006


"Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message
news:%23OaaAxESGHA.5808@TK2MSFTNGP12.phx.gbl...
> Hmmm. I've been able to get it to boot from a USB floppy when a memory
> stick wouldn't work. And, of course, a memory stick won't solve the common
> F6 problem that we still have to live with.

Sorry. What's F6 do?
(I don't have a floppy drive on my machine, or else I'd test it myself.)

Charlie
Wed Mar 15 20:01:44 CST 2006

F6 is the key that you have to hit during the initial install of any version
of Windows since NT3.1 if you need to add an additional storage driver
before you start the install. Since many, many of the SATA controllers that
are on the x64 motherboards out there are also RAID controllers, they
generally need the drivers loaded in order to see the HDs. Old server guys
like me don't even think about it, we're used to it. But it's a relatively
new problem for many XP x64 users.

--
Charlie.
http://msmvps.com/xperts64

DP wrote:
> "Charlie Russel - MVP" <charlie@mvKILLALLSPAMMERSps.org> wrote in message
> news:%23OaaAxESGHA.5808@TK2MSFTNGP12.phx.gbl...
>> Hmmm. I've been able to get it to boot from a USB floppy when a memory
>> stick wouldn't work. And, of course, a memory stick won't solve the
>> common F6 problem that we still have to live with.
>
> Sorry. What's F6 do?
> (I don't have a floppy drive on my machine, or else I'd test it myself.)

James
Thu Mar 16 04:08:21 CST 2006

Hah! Seems I spoke too soon.

Windows has lost the 2nd CPU again. (It bravely attempted to reinstall it
once, and then gave up after I'd restarted again.)

So, I suspect win x64 *is* the problem after all.


"James Robertson" <jamesr@funcom.com> wrote in message
news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
> Yep, flashing the BIOS solved the problem. (Although that was a job and
> half. I had to find a floppy disk first. Do you have any idea how scarce
> those things are now? I'm glad I wasn't at home. I've not owned a PC
> with a floppy drive in at least 5 years.)
>
> Thanks guys. :o)
>
>
> "Rick" <Rick@discussions.microsoft.com> wrote in message
> news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>problem and you should be talking to the vendor of your motherboard to
>>resolve the situation.
>>
>> I installed Win x64 on my motherboard with all the updates to the BIOS
>> and my Athlon 64 x2 was properly detected immediately.
>>
>>
>> James Robertson wrote:
>>> New install of WinXP x64 edition.
>>>
>>> The first couple of times I booted the system, Windows detected a
>>> multiprocessor system, and asked me to restart to finish the
>>> installation. I restarted. It detected a multiprocessor system, and
>>> asked me to restart to finish the installation. I restarted. It
>>> detected a multiprocessor system, and asked me to restart....
>>>
>>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>>
>>> Anyone know how to fix this? (Preferably without reinstalling Windows
>>> and praying.)
>>>
>

Dominic
Thu Mar 16 05:08:39 CST 2006

Have you applied the AMD x64 CPU driver from
http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html ?



"James Robertson" <jamesr@funcom.com> wrote in message
news:uPioPGOSGHA.2536@tk2msftngp13.phx.gbl...
> Hah! Seems I spoke too soon.
>
> Windows has lost the 2nd CPU again. (It bravely attempted to reinstall it
> once, and then gave up after I'd restarted again.)
>
> So, I suspect win x64 *is* the problem after all.
>
>
> "James Robertson" <jamesr@funcom.com> wrote in message
> news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>> Yep, flashing the BIOS solved the problem. (Although that was a job and
>> half. I had to find a floppy disk first. Do you have any idea how
>> scarce those things are now? I'm glad I wasn't at home. I've not owned
>> a PC with a floppy drive in at least 5 years.)
>>
>> Thanks guys. :o)
>>
>>
>> "Rick" <Rick@discussions.microsoft.com> wrote in message
>> news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>>problem and you should be talking to the vendor of your motherboard to
>>>resolve the situation.
>>>
>>> I installed Win x64 on my motherboard with all the updates to the BIOS
>>> and my Athlon 64 x2 was properly detected immediately.
>>>
>>>
>>> James Robertson wrote:
>>>> New install of WinXP x64 edition.
>>>>
>>>> The first couple of times I booted the system, Windows detected a
>>>> multiprocessor system, and asked me to restart to finish the
>>>> installation. I restarted. It detected a multiprocessor system, and
>>>> asked me to restart to finish the installation. I restarted. It
>>>> detected a multiprocessor system, and asked me to restart....
>>>>
>>>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>
>>>> Anyone know how to fix this? (Preferably without reinstalling Windows
>>>> and praying.)
>>>>
>>
>
>

Rick
Thu Mar 16 05:21:15 CST 2006

I still seriously doubt that the fault lies with Win x64.

To start with, you are the 1st person to have this problem.

So, it is my humble opinion that you have a hardware problem. Either
the motherboard itself, or the CPU; but not Win x64.


James Robertson wrote:
> Hah! Seems I spoke too soon.
>
> Windows has lost the 2nd CPU again. (It bravely attempted to reinstall it
> once, and then gave up after I'd restarted again.)
>
> So, I suspect win x64 *is* the problem after all.
>
>
> "James Robertson" <jamesr@funcom.com> wrote in message
> news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>> Yep, flashing the BIOS solved the problem. (Although that was a job and
>> half. I had to find a floppy disk first. Do you have any idea how scarce
>> those things are now? I'm glad I wasn't at home. I've not owned a PC
>> with a floppy drive in at least 5 years.)
>>
>> Thanks guys. :o)
>>
>>
>> "Rick" <Rick@discussions.microsoft.com> wrote in message
>> news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>> I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>> problem and you should be talking to the vendor of your motherboard to
>>> resolve the situation.
>>>
>>> I installed Win x64 on my motherboard with all the updates to the BIOS
>>> and my Athlon 64 x2 was properly detected immediately.
>>>
>>>
>>> James Robertson wrote:
>>>> New install of WinXP x64 edition.
>>>>
>>>> The first couple of times I booted the system, Windows detected a
>>>> multiprocessor system, and asked me to restart to finish the
>>>> installation. I restarted. It detected a multiprocessor system, and
>>>> asked me to restart to finish the installation. I restarted. It
>>>> detected a multiprocessor system, and asked me to restart....
>>>>
>>>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>
>>>> Anyone know how to fix this? (Preferably without reinstalling Windows
>>>> and praying.)
>>>>
>
>

James
Thu Mar 16 05:20:45 CST 2006

I have now. And still only one CPU. :o(

I'm slowly facing the fact that I'm going to have to waste yet another day
formatting the HD and reinstalling Windows. *sigh*




"Dominic Payer" <dominic@dc_payer.freeserve.co.uk> wrote in message
news:uE8x8nOSGHA.4276@TK2MSFTNGP10.phx.gbl...
> Have you applied the AMD x64 CPU driver from
> http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html ?
>
>
>
> "James Robertson" <jamesr@funcom.com> wrote in message
> news:uPioPGOSGHA.2536@tk2msftngp13.phx.gbl...
>> Hah! Seems I spoke too soon.
>>
>> Windows has lost the 2nd CPU again. (It bravely attempted to reinstall
>> it once, and then gave up after I'd restarted again.)
>>
>> So, I suspect win x64 *is* the problem after all.
>>
>>
>> "James Robertson" <jamesr@funcom.com> wrote in message
>> news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>>> Yep, flashing the BIOS solved the problem. (Although that was a job and
>>> half. I had to find a floppy disk first. Do you have any idea how
>>> scarce those things are now? I'm glad I wasn't at home. I've not owned
>>> a PC with a floppy drive in at least 5 years.)
>>>
>>> Thanks guys. :o)
>>>
>>>
>>> "Rick" <Rick@discussions.microsoft.com> wrote in message
>>> news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>>>problem and you should be talking to the vendor of your motherboard to
>>>>resolve the situation.
>>>>
>>>> I installed Win x64 on my motherboard with all the updates to the BIOS
>>>> and my Athlon 64 x2 was properly detected immediately.
>>>>
>>>>
>>>> James Robertson wrote:
>>>>> New install of WinXP x64 edition.
>>>>>
>>>>> The first couple of times I booted the system, Windows detected a
>>>>> multiprocessor system, and asked me to restart to finish the
>>>>> installation. I restarted. It detected a multiprocessor system, and
>>>>> asked me to restart to finish the installation. I restarted. It
>>>>> detected a multiprocessor system, and asked me to restart....
>>>>>
>>>>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>>
>>>>> Anyone know how to fix this? (Preferably without reinstalling Windows
>>>>> and praying.)
>>>>>
>>>
>>
>>
>
>

churin
Thu Mar 16 07:38:10 CST 2006

James Robertson wrote:
> I have now. And still only one CPU. :o(
>
> I'm slowly facing the fact that I'm going to have to waste yet another day
> formatting the HD and reinstalling Windows. *sigh*
>
>
>
>
> "Dominic Payer" <dominic@dc_payer.freeserve.co.uk> wrote in message
> news:uE8x8nOSGHA.4276@TK2MSFTNGP10.phx.gbl...
>> Have you applied the AMD x64 CPU driver from
>> http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html ?
>>
>>
>>
>> "James Robertson" <jamesr@funcom.com> wrote in message
>> news:uPioPGOSGHA.2536@tk2msftngp13.phx.gbl...
>>> Hah! Seems I spoke too soon.
>>>
>>> Windows has lost the 2nd CPU again. (It bravely attempted to reinstall
>>> it once, and then gave up after I'd restarted again.)
Try updating cpu driver before you try reinstalling WXP x64.

>>>
>>> So, I suspect win x64 *is* the problem after all.
>>>
>>>
>>> "James Robertson" <jamesr@funcom.com> wrote in message
>>> news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>>>> Yep, flashing the BIOS solved the problem. (Although that was a job and
>>>> half. I had to find a floppy disk first. Do you have any idea how
>>>> scarce those things are now? I'm glad I wasn't at home. I've not owned
>>>> a PC with a floppy drive in at least 5 years.)
>>>>
>>>> Thanks guys. :o)
>>>>
>>>>
>>>> "Rick" <Rick@discussions.microsoft.com> wrote in message
>>>> news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>>> I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>>>> problem and you should be talking to the vendor of your motherboard to
>>>>> resolve the situation.
>>>>>
>>>>> I installed Win x64 on my motherboard with all the updates to the BIOS
>>>>> and my Athlon 64 x2 was properly detected immediately.
>>>>>
>>>>>
>>>>> James Robertson wrote:
>>>>>> New install of WinXP x64 edition.
>>>>>>
>>>>>> The first couple of times I booted the system, Windows detected a
>>>>>> multiprocessor system, and asked me to restart to finish the
>>>>>> installation. I restarted. It detected a multiprocessor system, and
>>>>>> asked me to restart to finish the installation. I restarted. It
>>>>>> detected a multiprocessor system, and asked me to restart....
>>>>>>
>>>>>> It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>>>
>>>>>> Anyone know how to fix this? (Preferably without reinstalling Windows
>>>>>> and praying.)
>>>>>>
>>>
>>
>
>

John
Thu Mar 16 07:48:08 CST 2006

Can you change the hal from uni to multi processor at the Device Manager?

John

James Robertson wrote:

> I have now. And still only one CPU. :o(
>
> I'm slowly facing the fact that I'm going to have to waste yet another day
> formatting the HD and reinstalling Windows. *sigh*
>
>
>
>
> "Dominic Payer" <dominic@dc_payer.freeserve.co.uk> wrote in message
> news:uE8x8nOSGHA.4276@TK2MSFTNGP10.phx.gbl...
>
>>Have you applied the AMD x64 CPU driver from
>>http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html ?
>>
>>
>>
>>"James Robertson" <jamesr@funcom.com> wrote in message
>>news:uPioPGOSGHA.2536@tk2msftngp13.phx.gbl...
>>
>>>Hah! Seems I spoke too soon.
>>>
>>>Windows has lost the 2nd CPU again. (It bravely attempted to reinstall
>>>it once, and then gave up after I'd restarted again.)
>>>
>>>So, I suspect win x64 *is* the problem after all.
>>>
>>>
>>>"James Robertson" <jamesr@funcom.com> wrote in message
>>>news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>>>
>>>>Yep, flashing the BIOS solved the problem. (Although that was a job and
>>>>half. I had to find a floppy disk first. Do you have any idea how
>>>>scarce those things are now? I'm glad I wasn't at home. I've not owned
>>>>a PC with a floppy drive in at least 5 years.)
>>>>
>>>>Thanks guys. :o)
>>>>
>>>>
>>>>"Rick" <Rick@discussions.microsoft.com> wrote in message
>>>>news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>>
>>>>>I seriously doubt that Win x64 is the problem. This is a hardware BIOS
>>>>>problem and you should be talking to the vendor of your motherboard to
>>>>>resolve the situation.
>>>>>
>>>>>I installed Win x64 on my motherboard with all the updates to the BIOS
>>>>>and my Athlon 64 x2 was properly detected immediately.
>>>>>
>>>>>
>>>>>James Robertson wrote:
>>>>>
>>>>>>New install of WinXP x64 edition.
>>>>>>
>>>>>>The first couple of times I booted the system, Windows detected a
>>>>>>multiprocessor system, and asked me to restart to finish the
>>>>>>installation. I restarted. It detected a multiprocessor system, and
>>>>>>asked me to restart to finish the installation. I restarted. It
>>>>>>detected a multiprocessor system, and asked me to restart....
>>>>>>
>>>>>>It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>>>
>>>>>>Anyone know how to fix this? (Preferably without reinstalling Windows
>>>>>>and praying.)
>>>>>>
>>>>
>>>
>>
>
>

James
Thu Mar 16 08:41:37 CST 2006

How?


"John John" <audetweld@nbnet.nb.ca> wrote in message
news:%234n1tAQSGHA.4960@TK2MSFTNGP12.phx.gbl...
> Can you change the hal from uni to multi processor at the Device Manager?
>
> John
>
> James Robertson wrote:
>
>> I have now. And still only one CPU. :o(
>>
>> I'm slowly facing the fact that I'm going to have to waste yet another
>> day formatting the HD and reinstalling Windows. *sigh*
>>
>>
>>
>>
>> "Dominic Payer" <dominic@dc_payer.freeserve.co.uk> wrote in message
>> news:uE8x8nOSGHA.4276@TK2MSFTNGP10.phx.gbl...
>>
>>>Have you applied the AMD x64 CPU driver from
>>>http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html ?
>>>
>>>
>>>
>>>"James Robertson" <jamesr@funcom.com> wrote in message
>>>news:uPioPGOSGHA.2536@tk2msftngp13.phx.gbl...
>>>
>>>>Hah! Seems I spoke too soon.
>>>>
>>>>Windows has lost the 2nd CPU again. (It bravely attempted to reinstall
>>>>it once, and then gave up after I'd restarted again.)
>>>>
>>>>So, I suspect win x64 *is* the problem after all.
>>>>
>>>>
>>>>"James Robertson" <jamesr@funcom.com> wrote in message
>>>>news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>>>>
>>>>>Yep, flashing the BIOS solved the problem. (Although that was a job
>>>>>and half. I had to find a floppy disk first. Do you have any idea how
>>>>>scarce those things are now? I'm glad I wasn't at home. I've not
>>>>>owned a PC with a floppy drive in at least 5 years.)
>>>>>
>>>>>Thanks guys. :o)
>>>>>
>>>>>
>>>>>"Rick" <Rick@discussions.microsoft.com> wrote in message
>>>>>news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>>>
>>>>>>I seriously doubt that Win x64 is the problem. This is a hardware
>>>>>>BIOS problem and you should be talking to the vendor of your
>>>>>>motherboard to resolve the situation.
>>>>>>
>>>>>>I installed Win x64 on my motherboard with all the updates to the BIOS
>>>>>>and my Athlon 64 x2 was properly detected immediately.
>>>>>>
>>>>>>
>>>>>>James Robertson wrote:
>>>>>>
>>>>>>>New install of WinXP x64 edition.
>>>>>>>
>>>>>>>The first couple of times I booted the system, Windows detected a
>>>>>>>multiprocessor system, and asked me to restart to finish the
>>>>>>>installation. I restarted. It detected a multiprocessor system, and
>>>>>>>asked me to restart to finish the installation. I restarted. It
>>>>>>>detected a multiprocessor system, and asked me to restart....
>>>>>>>
>>>>>>>It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>>>>
>>>>>>>Anyone know how to fix this? (Preferably without reinstalling
>>>>>>>Windows and praying.)
>>>>>>>
>>>>>
>>>>
>>>
>>
>>
>

John
Thu Mar 16 09:15:18 CST 2006

HAL options after Windows XP or Windows Server 2003 Setup
http://support.microsoft.com/?kbid=309283

Click on the device and chose "Update drivers" then select the same type
of hal in the multiProc version.

On Windows 2000 it goes like so:
http://support.microsoft.com/kb/234558/EN-US/

Not sure if X64 does it the same way but you get the idea.

John

James Robertson wrote:

> How?
>
>
> "John John" <audetweld@nbnet.nb.ca> wrote in message
> news:%234n1tAQSGHA.4960@TK2MSFTNGP12.phx.gbl...
>
>>Can you change the hal from uni to multi processor at the Device Manager?
>>
>>John
>>
>>James Robertson wrote:
>>
>>
>>>I have now. And still only one CPU. :o(
>>>
>>>I'm slowly facing the fact that I'm going to have to waste yet another
>>>day formatting the HD and reinstalling Windows. *sigh*
>>>
>>>
>>>
>>>
>>>"Dominic Payer" <dominic@dc_payer.freeserve.co.uk> wrote in message
>>>news:uE8x8nOSGHA.4276@TK2MSFTNGP10.phx.gbl...
>>>
>>>
>>>>Have you applied the AMD x64 CPU driver from
>>>>http://www.amd.com/us-en/Processors/TechnicalResources/0,,30_182_871_9706,00.html ?
>>>>
>>>>
>>>>
>>>>"James Robertson" <jamesr@funcom.com> wrote in message
>>>>news:uPioPGOSGHA.2536@tk2msftngp13.phx.gbl...
>>>>
>>>>
>>>>>Hah! Seems I spoke too soon.
>>>>>
>>>>>Windows has lost the 2nd CPU again. (It bravely attempted to reinstall
>>>>>it once, and then gave up after I'd restarted again.)
>>>>>
>>>>>So, I suspect win x64 *is* the problem after all.
>>>>>
>>>>>
>>>>>"James Robertson" <jamesr@funcom.com> wrote in message
>>>>>news:ezAdi2DSGHA.2276@tk2msftngp13.phx.gbl...
>>>>>
>>>>>
>>>>>>Yep, flashing the BIOS solved the problem. (Although that was a job
>>>>>>and half. I had to find a floppy disk first. Do you have any idea how
>>>>>>scarce those things are now? I'm glad I wasn't at home. I've not
>>>>>>owned a PC with a floppy drive in at least 5 years.)
>>>>>>
>>>>>>Thanks guys. :o)
>>>>>>
>>>>>>
>>>>>>"Rick" <Rick@discussions.microsoft.com> wrote in message
>>>>>>news:exaWojDSGHA.4960@TK2MSFTNGP12.phx.gbl...
>>>>>>
>>>>>>
>>>>>>>I seriously doubt that Win x64 is the problem. This is a hardware
>>>>>>>BIOS problem and you should be talking to the vendor of your
>>>>>>>motherboard to resolve the situation.
>>>>>>>
>>>>>>>I installed Win x64 on my motherboard with all the updates to the BIOS
>>>>>>>and my Athlon 64 x2 was properly detected immediately.
>>>>>>>
>>>>>>>
>>>>>>>James Robertson wrote:
>>>>>>>
>>>>>>>
>>>>>>>>New install of WinXP x64 edition.
>>>>>>>>
>>>>>>>>The first couple of times I booted the system, Windows detected a
>>>>>>>>multiprocessor system, and asked me to restart to finish the
>>>>>>>>installation. I restarted. It detected a multiprocessor system, and
>>>>>>>>asked me to restart to finish the installation. I restarted. It
>>>>>>>>detected a multiprocessor system, and asked me to restart....
>>>>>>>>
>>>>>>>>It eventually gave up, and now I'm stuck with half a computer. :o(
>>>>>>>>
>>>>>>>>Anyone know how to fix this? (Preferably without reinstalling
>>>>>>>>Windows and praying.)
>>>>>>>>
>>>>>>
>>>
>
>

churin
Thu Mar 16 09:30:53 CST 2006

The process is the same as doing udate of any driver at Device Manager
and you just pick ACPI Multiprocessor. You can also specify HAL as ACPI
Multiprocessor during installation of WXP x64 if you ever want to try
that again.

James Robertson wrote:
> How?
>
>
> "John John" <audetweld@nbnet.nb.ca> wrote in message
> news:%234n1tAQSGHA.4960@TK2MSFTNGP12.phx.gbl...
>> Can you change the hal from uni to multi processor at the Device Manager?
>>
>> John
>>
>> James Robertson wrote:
>>
>>> I have now. And still only one CPU. :o(
>>>
>>> I'm slowly facing the fact that I'm going to have to waste yet another
>>> day formatting the HD and reinstalling Windows. *sigh*
>>>
>>>
>>>
>>>
>>> "Dominic Payer" <dominic@dc_payer.freeserve.co.uk> wrote in message
>>> news:uE8x8nOSGHA.4276@TK2MSFTNGP10.phx.gbl...
>>>
>>>> Have you applied the AMD x64 CPU driver from
>>>>