Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!umeecs!shim
From: shim@zip.eecs.umich.edu (Sam Shim)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Why use MS-window ?
Message-ID: <2472@zipeecs.umich.edu>
Date: 31 May 90 21:59:31 GMT
References: <404@newave.UUCP> <10509@ingr.com> <54985@microsoft.UUCP>
Reply-To: shim@eecs.umich.edu (Sam Shim)
Organization: University of Michigan EECS Dept., Ann Arbor, MI
Lines: 25

In article <54985@microsoft.UUCP> derekho@microsoft.UUCP (Derek HOIEM) writes:
>OS/2 is the operating system capable of *real* multitasking.  OS/2 has
>"threads" which are processes that can be happening at the same time.  For
>example, I can be formatting a floppy disk and downloading a file without
>noticeable system degradation in speed.   Pagemaker for OS/2 is a great
>example of how threads can be utilized for real multitasking.

Huh?  Is it true that in a single processor chip, multi-tasking is
accomplished by time-slicing since the processor can handle only 1 thing
at a time.  You might be able to break the time-slices into very small
amounts but it is not possible to have a single processor chip do true
multi-tasking relative to a multi-processor chip.  Sounds like you are
taking on the high-level operating system level.  I just want to clarify
that in the low-level hardware level, OS/2 uses time-slicing to multi-task,
as would any single chip computer that multi-tasks.



 -----------------------------------------------------------------------------
|  Sam Shim                                   | "I didn't do it...            |
|  EECS Departmental Computing Organization   |  It wasn't me...              |
|  University of Michigan                     |  Nobody saw me do it...       |
|  Ann Arbor, MI 48109                        |  Nobody can prove a thing..." |
|  internet: shim@eecs.umich.edu              |  - Bart Simpson               |
 -----------------------------------------------------------------------------