T40 WiFi Burp!

[JHEM]

After restoring my formerly troublesome T40 from my backup CDs I've encountered a new problem.

On XP startup I get a chide telling me my WiFi card is incorrectly installed and to reinstall the drivers. Nor does the Fn+F5 feature allow me to turn the card on and off.

Here's the interesting part, the card works just fine! I can access both my 11b and 11g networks here at home with no problems.

I've reinstalled the latest drivers for my a/b/g card, yet I continue to get the error message. All of my onscreen display functions work except Fn+F5.

What have I overlooked in my dotage?

Regards,

James

[jdhurst]

I had a problem with a T30 and the IBM High Rate Wireless card (Still have the problem - Access Connections does not support WPA on this card and has acknowledged same).

What I noticed is that when I uninstall Access Connections (to try a different version), it damages the wireless NIC installation along the way. That is one possible source of problem. What I did is uninstall both the wireless NIC and Access Connections; restart; install the wireless NIC and test with Windows software; then install Access Connections. Don't know if this relates in any way to you.

Next, whenever you uninstall / install Network drivers, Windows often leaves the driver information sitting in the registry. It is active information and can cause problems. You might wish to look in the registry to see if there are any extraneous network keys. They live in HK Local Machine -> System -> Current Control Set -> Control -> Network. Don't go there if you are uncomfortable.

Those are the two things I look at on any ThinkPad with Wireless problems.

Good luck. ... JDHurst

[rocky01]

that's good advice jd, once the registry gets extra or erroneus information/settings your entire connectivity can be problematic. also be certain to update intel controller package as it directly affects recognition of network hardware, irrespective of wifi card drivers being updated or not.

[JHEM]

Problem resolved! I don't know what specifically caused the hiccup in the system, but re-installing the latest a/b/g driver one more time has cleared the problem.

Regards,

James