From: Jolly Roger on
In article <C578079B.2988C%nicknaym@[remove_this].gmail.com>,
Nick Naym <nicknaym@[remove_this].gmail.com> wrote:

> In article jollyroger-02F027.12293224122008(a)news.individual.net, Jolly Roger
> at jollyroger(a)pobox.com wrote on 12/24/08 1:29 PM:
>
> > In article <jollyroger-897027.12193724122008(a)news.individual.net>,
> > Jolly Roger <jollyroger(a)pobox.com> wrote:
> >
> >> In article <C577773A.2980E%nicknaym@[remove_this].gmail.com>,
> >> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
> >>
> >>> In article jollyroger-9D6C08.04030624122008(a)news.individual.net, Jolly
> >>> Roger
> >>> at jollyroger(a)pobox.com wrote on 12/24/08 5:03 AM:
> >>>
> >>>> In article <C57769AA.29800%nicknaym@[remove_this].gmail.com>,
> >>>> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
> >>>
> >>> ...
> >>> ...
> >>>
> >>>> I'm reading reports of how the update has gone wrong for various people,
> >>>> and waiting until i feel relatively sure I won't experience the major
> >>>> issues, and I know how to recover should I experience any problems.
> >>>>
> >>>>> Are you suggesting that
> >>>>> Apple likely will be re-issuing the Standard and Combo updates, modified
> >>>>> to
> >>>>> address the problems folks seem to be having?
> >>>>
> >>>> Apple has done this in the past, so waiting also gives Apple time to do
> >>>> this if needed.
> >>>
> >>> Well then, I may very well wait until either Apple does something, or you
> >>> finish (and, hopefully, post) your assessment, whichever comes first.
> >>
> >> Well if it's any help, I let SuperDuper back up my entire startup volume
> >> on my Mac Pro last night, and then first thing this morning applied the
> >> combo update. Everything seems to have gone without a hitch so far.
> >>
> >> I'll evaluate the machine during the next day or two to make sure
> >> everything is in working order, and will make a decision about whether I
> >> want to roll out the update to the other machines I manage.
> >
> > I should note also that I did run Disk Utility's "Verify Disk" and
> > "Verify Permissions" commands before I made the SuperDuper backup. I
> > haven't run either of those commands in months and months. Neither
> > needed repair.
>
> I've been automatically backing up to separate externals for many months:
> SD! (once a day) on one, TM (9 times a day) on the other.

Ok... ?

--
Send responses to the relevant news group rather than email to me.
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.

JR
From: John McWilliams on
Jolly Roger wrote:
> In article <giu6mh$cmg$2(a)reader.motzarella.org>,
> John McWilliams <jpmcw(a)comcast.net> wrote:
>
>> Jolly Roger wrote:
>>
>>> Well if it's any help, I let SuperDuper back up my entire startup volume
>>> on my Mac Pro last night, and then first thing this morning applied the
>>> combo update. Everything seems to have gone without a hitch so far.
>> If one has SuperDuper-ed a drive, installed on a clean drive, is it
>> preferable to update the OS first, or is it all right to run Migration
>> Assistant first?
>
> Personally, I'd get the system up-to-date completely *before* attempting
> to migrate my data.
>
> By "installed on a clean drive", do you mean you erased the drive and
> installed from scratch on a blank volume?

Yes, that's what I meant.
> Since you have a backup, why
> wouldn't you simply install the 10.5.6 combo update over what you had?

What I had? You mean the backup? It was already updated, and with the
combo updater.
>
>> Is it easy to avoid creating a new user if taking the first option above?
>
> I'm not sure I understand the question - or more to the point, I'm not
> sure i understand exactly what you had before you started, and what you
> did / how it has changed.

Wiped the internal drive. Installed with installer disks that came with
the iMac (10.2). Then I updated software after testing that eject worked
fine, as it did just following the update.

Then ran Migration Assistant, but in so doing I ended up with two users.
The new user can eject; the migrated user, the one I want, cannot eject
normally.

One question I had was whether Migration Assistant makes it possible to
not create a new user, but just come in with what you had before on the
SuperDuper! back up.

--
john mcwilliams
From: J.J. O'Shea on
On Tue, 23 Dec 2008 17:41:51 -0500, Nick Naym wrote
(in article <C576D35F.29764%nicknaym@[remove_this].gmail.com>):

> In article michelle-A0AA74.14214323122008(a)mara100-84.onlink.net, Michelle
> Steiner at michelle(a)michelle.org wrote on 12/23/08 4:21 PM:
>
>> In article <C576BCC7.2970E%nicknaym@[remove_this].gmail.com>,
>> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
>>
>>> Does that suggest that I might try using the current Combo update,
>>> before embarking on an Archive and Install, as a potential means of
>>> addressing any corruption my system may have that could be causing
>>> the various problems I've been experiencing these past few months?
>>
>> It wouldn't hurt, but it shouldn't be necessary. Archive and Install
>> installs a brand new copy of the OS. But after you Archive and Install,
>> then run the combo updater.
>
> I am really very nervous about attempting an Archive and Install...I am
> under the impression that it could leave me with a lot of problems if not
> done just "right." (I recall seeing, for example, some complaints regarding
> external TM backup drives not recognizing the internal drive after an A&I;
> and other problems linked to third-party apps that were installed after the
> user first updated to/installed Leopard.)
>

