Disabling one core of dual core?
 

Is there a way to disable one core of a dual core
cpu?

The Intel proset wireless stuff has a bug that
apparently fails to lock correctly and wedges
itself in some impossible state requiring manual
disabling and reenabling of the software to
recover. (The lock failure may be a XP problem,
or not)

If it's only one core, it won't fall into this
bug.
--


On the internet, nobody knows you're a jerk.

Disabling one core of dual core?
 

On 11/04/2012 09:57 AM, Ron Hardin wrote:
Is there a way to disable one core of a dual core
cpu?

The Intel proset wireless stuff has a bug that
apparently fails to lock correctly and wedges
itself in some impossible state requiring manual
disabling and reenabling of the software to
recover. (The lock failure may be a XP problem,
or not)

If it's only one core, it won't fall into this
bug.


Go to:
Control panel...system...hardware... device manager



Now go to "computer" and your CPU will probably be identified as "ACPI
Multiprocessor PC" (Or something similar)

Next right click and look at "properties"
then opt to "update driver"

Opt for "no" when asked if you want to go on-line to search for new
drivers, then continue.

In the next dialog opt to "Install from a list..."


Then take the "don't search option"


Finally you will get several options of which driver to install...
take something other than "multiprocessor"

you will probably have an option for "standard PC" or "ACPI PC"

install one of those drivers and once installed.
save and exit

then reboot to confirm that your settings stuck


If it solves your problem...Good


but if the problems lies elsewhere,
be sure to re-install the original multi-core driver

Disabling one core of dual core?
 

Ron Hardin wrote in news:50969063.3AA8
@mindspring.com:

Is there a way to disable one core of a dual core
cpu?

The Intel proset wireless stuff has a bug that
apparently fails to lock correctly and wedges
itself in some impossible state requiring manual
disabling and reenabling of the software to
recover. (The lock failure may be a XP problem,
or not)

If it's only one core, it won't fall into this
bug.

You can edit the C:\Boot.ini file to add
/numproc=1
and then reboot. For more info, see:
http://support.microsoft.com/kb/833721

HTH,
John

Disabling one core of dual core?
 

Ron Hardin wrote:

Is there a way to disable one core of a dual core
cpu?

The Intel proset wireless stuff has a bug that
apparently fails to lock correctly and wedges
itself in some impossible state requiring manual
disabling and reenabling of the software to
recover. (The lock failure may be a XP problem,
or not)

If it's only one core, it won't fall into this
bug.

Thanks for the responses.

Disabling one processor has indeed stopped the wedged Intel Proset issue (so far).
So a lock bug looks like a likely source of the problem, if your Intel Proset
Wireless driver shows this symptom.
--


On the internet, nobody knows you're a jerk.

Disabling one core of dual core?
 

On 11/21/2012 06:41 AM, Ron Hardin wrote:
Ron Hardin wrote:

Is there a way to disable one core of a dual core
cpu?

The Intel proset wireless stuff has a bug that
apparently fails to lock correctly and wedges
itself in some impossible state requiring manual
disabling and reenabling of the software to
recover. (The lock failure may be a XP problem,
or not)

If it's only one core, it won't fall into this
bug.

Thanks for the responses.

Disabling one processor has indeed stopped the wedged Intel Proset issue (so far).
So a lock bug looks like a likely source of the problem, if your Intel Proset
Wireless driver shows this symptom.




Glad it worked...
I see that after I posted someone supplied an much easier to implement
solution

--
https://www.createspace.com/3707686

Disabling one core of dual core?
 

Ron Hardin wrote:

Ron Hardin wrote:

Is there a way to disable one core of a dual core
cpu?

The Intel proset wireless stuff has a bug that
apparently fails to lock correctly and wedges
itself in some impossible state requiring manual
disabling and reenabling of the software to
recover. (The lock failure may be a XP problem,
or not)

If it's only one core, it won't fall into this
bug.

Thanks for the responses.

Disabling one processor has indeed stopped the wedged Intel Proset issue (so far).
So a lock bug looks like a likely source of the problem, if your Intel Proset
Wireless driver shows this symptom.

Update: the singlized processor machines occasionally still lock up, but with much reduced
frequency. A lot less, not just a little.

So I'd say it's a logical bug in the Intel code, that's vastly more often encountered with
an idle CPU (in my case, the second core).

Probably some oversight between driver and utility about when an interrupt might happen and
screw up imagined status.
--


On the internet, nobody knows you're a jerk.