🚀 go-pugleaf

On Fri, 2 Feb 1996, Martin Nisshagen wrote:
> Fredrik.Pettersson@sto1.wmdata.se wrote:
> 
> > >Is it?  Pray tell, how is MacOS multitasking the following "application":
> > 
> > >main() { for(;;); }
> > 
> > I did one of those on a NT at work and it really shared processor time nicely,
> > 100% to that process and nothing to the other applications.

I missed the original thread, but sure, the above application will get
100% of the CPU time, IF there is no other process operating.  BTW, how
did you tell?  Did you use Performance Monitor, PWatch, or ps?  You must
have had some way of telling, since a process monitor must also be another
process...


> A friend of mine made an aproximatley comparable application that uses all CPU
> and never yeilds it to the OS.
> 
> He tried it on Win95 and NT. On Win95 it locked all other applications from
> getting any CPU, but on Win NT it multiasked just fine with other applications
> who got their share of the CPU.

Must be a 16-bit application.  I'm not aware of any 32-bit application that
will crash WinNT (possible exception to Microsoft's products...).

 
> > So if you write your applications badly they will lock system more or less even
> > in a preemtive environment.
> 
> Have never happend on my NT system. Maybe I can download your application and try
> it?

Agreed.  Under a preemptive environment, misbehaving applications cannot
crash the OS.  I guess a stronger classification would be OSes which
have "modern microkernel OS features".


Regards,

Walter Hsueh
hsuehw@ecf.utoronto.ca