I wish somebody would know how to fix the registry. This was my assumption as well, but I am not looking forward to w weekend of rebuild....Anybody?
Per
Main Topics
Browse All TopicsI 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"
Source: BCM43xx
EventId: 5005
Type: Error
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/fw
Any ideas?
Thanks in advance,
Per
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I know this question is dead, but I had the same problem and worked on the problem for a number of days. I reinstalled Win XP that did seem to fix it for a while, but then it went back to the same problem (probably after I ran some of the windows updates). Anyway, I worked on this problem and it drove me crazy because there was nothing on the web about it. However, I eventually found something that seemed to work though I don't know why. Here it is:
You need to change the permissions in your registry of one of the PCI related folders. I had two cards and the first one just required me to change the permissions on the PCI registry folder, but the second card required me to change the permissions of its parent folder (Enum). Anyway, you should try just change the PCI folder permisions first and if that doesn't work then change its parent folder (Enum). Here is how:
First with the card in, goto Device Manager and uninstall the driver.
Then goto Add and Remove programs in Control panel and uninstall the cards software.
Then shutdown the machine and remove the card and reboot.
Then click Start|Run
Type in RegEdit
Locate HKEY_LOCAL_MACHINE | SYSTEM | CurrentControlSet | Enum | PCI
OR
Locate HKEY_LOCAL_MACHINE | SYSTEM | CurrentControlSet | Enum
Highlight whichever you are going to change the permissions of (that is, highlight PCI or Enum).
Right click on it and select the Permissions option.
Now, you can change the permissions in a lot of differnet ways. I went ahead and added the Administrator Group and then gave that group Full Access. But you could also simply give the Everybody group Full Access. I think that you can change everything back after you get the driver installed, but I just left the Adminstrator Group with Full access on mine.
Ok, now reinstall your Network Card software, reboot your machine, Insert your network card and let it install the driver.
Then after you see that it is working you can go ahead and try changeing the permissions back in the same places in the registry (though, I didn't change it back so I'm not sure if it will cause the problem to occure again).
In any case, you will be surprised that it works for you, but odds are it will. I was suprised.
[ Code 10 PCMCIA PCCard PC Card LinkSys DLink D-Link Network Ethernet WinXP Registry NetGear Net Gear Wireless Belkin Sonicwall Cisco ]
I had a similar situation but with a pcmcia card. So following the steps listed in Enlade's post above, instead of adding the admin group I chose the system account that was already there with inherited full and read permissions. Next, click on advanced and change the check box FROM inherit TO replace. When given the option to copy or remove, choose COPY. Bingo! I removed the card from the device manager and let the machine find it again and install its drivers. After a reboot the card started perfectly.
Good day. After a frustrating weekend of trying the above tips on changing various registry permissions on my wife's ThinkPad R40, I have not resolved the Code 10. Everything seems to work until Windows is installing the drivers for the Belkin F5D6020 PCMCIA card - then the lights on the card go from "Green" to "out" and I get the Code 10. I have downloaded the latest drivers and this card works fine on my T40. Both machines are running XP.
So, before I schedule a day to reload the machine with new OS, I wanted to ask:
1. Any other suggestions out there?
2. Since I am a bit of a neophyte, any suggestions on how to back up all of the stuff on the machine prior to starting the reload so that rebuilding will be less painful?
Business Accounts
Answer for Membership
by: swift1004Posted on 2004-07-18 at 16:46:54ID: 11579811
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.