A
Archimedes' Lever
Guest
On Tue, 16 Dec 2008 07:17:21 -0500, "Bob Campbell" <bob@bob.bob> wrote:
I never used the task switcher predecessors. It still seemed a lot
like single tasking to me.
I used DesqViewX. It was the first OS that allowed remote processes. I
could run an app on another box, and get the screen and keyboard I/O on
my local workstation. So I could run things on dormant boxes anytime I
wanted a process to complete sooner than it would on my machine.
"Archimedes' Lever" <OneBigLever@InfiniteSeries.Org> wrote in message
news:emhek45o5h9rc9d91diaf8g8l6hd2sof1p@4ax.com...
On Mon, 15 Dec 2008 22:19:42 -0500, "Bob Campbell" <bob@bob.bob> wrote:
"Peter Hucker" <none@spam.com> wrote in message
newsp.ulyj5kqx4buhsv@fx62.mshome.net...
DOS simply loads TSRs, it doesn't 'manage' them.
Then what gives each program time on the CPU?
DOS is single-tasking. In DOS, there is only ever one program at a time
executing. The currently executing program "owns" the machine. There
is
no "executive", there is no time slicing of CPU time.
I fell in love with DesqViewX. It was among the first for the early
x86 architectures to slice things up well.
Yeah, I ran DesqView and DV 386 (not X) for years. I actually got X but
never used it.
I never used the task switcher predecessors. It still seemed a lot
like single tasking to me.
I used DesqViewX. It was the first OS that allowed remote processes. I
could run an app on another box, and get the screen and keyboard I/O on
my local workstation. So I could run things on dormant boxes anytime I
wanted a process to complete sooner than it would on my machine.