[net.micro.mac] Set File DA vs. New System

davidl@orca.UUCP (David Levine) (05/22/85)

As someone on the ARPAnet noticed, the Set File DA bombs when installed into
a copy of the System file provided on the recent software update.  However, 
I discovered that it would work when installed into a DIFFERENT new System 
file.  I'm not certain of the vintage of this particular System file, but I 
suspect it's an updated old System rather than a copy of the new System.  Then
again, it could be a copy of the System from the Write/Paint update disk rather
than the System update disk.

Anybody care to speculate what the differences are that could cause this
crash?

David D. Levine  (...decvax!tektronix!orca!davidl)          [UUCP]
                 (orca!davidl.tektronix@csnet-relay.csnet)  [ARPA]

jer@peora.UUCP (J. Eric Roskos) (05/23/85)

Actually, the Set File DA tends to "bomb" a lot on a 128K 1-drive system.
At least, this is true of the version I have.  It seems to respond to events
other than those directed to it: it also spontaneously opens itself when
you eject a disk, sometimes. (I noticed a posting in here about a month
ago complaining of a bug in some software product that caused it to ask you
to reinsert the disk as soon as you ejected it; this is what the Set File
DA does, and thus wondered if the person had Set File installed.)  I wrote
to the authors to report the problem, and they replied "yes, we've seen it,
but can't reproduce it regularly," and have heard nothing since.  Was a
new version that has this fixed posted later, which just didn't get here?
-- 
Full-Name:  J. Eric Roskos
UUCP:       ..!{decvax,ucbvax,ihnp4}!vax135!petsd!peora!jer
US Mail:    MS 795; Perkin-Elmer SDC;
	    2486 Sand Lake Road, Orlando, FL 32809-7642