I am troubleshooting a friend's computer.
His problem is this: He can't connect wirelessly BECAUSE his nephew wiped out his HDD when reinstalling Windows XP Pro for another issue (Printer malfunction . . . go figure). Consequently, the driver for his ethernet adapter/wireless card was wiped out.
His nephew talked to a Dell tech, but the tech was unable to solve the problem . . . maybe it was an off shore inexperienced tech that just read from a checklist. I don't know anything other than that the call was not any help.
Since he's coming up here in a few weeks (he lives in Southern California and I live in northwestern Arizona) and bringing his machine with him . . . a Dell Inspiron 6000 laptop, I'm going to troubleshoot it in detail then. Of course, he'll be well out of range for his wireless network, so I won't be able to check if the settings and driver work for sure. I may end up trying to do some remote assistance (CrossLoop) when he gets back to SoCal.
And he DOESN'T have a CD for the driver for the wireless card (which, BTW, I've discovered is embedded in his MOBO, which I expected for a laptop anyway). The chipset driver should take care of some of that.
But for now, I'm trying to get some info from him, specifically his hardware config on the machine . . . so that I can prepare and perhaps look for and download the drivers he needs. Plus, I don't even know if his nephew tried to install the Windows Pro default drivers from the CD driver library, so that might solve his problem.
Here's what I've done so far (and, BTW, this guy is TOTALLY computer illiterate . . . which is why I've decided to go no further 'till he brings the machine up):
I had him run an Msinfo report on adapters (Components>Network>Adapters in Msinfo) and email it to me. That was complete agony for both him and me, and it took me several emails and phone calls just to get him through it.
I finally got the report, and it had several entries that were "Not Available" and also a lot of "??". I've never seen that before but I was able to get enough clues that MAYBE he has the "Intel Pro 2200 Wireless" adapter and a Broadcom 440 ethernet 10/100 controller.
I had him run a Belarc profile and send it to me (another tedious chore for both of us). Something I hadn't seen in the Balarc profille before was several "None detected" entries.
3. Service Tag stuff
Dell, on their support web site, offers quite a few diagnostic services, not the least of which is a listing of the config when the thing left the factory . . . sort of like the inventory packing slip with the system (which he DOESN'T have . . . and that was one of the first things I asked him for). All of these services are contingent on having the Service Tag, which is a sticker on the machine. I DID manage to get that from him, but not without several emails and a lot of torture.
5. System Configuration tool
Dell has a System Configuration Tool on their web site. Once again, that's contingent on using the Service Tag number. So when he brings his machine up, I'll probably run that.
6. Notebook System Software
Before I install any ethernet/wireless driver, Dell says I first have to install the "Notebook System Software". It looks like this is mostly a marketing ploy with a lot of Dell junk, but I'll do it anyway.
7. Chipset drivers
Likewise, Dell says I first need to install a chipset driver. Since I don't know yet what his chipset is, I'll see if the Dell System Configuration Tool can ID it. If not, I'll try some of the diagnostic tools I've listed below.
I just had him download Everest Home Edition from the Major Geeks site and put it on his desktop. I was going to have him run a diagnostic and send me the report, but I think I'll wait.
Same as Everest . . . just had him download it and save it to his desktop.
10. AIDA32 Enterprise
Same as above
11. Postings on Dell forum.
I've looked at some of these, and believe it or not there have been others in similar situations.
A restore is obviously out since his nephew wiped everything out, and so also may be the Dell recovery partition since I assume that was wiped out too.
If I can ID the chipset (which I'll likely be able to do with one of the diagnostics above), then maybe I can go from there.
There are plenty of drivers on the Dell site, but I won't know which ones to download 'till I look at his machine's guts.
What am I missing, or am I on the wrong track all together?