After reading some posts. I discovered i have the exact same problem as mentioned underneath the dotted line But the solution provided underneath did not work. I did a clean XP pro install and it still didnt fix it.
I have linksys WPC11 v3. pcmcia Wireless card. And my laptop has two PCMCIA SLOTS. PCI Slot 1 (PCI bus 2, device 0, function 0) --Texas Instruments PCI-1520 CardBus Controller) AND PCI Slot 2 (PCI bus 2, device 0, function 1) -- Texas Instruments PCI-1520 CardBus Controller).
i am writing this post with Wirless card plugged in PCMCIA slot 1 and its working fine..and connecting.. but i take the same card and plug it in PCMCIA slot 2, it gives the This device cannot start. (Code 10) error.
Any one has fix different then whats mentioned underneath?
Title: Linksys PCMCIA Wireless Card Returns Code 10
asked by psolli on 07/18/2004 03:25PM PDT
This solution was worth 125 Points and received a grade of B
I had a Linksys WPC54G card working on my laptop, but suddenly it started to return Code 10, cannot start device. I have tried the card on another laptop and there it installs fine. Also a frinds Lucent wireless card installs fine on my computer. By doing that exercise I think both the card and the PCMCIA slot is working fine.
I have deinstalled, reinstalled and tried everything possible but I cannot get it to install correctly. I have seen many other posts about this but no successful solutions. In my Eventlog it returns"
Wireless-G Notebook Adapter : Has encountered an internal error and has failed.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp
Thanks in advance,
Send to a Friend Printer Friendly See Solution
Accepted Answer from swift1004
Date: 07/18/2004 04:46PM PDT
It's a registry corruption in the networking section. Unfortunately, after spending a total of weeks on this issue with multiple laptops and multiple PCMCIA cards, I found the only way to fix it is to reload the system from scratch. (I'm sure there's a way to fix in the reg, but I haven't found it) I've seen this with ethernet cards, wireless cards, modem cards, token ring cards, etc. It's not the card or it's specific driver....it's windows. Sorry for the bad news.