Path: utzoo!attcan!uunet!husc6!bloom-beacon!mit-eddie!uw-beaver!fluke!ssc-vax!ted
From: ted@ssc-vax.UUCP (Ted Jardine)
Newsgroups: comp.sys.mac
Subject: Re: S.U.M. glitches
Summary: Don't change SUM utility version numbers OR their names
Message-ID: <2178@ssc-vax.UUCP>
Date: 23 Aug 88 18:10:46 GMT
References: <20369@cornell.UUCP> <8143@coherent.com> <9875@dartvax.Dartmouth.EDU>
Distribution: comp
Organization: Boeing Aerospace Corp., Seattle WA
Lines: 43

In article <9875@dartvax.Dartmouth.EDU>, isle@eleazar.dartmouth.edu
(Ken Hancock) writes:
> In article <8143@coherent.com> dplatt@coherent.com (Dave Platt) writes:
> ...
> >From the creation and modification dates, I assume that these are in fact
> >newer versions than the ones shipped in the S.U.M. package.  However, it
> >doesn't make me feel all that good to see that Symantec didn't bother to
> >update the Version information (from the signature resource in the INIT
> >file) to reflect the actual status of the software. ...
> 
> DON'T CHANGE THEM!  There's a good (bad?) reason why they didn't change
> them.  I went in and changed them to 1.01.  Guess what happened?
> Shield options no longer recognized it as a Shield file.  I don't
> know HOW shield options checks for a valid Shield INIT, but it sure
> doesn't seem like the right way! ...
> 
> Ken Hancock  '90                   | BITNET/UUCP/
> Personal Computing Ctr Consultant  |   INTERNET:  isle@eleazar.dartmouth.edu

Hmmm!  Have had Symantec's utility package on my Mac II for a few weeks now.
Everything was going just fine.  Then I read someone's article about being
able to determine the order in which INITs were loaded at boot time by
changing their names.  So, I figured out what order I wanted and prefixed the
name of each INIT in my system file with 'Amm ' (where mm is a two digit
number).  Fortunately I have been playing with computers since the days of
the IBM 704, and I don't trust any of them, so I did a restart.

And what to my wondering eyes did appear, but at the time that Shield was
about to display its icon, I get a Bomb message instead!  At first I
thought that the desktop needed rebuilding (per Disk Clinic diagnostic
suggestions).  Got things to work only after suppressing all INITs.  File
system was intact, so I reversed my most recent change (INITs back to
original names) and now things are fine.  Whew!

Hope this sad tale of woe helps someone else avoid the same trap.  No
flames to Symantec (as long as they get me my copy of MacSQZ that works
with MultiFinder and the Mac II).

-- 
TJ {With Amazing Grace} The Piper
aka Ted Jardine  CFI-ASME/I
Usenet:		...uw-beaver!ssc-vax!ted
Internet:	ted@boeing.com