Greg,
Yes, aware of this. Sadly I do not know how/where to do this. I really
try to stay out from under-the-hood. These newer OS's are just too
complicated for me any more.
Spent yesterday reading up on the HAL. Best advise is
another rebuild. At least this build lasted 2 error-free years. I'm fairly
certain this PC started out as 'ACPI Multiprocessor PC.' Unknown how/when
it got switched back. Will try a repair install today.
Thanks,
Duncan
On 09/19/2012 19:25, Greg Sevart wrote:
I don't have any XP machines handy to confirm the exact settings, and these
changed substantially/were deprecated in later Windows versions. It is
possible to limit Windows to 1 or n processors through various configuration
settings and flags.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of DSinc
Sent: Wednesday, September 19, 2012 9:20 AM
To: [email protected]
Subject: Re: [H] Coreinfo?
Greg,
What do I focus on in msconfig and the boot.ini?
Duncan
On 09/18/2012 23:47, Greg Sevart wrote:
Also worth checking msconfig and/or boot.ini
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Jamie
Furtner
Sent: Tuesday, September 18, 2012 10:41 PM
To: [email protected]
Subject: Re: [H] Coreinfo?
Agreed - Windows only sees one processor.
DSInc, you said the BIOS sees two processors (cores)?
What HAL is Windows using (Device Manager | Computer)? If it's something
like /ACPI Uniprocessor/ then you won't ever take advantage of multiple
CPUs, and coreinfo doesn't report accurate results, as it depends on the
HAL giving it the right information.
Jamie
