If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Intel ProSet Wireless on 5000 series cards wedging itself, fix
A constant problem for us is Intel wireless geting
wedged in an impossible state, which has to be fixed by disabling and reenabling the wireless manually, to restore wireless connectivity. (Dell wireless cards don't have this problem.) It's most likely to be a lock bug in the Intel driver, or perhaps in XP. Anyway you can avoid it by disabling one core of a dual-core processor. (start/run/msconfig/boot.ini/advanced, select one processor) -- On the internet, nobody knows you're a jerk. |
#2
|
|||
|
|||
Intel ProSet Wireless on 5000 series cards wedging itself, fix
On 11/21/2012 7:49 AM, Ron Hardin wrote:
A constant problem for us is Intel wireless geting wedged in an impossible state, which has to be fixed by disabling and reenabling the wireless manually, to restore wireless connectivity. (Dell wireless cards don't have this problem.) It's most likely to be a lock bug in the Intel driver, or perhaps in XP. Anyway you can avoid it by disabling one core of a dual-core processor. (start/run/msconfig/boot.ini/advanced, select one processor) In otherwords the fix is to cut your CPU speed in half? What a solution. If somebody pays for a dual core CPU, God damnit they have the right to use it. That's like buying a car with a V8 but turning off four cylinders. |
#3
|
|||
|
|||
Intel ProSet Wireless on 5000 series cards wedging itself, fix
Justin wrote:
On 11/21/2012 7:49 AM, Ron Hardin wrote: A constant problem for us is Intel wireless geting wedged in an impossible state, which has to be fixed by disabling and reenabling the wireless manually, to restore wireless connectivity. (Dell wireless cards don't have this problem.) It's most likely to be a lock bug in the Intel driver, or perhaps in XP. Anyway you can avoid it by disabling one core of a dual-core processor. (start/run/msconfig/boot.ini/advanced, select one processor) In otherwords the fix is to cut your CPU speed in half? What a solution. If somebody pays for a dual core CPU, God damnit they have the right to use it. That's like buying a car with a V8 but turning off four cylinders. It doesn't cut your speed in half. Depending on what you're doing, it may make it faster by cutting memory contention. If you're running a single thing, it probably makes it faster. -- On the internet, nobody knows you're a jerk. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Catalyst 10.4 for both 4000 & 5000 series cards | rms[_4_] | Ati Videocards | 0 | April 22nd 10 05:02 PM |
Catalyst 10.4 Preview: Dramatic BFBC2 Speedups for 5000 series cards | rms[_4_] | Ati Videocards | 0 | April 17th 10 05:43 AM |
Intel ProSet error | J Lunis | General | 2 | November 30th 06 04:44 PM |
P4C800E-Deluxe - Intel(R) Proset problem | Laredo | Asus Motherboards | 2 | April 14th 06 10:17 PM |
5000 series | Ted | Compaq Computers | 4 | September 24th 04 03:36 AM |