Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!hplabs!hpcc05!hpcuhb!hpcllla!hpclisp!defaria@hpclapd.HP.COM
From: defaria@hpclapd.HP.COM (Andy DeFaria)
Newsgroups: comp.windows.ms
Subject: Re: Windows 3.0/Multi-tasking/286 & DOS window shells?
Message-ID: <27220003@hpclapd.HP.COM>
Date: 20 Dec 90 21:31:08 GMT
References: <27220002@hpclapd.HP.COM>
Organization: Hewlett-Packard Calif. Language Lab
Lines: 23

>/ hpclapd:comp.windows.ms / bcw@rti.rti.org (Bruce Wright) / 12:08 pm  Dec 19, 1990 /

>This happens when the application is somewhat mis-behaved and loads
>the hourglass cursor while it does some compute-bound operation, but
>then doesn't relinquish the CPU to other apps in the system until it's
>through.  Windows _is_ multi-tasking, but only for cooperating
>processes;  a single ill-behaved task can cause the behavior you
>describe.  In general, if the application is going to have the
>hourglass displayed for more than a very few seconds (say 5), it
>_should_ relinquish the CPU and run in the background, only displaying
>the hourglass while it's the window with the input focus.  Too many
>applications _don't_ behave very well though.

You  got that right!    Considering the   application  in  question  are MS
supplied with Windows 3.0, are you  saying that even MS applications aren't
well behaved?

>I'm afraid that you'll either have to live with it or upgrade the
>CPU to a 386 of some flavor - a 386sx shouldn't be too different in
>cost from a 286 at this point.

My 286 is a loner from work so it cost me $0.00.  Do you know  where  I can
get a 386sx for the same?!?