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 | Rate Thread | Display Modes |
#1
|
|||
|
|||
Netgear A6200 wireless adapter & Win8pro64
Went to fire up a new win 8 desktop this evening. It's been setting on
my bench, awaiting an additional fan, and the install of a larger secondary HD. For one fan, I'd usually just get one locally, and pay the price. Unfortunately, the local store is out of fans. (Besides, they sell "cheap" fans at a high price.) I can order four of the same fans for their price for one. Anyway--- At startup, after switching to the "classic" desktop, the windows update icon was shown. Shortly thereafter, wireless connectivity when down the tubes. A few clicks into the related diags showed that the adapter did not see any of the usual three wireless networks it sees. After several futile attempts to get things to work, I ended up reverting to a hard wire (ethernet) connection. That worked immediately. Downloaded and installed the 21 updates, and restarted. Still no joy with the wireless adapter. It appeared that the adapter RF section was either shutdown, or had died. There was the usual 10 error code shown in the windows diags for the Adapter, and the adapter oem driver showed an "unexpected" error. ??? Scratched my thinning hair a bit, plugged in an ethernet cable, and downloaded a fresh copy of the driver. Followed instructions, and uninstalled the earlier (but the same rev driver package.) Reinstalled, checked the protocols, services, etc for the adapter, and set up for my network. Low and behold, things worked again! Why they quit to begin with, I have absolutely no idea. Maybe SSD's are subject to cosmic rays? After all, the sun's activity is quite high these days! |
Ads |
Thread Tools | |
Display Modes | Rate This Thread |
|
|