New
#1
WiFi won't work after disk transplant to identical machine
My problem is similar to, but probably caused differently than this one: https://www.sevenforums.com/network-s...urned-off.html
My old Lenovo T61p laptop died, so I bought a new identical old one. I transplanted my old disk into the new machine. Everything works perfectly, except for WiFi. I know the WiFi is good because the machine came with win xp, and under xp, the WiFi works perfectly.
I tried using device manager to "update driver," but it claims I have the latest driver. I ran windows update to get the latest, greatest everything. I unchecked in device manager "allow computer to turn off this device to save power."
What I observe is that the WiFi LED is on, but turns off momentarily every 5 secs or so. I have no idea what that means. Because the apps that tell me what incoming signals are present show nothing, this is not an access authentication problem. It seems to be some kind of driver issue.
One thing that bothers me is that in device manager there are 3 devices under "Other devices" with yellow ! signs: 2 of "Base System Device", and one "PCI Memory Controller". I don't recall seeing those issues on the old currently dead machine. At least the "PCI Memory Controller" one I noticed failed to be found at first boot in the new machine.
I should also clarify that I lied about the old and new machines being identical. The new machine does not have WWAN unlike the old, and it does have a fingerprint reader, which the old one lacked. Also, obviously the MAC address of the new WiFi card is different.
Another thing that bothers me is that Device Manager refers to the WiFi device as "Intel(R) Wireless WiFi Link 4965AGN #2", although in the details section of "device description" it is just plain "Intel(R) Wireless WiFi Link 4965AGN". This makes me think that the driver thinks the previous card is around somewhere and is confused about which one it is communicating with, or some such.
Can anyone cast some light on the meaning of these things, or what else I might be able to do to fix it?
--peter