[Elecraft] [K*] Hooks into the RTOS for an API

[kevinr]

When the original Macintosh was introduced it booted from ROM.  Hooks 
were provided in the ROM code to allow external fixes to the OS.  An API 
was released so application or OS programmers could modify the existent 
code.  There are good and bad sides to this.  In the case of the K2, K1, 
K3 (and most probably the KX1 and KX3) the timing of the RTOS is fairly 
strict.  If an API programmer added their own code through the hooks 
into the RTOS the timing would change for many things.  You could write 
your own code and add it to the mix but then the RTOS timing would be 
upset and you would most probably break many things.  The interactions 
between the many and varied tasks of the RTOS would change and mostly 
for the worse.  I realize the RTOS code for the Elecraft gear will never 
be released to the public.  So the work of adding new tasks to the 
timing loops of the rigs' RTOS falls on the in-house code jockey(s).  
Remember this when you ask for new features or tweaks to existing code.  
Do you want a rig that works quickly and smoothly when you enter 
commands via the front panel or the serial bus?  Or would you rather 
have a kluge of mashups?  Don't ask about the divergent meanings of 
kluge and kludge.  I appreciate the effort the Elecraft team has put 
into making fine products which work well.
    73,
        Kevin.  KD5ONS