Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!mailrus!purdue!decwrl!decvax!tektronix!percival!billc From: billc@percival.UUCP (William Coldwell) Newsgroups: comp.sys.amiga.tech Subject: Re: Negative Open Counts (was Re: IEEE libraries) Message-ID: <1369@percival.UUCP> Date: 19 Sep 88 06:09:21 GMT References: <6988@gryphon.CTS.COM> Reply-To: billc@percival.UUCP (William Coldwell) Organization: Percy's UNIX, Portland, OR. Lines: 26 In article <6988@gryphon.CTS.COM> bilbo@pnet02.cts.com (Bill Daggett) writes: >My concern and 2 cents about GURUing, as an end user point of view and not >developer/programmer would be that instead of staring at a meaningless >flashing number on the screen, the machine could just go into a warm boot and [stuff deleted] > >Bill > >UUCP: {ames!elroy,}!gryphon!pnet02!bilbo Actually, how about when the Amiga barfs, to tell which task is barfing, and allow the user to terminate the task and flush the resources and libraries (pending a fix to the -# usecount)? I think that this would be more of a visual help to the user rather than shutting the whole system down. GOMF seems to do a pretty decent job of remeding the situation... how about a real fix? I mean, hell if the operating system is going to be revamped, why not handle a stray task a little bit better? Bill -- William J. Coldwell Creative Microsystems "We the unwilling, Amiga Attitude Adjuster 10110 SW Nimbus B1 led by the unknowning, (Software Developer) Portland, OR 97223 are doing the impossible, "Blame the hardware" (503) 684-9300 for the ungrateful..."