BB> OXC3 seems to come to mind (that 
BB> is a one-byte RET instruction). The clever bit is what you 
BB> do to restore the original code when you reach the 
BB> breakpoint. The ret instruction fills the bill because it 
BB> pops the return address off the stack and allows you to 
BB> implement a standard procedure at that point.

I ran into a friend, a professor at a nearby college, who explained how 
the hardware portion of this situation worked (he's a hardware guy, 
after all).  Now you've added the software piece to the puzzle solution.  
Thank you.

þ CMPQwk 1.42 999

--- Maximus/2 3.01