Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!uxh.cso.uiuc.edu!archetyp
From: archetyp@uxh.cso.uiuc.edu (Joseph R Pickert)
Newsgroups: comp.os.minix
Subject: Re: Macminix: Crashes...help...
Message-ID: <1990Nov8.145758.6845@ux1.cso.uiuc.edu>
Date: 8 Nov 90 14:57:58 GMT
References: <15498@brahms.udel.edu> <1250001@hpcuhc.cup.hp.com>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 26

rterry@hpcuhc.cup.hp.com (Ray Terry) writes:

>MacMinix seems to be running okay on my 6.0.7 Mac II.  One thing that I 
>did notice is that it doesn't get along with the Virtual INIT.  This is 
>the very first program that I've encountered that doesn't...  With Virtual
>in, MacMinix will not boot.  It hangs the Mac.

Yes, I'm aware of the Virtual problem.  The people who make it and
I are currently exchanging respective software in hopes of finding the
problem.

Also, as some people have found out, MACMINIX does not seem to
get along with many screen savers and some inits. This is because
these programs (and some other programs as well) simply take over
the machine and start doing their thing whenever they want, on
whatever stack happens to be active (which they assume to be the
one and only application stack).  This is not a good thing,
since some of the Quickdraw routines use significant amounts of
stack space.

Screen savers should only take over the machine only at a Mac OS
call boundry (GetNextEvent would be best).  If they did this, there
would be no problem because MINIX switches to the main application
stack before doing Mac OS calls.  Inits should use their own stack.

Joe Pickert