might think about a REPAIR install instead of a full one.
it might help.
"Bill Leary" <Bill_Leary@xxxxxx> wrote in message news:667E2F56-01C7-4BF9-8C9E-420DC727927A@xxxxxx
"Richard G. Harper [MVP]" <rgharper@xxxxxx> wrote in message
> The only dependable way to fix this is to reinstall Windows. As it was
> installed with a uniprocessor core, it sees one processor. Reinstalling
> Windows will allow it to see two processors and install the multiprocessor
I was afraid it would come to that.
Before I go that far, since a re-install would be such a pain, I've got it
to seeing two processors, correctly identified, in Device Manager. Is there
another approach that might work?
Or, perhaps, something like install on another drive (I've got a pair of
these) and copy all of C:\Windows\system32? Or the key files or
directories? Or something similar?
Either way, thanks.
> Richard G. Harper [MVP Desktop] rgharper@xxxxxx
> * NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
> * PLEASE post all messages and replies in the newsgroups
> * The Website - http://rgharper.mvps.org/
> "Bill Leary" <Bill_Leary@xxxxxx> wrote in message
>> I'm running Vista Ultimate 32 bit.
>> I've had a single-core AMD Athlon in here since I build the machine and
>> installed Vista.
>> I just updated to a Dual core AMD Athlon.
>> When I first powered up, the BIOS reported an unknown model AMD with two
>> cores. Vista, in System Information, reported an unknown AMD with a
>> single core. So, I updated the BIOS. The BIOS now reports the correct
>> AMD with two cores. Vista, in System Information, now reports the
>> correct AMD, but with one core, one logical processor. Performance meter
>> and other things which would normally show two dials or scales for a dual
>> core still show only a single display.
>> Someone suggested I check Processors under Device Manager. That shows
>> "AMD Processor unknown model" twice. They suggested that Vista is
>> "stuck" from the start up with the BIOS that didn't ID the CPU and I
>> should delete the two entries under Processor and reboot to let it
>> rediscover them. I've seen this work for other things, but I'm feeling a
>> bit cautious about doing it to the CPU.
>> Is this the right way to go? Any other ideas?
>> - Bill