I would say chip to chip since I have=A0 been reading the old PIC with my p= rogrammer then inserting another and attempting to burn it.=A0 I know that = normally, when a PIC is protected you usually show all FFFF in the memory a= nd the protected chips I do have show exactly that, however this one does n= ot, it has different HEX data in each address location which leads me to th= ink it truly isn't protected.=A0 The person that sent it to me said it wasn= 't.=A0 It is from a rather old controller that operates a heater, fan, etc.= and he couldn't find any of the actual source code left in his files.=A0 W= hich doesn't surprise me. Randy Abernathy CNC and Industrial Machinery = service, repair, installation and = design 4626 Old Stilesboro Rd NW Acworth, GA 30101 Fax: 770-974-5295 Phone: 678-982-0235 E-mail: = randyabernathy@bellsouth.net --- On Thu, 6/10/10, ivp wrote: From: ivp Subject: Re: [PIC]Copy from unprotected PIC then programming another PIC To: "Microcontroller discussion list - Public." Date: Thursday, June 10, 2010, 7:30 PM > I take it that the programmer may report no protection but in > reality there might be protection If you look at the hex file you'd soon find out whether you have blank data. Are you doing this through an editor or just chip-to-chip ? -- = http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist -- = http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist