Bonjour Sylvain!
SL> > When a character is received, it generates an interrupt which
SL> > goes back to the terminal. The terminal would then hopefully save the 
byte
SL> > to disk and then exit. The computer would be switching back and forth
SL> > between the terminal and the TSR.
SL> Okay, here is what i understand of this.
SL>  |Terminal|                       Goes back to terminal  <--=
SL>      |                            Save the byte, but how     |
SL> |Key pressed| -> |TSR program|    it returns control to      |
SL>                      |            TSR program. And how       |
SL>                      |            it doesn't overwrite the   |
SL>                      |            current TSR window?        |
SL>                      |                                       |
SL>                  |Irq interrupt| (bytes received) -----------
That's about what I was thinking of, but more like:
|Terminal|
    |
|key press| -> |TSR program|   <- back to TSR --------
                   |                                  |
              |incoming byte| -> |Terminal receive| --
I'm guess that, if the terminal uses IRQs, then when a byte was received,
the handler just gets and saves it. So things like the screen wouldn't get
refreshed, but the file would download. Mind you thinking how it works and
how it actually works are two different things. The TSR could just stop
terminal, where you end the terminal.
SL> > everything down. For example, if I load the VSAFE TSR and pop
SL> > it up, my blinky program stops.
SL>Hum,
On the other hand, I my blinky program is installed, and I try a download,
both go on as normal. The transfer would still take place, and the LED would
blink as well. Though is this is slightly different then activating a TSR
program.
Perhaps I'll try it out with various programs and see what happens.
Cheers,
    Denis Boyles
 * OLX 2.1 TD * hAS ANYONE SEEN MY cAPSLOCK KEY?
--- Maximus/2 3.01
---------------