Archive & Installs typically don't cause problems, except with Adobe products
and even then only rarely. (Adobe does Very Strange Things(tm) with their
registration schemes) The Adobe problems can be fixed, so long as you have
the original serial number available, by a simple call to Adobe support. This
is an annoyance, but hardly fatal.

I've never had a Time Machine problem after an Archive & Install.


--
email to oshea dot j dot j at gmail dot com.

From: Nick Naym on
In article jollyroger-FFB2CC.15500224122008(a)news.individual.net, Jolly Roger
at jollyroger(a)pobox.com wrote on 12/24/08 4:50 PM:

> In article <C578079B.2988C%nicknaym@[remove_this].gmail.com>,
> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
>
>> In article jollyroger-02F027.12293224122008(a)news.individual.net, Jolly Roger
>> at jollyroger(a)pobox.com wrote on 12/24/08 1:29 PM:
>>
>>> In article <jollyroger-897027.12193724122008(a)news.individual.net>,
>>> Jolly Roger <jollyroger(a)pobox.com> wrote:
>>>
>>>> In article <C577773A.2980E%nicknaym@[remove_this].gmail.com>,
>>>> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
>>>>
>>>>> In article jollyroger-9D6C08.04030624122008(a)news.individual.net, Jolly
>>>>> Roger
>>>>> at jollyroger(a)pobox.com wrote on 12/24/08 5:03 AM:
>>>>>
>>>>>> In article <C57769AA.29800%nicknaym@[remove_this].gmail.com>,
>>>>>> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
>>>>>
>>>>> ...
>>>>> ...
>>>>>
>>>>>> I'm reading reports of how the update has gone wrong for various people,
>>>>>> and waiting until i feel relatively sure I won't experience the major
>>>>>> issues, and I know how to recover should I experience any problems.
>>>>>>
>>>>>>> Are you suggesting that
>>>>>>> Apple likely will be re-issuing the Standard and Combo updates, modified
>>>>>>> to
>>>>>>> address the problems folks seem to be having?
>>>>>>
>>>>>> Apple has done this in the past, so waiting also gives Apple time to do
>>>>>> this if needed.
>>>>>
>>>>> Well then, I may very well wait until either Apple does something, or you
>>>>> finish (and, hopefully, post) your assessment, whichever comes first.
>>>>
>>>> Well if it's any help, I let SuperDuper back up my entire startup volume
>>>> on my Mac Pro last night, and then first thing this morning applied the
>>>> combo update. Everything seems to have gone without a hitch so far.
>>>>
>>>> I'll evaluate the machine during the next day or two to make sure
>>>> everything is in working order, and will make a decision about whether I
>>>> want to roll out the update to the other machines I manage.
>>>
>>> I should note also that I did run Disk Utility's "Verify Disk" and
>>> "Verify Permissions" commands before I made the SuperDuper backup. I
>>> haven't run either of those commands in months and months. Neither
>>> needed repair.
>>
>> I've been automatically backing up to separate externals for many months:
>> SD! (once a day) on one, TM (9 times a day) on the other.
>
> Ok... ?

I interpreted your "I let SuperDuper back up my entire startup volume on my
Mac Pro last night, and then first thing this morning applied the combo
update" to mean you took a safety precaution prior to updating the OS. Since
I am always within 24 hours of a cloned backup, and several hours from an
archival backup, I have a reasonably continuous "safety net," so I will be
"covered" whenever I get the balls to attempt the update.


--
iMac (24", 2.8 GHz Intel Core 2 Duo, 2GB RAM, 320 GB HDD) � OS X (10.5.4)

From: John Varela on
On Tue, 23 Dec 2008 20:10:52 -0500, Michelle Steiner wrote
(in article <michelle-233CBC.18105223122008(a)mara100-84.onlink.net>):

> In article <0001HW.C576E407001FFAB2B01AD9AF(a)news.verizon.net>,
> John Varela <OLDlamps(a)verizon.net> wrote:
>
>>> I used the Software Update to get 10.5.6 and everything worked.
>>
>> Same here, so far, except that iCal hangs when I try to goto a
>> different date by using shift-cmd-T and entering the date.
>
> Works for me.

I suspect that the problem has to do with syncing calendars with my
wife's iMac via MobileMe. Since 10.5.5 the calendar sync has been
pegging CPU utilization for several minutes every time it runs, and
changing dates takes a long time unless I uncheck the Subscriptions
box. Now with 10.5.6 iCal just hangs --- perhaps if I waited long
enough it would clear itself but I lack the patience.

--
John Varela
Trade NEW lamps for OLD for email.