Mike Riendeau wrote: > You could also write a macro at the end of your program > which fills empty EEPROM with reset vectors. Mike: Bad idea. First, it's unnecessary; the "empty" code-space is ALREADY filled with instructions that won't affect program flow. The PC will just increment through them until it wraps around to 0000 and hits the reset vector. Second, what will those "reset vectors" look like? Just a bunch of GOTOs? How's that going to work on a processor whose code-space is paged? Even if you're a little clever about this, it's unlikely that your "solution" would be more reliable than simply leaving the unused space in its erased state. -Andy Andrew Warren - fastfwd@ix.netcom.com Fast Forward Engineering, Vista, California http://www.geocities.com/SiliconValley/2499