Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcsun!ukc!axion!vision!ukpoit!paul From: paul@ukpoit.co.uk (Paul Wood) Newsgroups: comp.os.minix Subject: Re: macminix Message-ID: <1655@ukpoit.co.uk> Date: 31 Dec 90 13:32:16 GMT References: <1990Dec22.1046.1132@canrem.uucp> Reply-To: paul@ukpoit.co.uk (Paul Wood) Organization: iT - The Information Technology Business Of The Post Office Lines: 30 Summary: Expires: Sender: Followup-To: In article <1990Dec22.1046.1132@canrem.uucp> "glen lalonde" writes: >Problems: > The recent changes have enabled me to boot MacMinix from >multifinder but it dies after about four minutes. I have >a 4MB Mac+. I get this, even under the plain Finder. If I start up MacMinix, and then DON'T DO ANYTHING except go make a cup of tea, not even login, then when I get back I'll have had a system crash. My guess is that my problem with the plain Finder and yours with the MultiFinder may well be related. Is something eating the heap or stack? >**** MacMinix upon boot overwrites the address error trap handler >address in low memory! This will cause a great number of problems, >since address errors will not drop you into macsbug but will cause >strange system behaviour. Most of the time the internal drive will >start to run, for no reason at all, after a little while of runnning >some bad code it will just crash the system. I get this as well. The internal drive (without a disk in it even!) will start running, eventually resulting in a system crash. I have attributed it to cron. Do you have cron running? Recently someone on the net recommended putting "extern char *malloc();" in cron, but that didn't seem to fix the problem for me. Ideas anybody? My current solution is to not run cron - great eh! :-( Thanks, Glen, for the interesting stuff that I have omitted. Paul Wood | UUCP Mail: paul@ukpoit.co.uk 31 Buttermere Drive, Dronfield Woodhouse, | Bang-Style: ...!ukc!ukpoit!paul Sheffield, England, S18 5PX | Voice: +44 246 418031