__/ [ John Locke ] on Monday 23 April 2007 22:53 \__
>>Windows uses non-preemptive multi tasking, so that Windows applications
>>contend with each other for system time. In this environment, one
>>application or process can seize the system and deny system access to
>>other applications until that application or process is finished.
>>Similarly when a process that has control of the system depends on the
>>completion of an external event (such as receipt of a message from the
>>network), this one process can hold up the whole system while it waits
>>for the event to occur.
>>
>>As a result, Windows users often find that their applications really
>>don't "multi-task" under Windows. This weakness in Windows is especially
>>disruptive in networked environments.
>
> I ran OS/2 when I worked for the government. Very robust OS.
> I reaaly liked its ability to multi task. The we were forced to move
> to Windows 3.1. ugh...It reaaly had a negative impact on our work
> perfromance.
>
> As far as I know, multi tasking is still a problem with Microsoft
> operating systems to this day.
Coupled with the fact that there is just one virtual desktop and one virtual
terminal...
--
~~ With kind regards
Roy S. Schestowitz | while (sig==sig) sig=!sig;
http://Schestowitz.com | Open Prospects ¦ PGP-Key: 0x74572E8E
Tasks: 103 total, 1 running, 99 sleeping, 0 stopped, 3 zombie
http://iuron.com - knowledge engine, not a search engine
|
|
