X31 "lost" the wireless network card

[Steen]

Some drivers are in trouble with each other so I can't turn the wireless card on (despite the fact that the light is on). When I hand over control til Windows instead of access conn. I can actually turn the light and the card off, and on, and for a short moment Windows tells med there is wireless networks found, but then the wireless networks card is lost again.
Probably there is some automativ turn off, that has gone wrong, but how can I fix this.

Actually I got it fixed yesterday by removing both the driver and a lot of other stuff, then reinstalling all, and when it was working I saved a windows state. After a day where all was fine I lost it again and resetting windows to the saved state didn't help.

When I try to install the Think Pad Wireless Adapter software it fails around 31% telling me there is a file that is missing, but not which one, so I can't get this software reinstalled, despite I can install the driver it self.

Any ideas?

[jronald]

What is the name brand on the card? Atheros, Intel, Broadcom?

Ron

[Steen]

My best bet is Atheros - that's what the drivers says and the support page from Lenovo says the same. Machine number is 2672-phg

[Harryc]

Product: ThinkPad X31 2672-PHG [change]
Operating system: All [change]

Original description: P M 1.6GHz, 256MB RAM, 40GB 4200rpm HDD, 12.1 XGA(1024x768) TFT LCD, 16MB ATI Radeon, IBM 802.11a/b/g wireless(MPCI), Bluetooth/Modem(CDC), 1Gb Ethernet(LOM), Secure Chip, IEEE 1394, 6cell Li-Ion battery, WinXP Pro

http://www-307.ibm.com/pc/support/site. ... MIGR-67214

* The following software must be updated when you install this package.
o Access Connections version 4.11 or later
o Hotkey Features for Windows 98/Me/NT/2K/XP version 1.22.0512 or later

[Steen]

And I do have both. Actually .NET is needed for Access Conn. so I also have this but the issue can be related to .NET as I have some keys in the registry pointing to missing .NET v1.1 (have upgraded to .NET v4). I am going to play around with this today.

But thenwhen I checked it is different what different cleaners report on the .NET, so I went another way: removed the Acc.conn. and switch windows to handle the wireless. Then it works?!? At the moment I don not have the needed Acc.conn. for the netcard driver, but despite this it works. Something is really weird...