Quote:
|
Originally Posted by Thorn
You're welcome. As to the solution, I don't know, simply because I can't see it. I don't belong to the Experts Exchange.
|
Neither do I.
My apologies. I had been viewing a cached version:
http://209.85.165.104/search?q=cache..._21062798.html
You have to scroll to the bottom of the page for the replies. That's where I saw (via a Google search) that someone reported these symptoms in relation to my card. (SoccerSam16)
Enlade lays out the fix, and WooDaddy tweaks it appropriately. It sounds good, but I've not done that kind of regedit before. Mine have (on my
desktop) been all for changing icons and drive names.
What's your take on that?
Quote:
|
Originally Posted by Thorn
In general, the biggest problem with a Registry edit isn't that you lose or gain security (although that may be an issue), but rather that you screw up the Registry completely. The simple solution to that is simply copy the Registry .dat files before the edit. Then, if you screw it up, or the edit doesn't have the desire results, you copy the .dat files back, and you're no worse than when you started. There are plenty of sites out there describing the backup procedure. Making an "XP Restore Point" is probably the easiest way to do it.
|
Yeah, I had planned on that, but I wondered about security in relation to granting permissions. I naturally assumed that if there weren't any, there's usually a reason.
Quote:
|
Originally Posted by streaker69
The registry is not as scary as a place to play in as everyone would make it seem to be. I've done hundreds of edits across dozens of machines over the years and have not had one bad issue yet.
If a site gives you exactly what key to change, no biggie, just go change it. It isn't like that one key related to your NIC is going to cause your entire machine to self destruct.
Now there are certain areas you don't want to go into unless you know exactly what you're doing, but making one or two changes to a driver configuration ain't gonna hurt nuttin'.
|
Oh, I know that. My worries were over opening up certain avenues to hackers, trojans or malware etc. I'm not sure they could take advantage of the new settings, but again, I don't know, and wanted to ask.
In case it disappears somehow, here's the relevant part I had referred to:
Quote:
Comment from Enlade
Date: 02/12/2005 10:33PM PST
Comment
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 ]
Comment from WooDaddy
Date: 06/27/2005 06:28AM PDT
Comment
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.
Comment from SoccerSam16
Date: 07/05/2005 07:35AM PDT
Comment
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?
|