🚀 go-pugleaf

I'm having trouble with the following piece of vt100 2.8a scripting.  Depending
 on the rest of the script (what I don't know) if KR (Kermit receive) fails,
the script will terminate rather then executing the next line.

ON              # turn off MORE trapping
ON "term" GOTO EndLoop1
WAIT "xyzzy"
#--------download loop ------------
SEND ^M   /* signal back to mainframe that we are ready */
TopLoop1:
        WAIT "file(s)."
        KR
        delay 1
        SEND ^Q         /* clear parity error */
        SEND ^M         /* signal exec that we're ready */
goto TopLoop1
EndLoop1:
SEND ^M

This code is supposed to be self contained and as best I can tell, it is.
But.  I've got three large scripts that contain this exact code.  In one it
works, and in the the other two a failed kermit receive will abort the script.

Does anyone know what causes this and perferably could suggest a work around?

Now, before I get flooded with replies telling me to upgrade to 2.9xx, that
won't work.  This code cannot function without the ability for an ON statement
to interupt a WAIT.  The inability of an ON in vt100 2.9xx to interupt a wait
statement is IHMO the biggest misfeature of the program.

Eric Edwards: c506634 @    "The 3090.  Proof that by applying state of the
Inet: umcvmb.missouri.edu   art technology to an obsolete architecture,
Bitnet: umcvmb.bitnet       one can achieve mediocre performance."