TSR - Revision history

Jnc: +cat

2019-01-01T13:28:02Z

+cat

Jnc: Proper cat, +links

2018-10-21T19:03:35Z

Proper cat, +links

Tor: Typo

2016-01-25T13:06:32Z

Typo

Neozeed at 15:16, 4 July 2010

2010-07-04T15:16:44Z

Neozeed at 01:31, 3 July 2010

2010-07-03T01:31:32Z

Neozeed: 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...

2009-10-18T04:33:27Z

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...

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 program.

These were VERY hard to program as MS-DOS was intended as a single tasking program.

Many debuggers ran as TSR's.

{{stub}}

← Older revision		Revision as of 13:28, 1 January 2019
Line 10:		Line 10:

	{{semi-stub}}		{{semi-stub}}
		+
		+	[[Category: DOS Enhancements]]

@@ Line 1: / Line 1: @@
-TSR's were popular in the MS-DOS days as pseudo multitasking.  They would 'terminate and stay resident'.  You could call them up with a hotkey and you could have them accessible from another program.
+'''TSR''''s were popular in the [[MS-DOS]] days as pseudo [[multi-tasking]].  They would 'terminate and stay resident'.  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.
+Many [[debugger]]s 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.
+TSR's typically [[hook]]ed 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.
+{{semi-stub}}

← Older revision		Revision as of 13:06, 25 January 2016
Line 1:		Line 1:
−	TSR's were popular in the MS-DOS days as ~~psudo~~ multitasking. They would 'terminate and stay resident'. You could call them up with a hotkey and you could have them accessible from another program.	+	TSR's were popular in the MS-DOS days as pseudo multitasking. They would 'terminate and stay resident'. 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.		These were VERY hard to program as MS-DOS was intended as a single tasking program.

← Older revision		Revision as of 15:16, 4 July 2010
Line 1:		Line 1:
−	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.	+	TSR's were popular in the MS-DOS days as psudo multitasking. They would 'terminate and stay resident'. 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.		These were VERY hard to program as MS-DOS was intended as a single tasking program.

← Older revision		Revision as of 01:31, 3 July 2010
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}}