Re: Additional Info: Lattitude D620 Inbuilt Wireless died
- From: "S.Lewis" <NVRambo@xxxxxxxxxx>
- Date: Sat, 29 Dec 2007 10:04:42 -0600
"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
Thanks for continuing to offer advice. I've reconfirmed the device is and
"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
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
.
- References:
- Lattitude D620 Inbuilt Wireless died
- From: JCMc
- Additional Info: Lattitude D620 Inbuilt Wireless died
- From: JCMc
- Re: Additional Info: Lattitude D620 Inbuilt Wireless died
- From: JCMc
- Re: Additional Info: Lattitude D620 Inbuilt Wireless died
- From: S.Lewis
- Re: Additional Info: Lattitude D620 Inbuilt Wireless died
- From: JCMc
- Lattitude D620 Inbuilt Wireless died
- Prev by Date: Re: OT--Desktop Icons and Bootup Speed
- Next by Date: Re: OT--Desktop Icons and Bootup Speed
- Previous by thread: Re: Additional Info: Lattitude D620 Inbuilt Wireless died
- Next by thread: Vista to XP
- Index(es):
Relevant Pages
|
