I had plenty of experience with long cable problems, but they showed up as an inability to debug. They would identify OK every time, and program successfully most times. Single-stepping is where it would fall down. So, ID=3D0 doesn't sound as likely to me to be a cable. Nonetheless, your comment about your "cobbled" and "shaky" cables struck a chord here. My fallback cable when I was having problems was the first one I built; it was patched together and has one extra wire added after I discovered one was missing, and the poor thing is even intermittent. But, it always would work where the others would fail! Owing to this, I had another tactic besides shortening the cables. Remove the jacket and otherwise separate the conductors to reduce crosstalk. This is what gives the cables their cobbled/shaky look, but it can pay off. Oddly enough, when I upgraded to the ICD3 (and real ICE), the cable problems went away. Subsequent can't-identify-the-chip problems have turned out to be actual broken cables, and failure to remember to turn on target power (or set "ICD supplies power" in the settings) Barry On Thu, Feb 23, 2012 at 5:09 PM, wrote: > ...So as a last gasp, I stuck a 30F3013 on one of > those stupid proto boards, used a very shaky cable, and it worked first > time out! > --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .