Uninstalling USB Drivers - 51417c
Uninstalling USB Drivers - 51417c
Uninstalling USB Drivers - 51417c
Note: If you have installed the drivers and been able to communicate without
errors initially, but then have experienced communication problems,
reinstalling the drivers may not solve your problems. Please refer to the
MPLAB® ICD 2 on-line help for possible software solutions before
attempting to uninstall/reinstall the drivers.
Note: If unsure which device listed is the tool being used, unplug the tool and
see which one disappears. Then plug the tool back in to see it
reappear.
4. Click once on this device to select it, and then right click on this device and select
“Uninstall” from the drop-down menu. Click OK on the warning.
Note: DO NOT unplug the tool from the USB port at this time. Leave it
plugged in.
3. For Windows 2000/XP, the permissions will need to be changed before the key
can be deleted.
a) Right click on the key and select “Permissions” (or select Security>Permissions.)
c) Ensure that the checkbox to allow inheritable permissions from parent to propa-
gate to this object is checked. This check box may be on the Advanced Security
Settings dialog (click the Advanced button) or may be on the main Permissions
dialog.
Note: Keep track of the INF file names that are deleted, because the
corresponding files with PNF extensions will have to be deleted as well. For
example, if OEM26.INF is deleted, OEM26.PNF will also need to be
deleted, if it exists. PNF files are not text files and cannot be searched like
INF files.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today, when used in the
intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these methods, to our
knowledge, require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data
Sheets. Most likely, the person doing so is engaged in theft of intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code protection does not
mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protection features of our
products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts
allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.
12/08/06