From: Jolly Roger on
In article <C576BCC7.2970E%nicknaym@[remove_this].gmail.com>,
Nick Naym <nicknaym@[remove_this].gmail.com> wrote:

> In article jollyroger-1D534B.14391723122008(a)news.individual.net, Jolly Roger
> at jollyroger(a)pobox.com wrote on 12/23/08 3:39 PM:
>
> > In article <C576A7BB.28F80%nicknaym@[remove_this].gmail.com>,
> > Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
> >
> >> Besides the security component, what else does the combo include that the
> >> standard doesn't? Is it only the additional code to handle "update
> >> skippers?"
> >
> > Not just code - mainly files - and lots of them. The combo updater is a
> > delivery mechanism for every single file that has changed in every
> > single update since the initial operating system release. Because it
> > replaces so many base files in the system, it has a much greater chance
> > of repairing damage resulting from files that have become misplaced,
> > corrupt, or whatever else. The closer you get to wiping the slate clean
> > with an OS update, the less potential problems there are. With
> > incremental updates, Apple has to make more assumptions about the state
> > of the system.
>
> 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?

Absolutely.

--
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: Nick Naym on
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.)





--
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 12:06:28 -0500, aRKay wrote
(in article
<arkayREMOVE-8A4F0E.11062723122008(a)news.houston.sbcglobal.net>):

> 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. Repeated
clicking on the arrow at the top will get me to a different date safely
and eventually.

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

From: Jim Gibson on
In article <C576D35F.29764%nicknaym@[remove_this].gmail.com>, Nick Naym
<nicknaym@[remove_this].gmail.com> wrote:

> 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.)

I had to do an Archive and Install after the 10.5.5 upgrade hosed my
computer. After the A&I that took me back to 10.5.1 and a lot of
software upgrades to get back to 10.5.5 my system was OK. The only
problem I encountered was that I lost a certificate for the Microsoft
Exchange server we use here at work. I could probably figure out how to
fix that by calling IT support, but in the meantime Entourage still
works; I just have to click on an OK button in a dialog asking me to
accept the site once a day.

I recommend doing a full backup, then doing an Archive and Install,
then spend some time testing your critical software to make sure it
works. If you find anything wrong, then you can restore from the full
backup.

However, in my limited experience, A & I will solve more problems than
it causes.

--
Jim Gibson
From: Jamie Kahn Genet on
Jim Gibson <jimsgibson(a)gmail.com> wrote:

> In article <C576D35F.29764%nicknaym@[remove_this].gmail.com>, Nick Naym
> <nicknaym@[remove_this].gmail.com> wrote:
>
> > 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.)
>
> I had to do an Archive and Install after the 10.5.5 upgrade hosed my
> computer. After the A&I that took me back to 10.5.1 and a lot of
> software upgrades to get back to 10.5.5 my system was OK. The only
> problem I encountered was that I lost a certificate for the Microsoft
> Exchange server we use here at work. I could probably figure out how to
> fix that by calling IT support, but in the meantime Entourage still
> works; I just have to click on an OK button in a dialog asking me to
> accept the site once a day.

If you expand that warning you'll see you've the chance to "always
accept", assuming it's the standard OSX certificate warning you're
seeing.
--
If you're not part of the solution, you're part of the precipitate.