Thanks, I assumed any disassembly would lose comments, etc.=A0 It is the sa= me with other MCUs with which I have worked in the past.=A0 Although I can'= t say I haven't done something that stupid, it wasn't me this time.=A0 Some= one else lost the source code for this one.=A0 I am beginning to think it m= ight be easier to just do this from scratch myself. =A0 Thanks again, 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 Fri, 6/11/10, Olin Lathrop wrote: From: Olin Lathrop Subject: Re: [PIC]Copy from unprotected PIC then programming another PIC To: "Microcontroller discussion list - Public." Date: Friday, June 11, 2010, 6:43 PM RANDY ABERNATHY wrote: > I was told you couldn't disassemble the HEX code when read from the > PIC. From what you are telling me I can. Of course you can.=A0 Obviously the machine can interpret each instruction,= so some interpretation program could too.=A0 The problem is that while it is possible to create a assembly file that results in the code you have, it's only the bare instructions.=A0 It won't tell you the intent of the programm= er, and all original label names, comments, and module structure will be lost. All in all, if you've managed to lose the source code (look up something called "backups"), it's probably easier to start with the spec and write the code from scratch than to reverse engineer the dissassembly result. ******************************************************************** Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products (978) 742-9014.=A0 Gold level PIC consultants since 2000. -- = 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