Difference between revisions of "TSR"
(New page: TSR's were popular in the MS-DOS days as psudo multitasking. They would 'terminate and stay ready'. You could call them up with a hotkey and you could have them accessible from another p...) |
|||
| Line 4: | Line 4: | ||
Many debuggers ran as TSR's. | Many debuggers ran as TSR's. | ||
| + | |||
| + | I think the most popular TSR was Sidekick from Borland. Sidekick included a calculator, notepad, appointment book, basic terminal program, clip board among other things. | ||
| + | |||
| + | TSR's typically hooked the keyboard interrupt looking for a special sequence that would call them up, and interrupt the underlying program. More sophisticated ones would also hook the timer, and allow the 'foreground' program to continue to execute, a form of multitasking. | ||
{{stub}} | {{stub}} | ||
Revision as of 03:31, 3 July 2010
TSR's were popular in the MS-DOS days as psudo multitasking. They would 'terminate and stay ready'. You could call them up with a hotkey and you could have them accessible from another program.
These were VERY hard to program as MS-DOS was intended as a single tasking program.
Many debuggers ran as TSR's.
I think the most popular TSR was Sidekick from Borland. Sidekick included a calculator, notepad, appointment book, basic terminal program, clip board among other things.
TSR's typically hooked the keyboard interrupt looking for a special sequence that would call them up, and interrupt the underlying program. More sophisticated ones would also hook the timer, and allow the 'foreground' program to continue to execute, a form of multitasking.
