philip@utstat.uucp (Philip McDunnough) (08/20/90)
Some new DA's are (probably) the source of error 0877("unclaimed sound
interrupt"). I seem to have tracked this down to a Bill the Cat NDA called
Ack.
Also the NDA called TWGS shifter seems to cause problems, but I can't be
sure.
Is there a utility of sorts which will indicate an offending program? That
is, is there a program available which associates errors with programs and
vice versa?
Philip McDunnough
University of Toronto
philip@utstat.toronto.edu
[my opinions]dlyons@Apple.COM (David A. Lyons) (08/21/90)
In article <1990Aug20.021901.28351@utstat.uucp> philip@utstat.uucp (Philip McDunnough) writes: >[...] >Is there a utility of sorts which will indicate an offending program? That >is, is there a program available which associates errors with programs and >vice versa? No, probably not. Sure, you could write something that tells you which application or DA actually made the call to SysFailMgr, but that doesn't tell you whose fault it was that the unrecoverable condition came about. In general, somebody actually has to look at the code & see who's doing what wrong. -- David A. Lyons, Apple Computer, Inc. | DAL Systems Apple II Developer Technical Support | P.O. Box 875 America Online: Dave Lyons | Cupertino, CA 95015-0875 GEnie: D.LYONS2 or DAVE.LYONS CompuServe: 72177,3233 Internet/BITNET: dlyons@apple.com UUCP: ...!ames!apple!dlyons My opinions are my own, not Apple's.
paul@nuchat.UUCP (Paul Hutmacher) (08/21/90)
In article <1990Aug20.021901.28351@utstat.uucp> philip@utstat.uucp (Philip McDunnough) writes: > >Some new DA's are (probably) the source of error 0877("unclaimed sound >interrupt"). I seem to have tracked this down to a Bill the Cat NDA called >Ack. Bill cause problems? I've had it in my DA directory for a few months now and have not had any problems I could trace back to it. Why do you need a Bill DA? It makes a good second opinion when you're writing with AWGS of course! ("What do you think Bill?" "Ack ack ack.") -- Paul Hutmacher | paul@nuchat.UUCP |Sometimes the only thing a P.O. Box 66046 | {uhnix1, uunet}!nuchat!paul |western savage understands Houston, TX 77266| paul%nuchat.uucp@uhnix1.uh.edu|are whiskey and rifles and 713/526-0612 CDT | "Ai Carumba!" |an unarmed man like you.
joseph@elbereth.rutgers.edu (Seymour Joseph) (08/22/90)
What give me the most headaches is that the GS environment is so complicated that it is quite common for multiple NDAs, CDAs, INITs or applications to be doing things wrong. I have loaded and unloaded inits, and das until I was dizzy but still don't know why some things screw up. I find the database module of AppleWorks GS to be the most often affected application. I will have a database open and be updating data, and after a while will notice that some fields have been corrupted. If I save the file then, it cannot be reloaded, and trying to fix the corrupted fields causes others to be screwed up. I think I tracked this down to two NDAs called WriteIt! and DeskPaint! (I may have the names wrong, they were by the same author and were a Write/Paint NDA set. I liked them a great deal, but when they are installed AppleWorks GS eats my databases for lunch. I have had other interactions too. StartSound by Guy Rice would keep SoftDiskGS from starting correctly. There are still more that I have been unable to track down. I used to download and try NDA's all the time. Now, after being burned, I am much more cautious. Unfortunately I still no of no way of finding out if it will cause a problem besides trying..... Seymour
gwyn@smoke.BRL.MIL (Doug Gwyn) (08/23/90)
In article <Aug.21.18.57.46.1990.6035@elbereth.rutgers.edu> joseph@elbereth.rutgers.edu (Seymour Joseph) writes: >I used to download and try NDA's all the time. Now, after being >burned, I am much more cautious. Unfortunately I still no of no way >of finding out if it will cause a problem besides trying..... While it is possible to automatically detect some such programs that WILL cause problems, it is inherently impossible to devise a practical procedure that will reliably catch ALL programs that could cause problems. The reasons for this are obvious to anyone who paid attention in their CS classes.
toddpw@tybalt.caltech.edu (Todd P. Whitesel) (08/23/90)
Mac users have been putting up with flaky DA's for much longer than we have. Caution is always advised when trying out new stuff for your system. Todd Whitesel toddpw @ tybalt.caltech.edu
bchurch@oucsace.cs.OHIOU.EDU (Bob Church) (08/24/90)
In article <13645@smoke.BRL.MIL>, gwyn@smoke.BRL.MIL (Doug Gwyn) writes: > > While it is possible to automatically detect some such programs > that WILL cause problems, it is inherently impossible to devise > a practical procedure that will reliably catch ALL programs that > could cause problems. The reasons for this are obvious to anyone > who paid attention in their CS classes. CHAOS theory is getting a lot of attention these days. I personally think that one of the first practical applications will be in debugging. I'm serious. If a home computer with a dozen DA's is too complex to completely predict think about new systems for running airports, etc. ******************************************************************** * * * bob church bchurch@oucsace.cs.ohiou.edu * * * * If economics isn't an "exact" science why do computers crash * * so much more often than the stock market? * * bc * ********************************************************************