> that the memory cell is not rewritable. I would like to hear what happens
> with a 16C84 part? Do you have to erase it or does it erase byte by byte
> -- Lauri

It can do a byte erase. I am a bit disappointed to hear that the 16F84 has
to completely erased during each programming cycle. With the 16C84, very
fast program/edit/debug/assemble cycles can be achieved if the changes are
made at the end of the code, which is easily arranged, as only the changed
bytes are reprogrammed.

Additionally, whilst I am here, I have a macro BND, which generates a ORG at
the next 16 byte boundary. This when placed between procedures, not only
eats ROM, but allows edits to be made without displacing all the code. This
increases programming speed, but alas, only on EPROM based devices.

It looks something like this:

BND     MACRO
        ORG     $+(16-($ & 15))
        ENDM

That _should_ be OK. 16 bytes is chosen arbitrarily, but gives good results.
8 might be worth a go too.

Bye,

Stuart.