Sorry James, Thunderbird seems to have defaulted to send direct as=20 Private message. Apologies. Resent to Piclist. I would tend to agree with James. When you cross the XP / 7 and on-wards barrier, you do come up against=20 this sort of silliness , where sometimes software, sometimes hardware is=20 preventing access to the low level USB hardware (or other hardware),=20 because, it in fact thinks (this is specially true for W7 on-wards) your=20 connected hardware maybe malicious. This is not necessarily pointing to your said possible antivirus=20 software, (third party or otherwise), which you may have installed. One case, I saw was, "...that's old aka XP...". so software won't let=20 that connect or run... Fix the naming conflicts in software and then things are different. It seems to be, if you say it, many people just buy new...! I say this because, knowing the insides of XP, and seeing the horror=20 show of moving almost anything in terms of XP connectable hardware to W7=20 on-wards, makes me shudder. I have spent years in this field, and still=20 W7 on-wards don't please me, with the things done to these OS's. A recent example that happened, where I moved some image scanning=20 hardware from XP to W7. the horror show that unfolded lead me to=20 believe, that many manufactures (will not name them) do this simply for=20 revenue. If I went down the path of the manufactures, the hardware would be dead=20 scrapped now. I refused this option. However many of my customers, have taken the replace option and simply=20 scrapped their troublesome hardware and replaced with something else,=20 often from the same brand/manufacture. I discovered what James is saying to be true, when I went deep into the=20 hardware/software trouble. Now I have got past that silliness, but took some doing. Don't think because it worked before on MS OS, that when you change to a=20 newer OS, it will work. Think again. Also don't think that forcing compatibility will be the answer either! It is in my opinion been planned this way. If a hardware descriptor or key or both, and/or as James says: "...A=20 vectored filtering application..." has simply stepped in. You may never really know, without lots of=20 headaches, the real cause. In the past, I have fixed some OS upgrade, hardware conflict silliness=20 with software manipulation, some so simple it's not funny. As for my scanning hardware, bypassing many bits of software, and=20 rehashing, it now works. You may find it is the OS and not the hardware, causing the issue. I still prefer XP. 32 or 64. Peter. ------------------------------------------------------------------------ On 1/01/2018 7:32 AM, James Cameron wrote: > Possibly a software interloper. A vectored filtering application > "protecting" you from malicious USB devices. Anti-virus tools. > > You might test for this by either; > > (a) install the same tools on the inner operating system on the VM, > or; > > (b) disable or remove the tools from the outer operating system. > > The other root cause that springs to mind is a race condition on > too-fast hardware, but that seems unlikely. > > On Sun, Dec 31, 2017 at 08:12:25PM +0000, David C Brown wrote: >> Just rechecked and it is windows 7 not 8 that I am running. >> >> As you say: if it was a driver issue I would expect the ICD2 to fail >> completely. As it is it connects OK; it will program Ok; it just >> can't connect to the debugger in the PIC. >> >> But that is the only difference. The cables are identical and I have >> made new cables from the ICD2 to the chip. Baffled. --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .