Resolved: Additional Info: Lattitude D620 Inbuilt Wireless died



Thanks for all the advice. In the end, we replaced the motherboard and of
course that resolved the problem. Because this is pretty typical
configuration among my colleagues we swapped my hard drive to an identical
system to confirm there was not driver, configuration, registry problem.
So, we declared ourselves at a point of diagnostic diminishing return and
ordered the motherboard for the system that was still under warranty.
Swapped it in, move my memory over, and all is well. I wish I was more
confident this was our only course of action, but I was wishing for the
convenience of inbuilt wireless even more. All this just before I serve a
couple days jury duty. I am hoping to catch up on some work away from
phones and colleague interruptions.

Happy new year,
Jere


"S.Lewis" <NVRambo@xxxxxxxxxx> wrote in message
news:beudj.38851$N67.14233@xxxxxxxxxxxxxxxxxxxxxxxxx

"JCMc" <mcdonald.jc@xxxxxxxxxxx> wrote in message
news:hNrdj.3110$ZI4.284@xxxxxxxxxxx

"S.Lewis" <NVRambo@xxxxxxxxxx> wrote in message
news:Iykdj.19620$L27.5382@xxxxxxxxxxxxxxxxxxxxxxxxx

"JCMc" <mcdonald.jc@xxxxxxxxxxx> wrote in message
news:S3jdj.213$sE5.211@xxxxxxxxxxx
Installed a new replacement Wireless mini-card from Dell today, and did
not resolve this problem. Typically, windows does not even find the
device on it's own, but I can force it to show up by initiating the
Dell Install wizard. However, it shows up in the device list with an
! over the icon. If I open the properties box it shows an error message
that says the "device cannot be started - error code 10". Any
additional ideas are welcome.
Thanks,
Jere



Assuming that:

1) The card is enabled in BIOS, and......

2) That the software/driver/utility is properly installed and updated to
the latest driver version.....

3) ...then if the above are true, I suspect you may have a failed card
controller on your system board.


Stew

Thanks for continuing to offer advice. I've reconfirmed the device is
and has been enabled in BIOS, I am confident the original driver was
installed properly, it had run for over a year prior to failure. I've
since attempted to install a new driver from Dell dated 3/07, but it has
not completed successfully due to the device not "Starting". I've rolled
back, uninstalled, reinstalled, but always end up the same place.

I fear you are right about the cardbus controller. I suspect I'll get a
new mother board as part of my warranty. I'll post any next steps and
hopefully progress. By the way, have you ever run across a list of the
codes as reported in the properties box of this device (code 10) in this
case?

Thanks again,
Jere


Jere -

No, I've not, but I feel sure such a list is out there on the web. Per
your post, I did a cursory search on the code 10 (I've actually seen it
before, but not for this device and not in a while).

I was hoping to find something that would show either a re-seating of the
card or a simple driver upgrade as a solution, but I didn't find that -
but I also didn't find any threads where bad/failed hardware was the
absolute conclusion.

You're obviously capable in assessing and t-shooting your own issue. My
only suggestion at this point is to not 'over-think' the apparent failure
by immersing yourself in error codes (unless that's something you really
enjoy).

My gut feeling at this point (since we now have TWO cards - one of them
new and behaving in exactly the same manner) is that the controller is
bad. I wish I were wrong, but you and I both know that driver installs in
WinXP are (generally) a slam dunk and don't require this much finesse.

At least you've got the 3 year default warranty, which beats fixing this
out of pocket.

Again, post back if you can once it's resolved. It helps everyone here
who might be following your problem.


Stew






.



Relevant Pages

  • Re: Dead Mobo or PSU?
    ... cleared out a bunch of dust and decided to buy a new heatsink and PSU ... was searching for a new driver to the new 8600 GTS, ... download and install that driver while the system was still shutting ... motherboard wasn't even going through post anymore. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Realtek AC97 audio
    ... Motherboard: ASRock K7NF-RAID, Realteck AC'97 audio chip integrated in the ... Now I am not able to install Realtek AC'97 audio. ... It is impossible to load a driver for this hardware. ... Problem is just the same and refer to the error code 39 (I do not know what ...
    (microsoft.public.windowsmedia)
  • Re: New Computer Boots Very Slowly..
    ... As for if you need to install the RAID drivers, check the motherboard ... I'm using two SATA drives but I did not install the RAID/AHCI Controller Driver since the two drives are not being used in a RAID. ... The pooper computer is SATA drives and I see the motherboard CD has a driver called RAID/AHCI Controller Driver but I didn't install that because I'm not using the two drives on a RAID. ...
    (microsoft.public.windowsxp.basics)
  • Re: crash during setup
    ... As you are setting up a RAID configuration, you will need to install it ... The motherboard disk should have a utility to create the ... motherboard drivers can be installed immediately after Windows has completed ... > a missing or incompatible driver for a disk subsystem. ...
    (microsoft.public.windowsxp.newusers)
  • Re: configuration process runs every time start Word 2007
    ... When you installed Office did you select Run from Disc or install on Hard Drive ... I've run Office Diagnostics, and the only answer I can find ... is that a OneNote driver and a Document Image Writer driver are missing - but ... or even if I should resolve it. ...
    (microsoft.public.office.misc)