Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site peora.UUCP Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!hjuxa!petsd!peora!jer From: jer@peora.UUCP (J. Eric Roskos) Newsgroups: net.micro.mac Subject: Re: SetFile DA problem Message-ID: <2015@peora.UUCP> Date: Mon, 10-Mar-86 10:19:57 EST Article-I.D.: peora.2015 Posted: Mon Mar 10 10:19:57 1986 Date-Received: Wed, 12-Mar-86 03:09:33 EST References: <413@zaphod.UUCP> Organization: Concurrent Computer Corporation, Orlando, Fl Lines: 31 wolfl@zaphod.UUCP (Wolf Lunscher) writes in <413@zaphod.UUCP>: > I have a problem with the SetFile DA, V?. The original posting above was posted to net.sources.mac, but I have redirected it here since net.sources.mac is not the proper place for discussions. The poster said he had problems with the SetFile DA. I also had problems back when I first started trying to use it, as a result of which I eventually quit using it. I was surprised that no one else had commented on the problem; I wrote to the person who posted the DA, who said "we've seen the problem but don't know what causes it", and I never heard any more about it. The problem was that certain events other than "open" events for the DA were interpreted as open events, causing the DA to spontaneously open itself. Subsequently a "bomb" would frequently occur. In particular, whenever a disk was ejected from the internal drive, the DA would spontaneously open itself; this forced the user to reinsert the disk again since the disk had to be in the drive in order for the open to succeed. I suspect that the problem the poster described might be related to the one I observed. I hope someone can fix it, as the SetFile DA was potentially one of the more useful DAs. -- Ofc: jer@peora.UUCP Home: jer@jerpc.CCUR.UUCP CCUR DNS: peo S Mail: MS 795; CONCURRENT Comp.ter Corp. SDC; (A Perkin-Elmer Compa 2486 Sand Lake Road, Orlando, FL 32809-7642 ---------------------- Obviously if I supplied LOTD(7) you'd know what was going to happen next, wouldn't you?