ComboUpdate (10.6.3 -> 10.6.7) fails immediately

[Kpt_Superskoot]

Hi all.

I used to run 10.6.7 on this rig, and then a drive corrupted.
So I wanted to install it all again, exactly as the first time:
1) iBoot
2) 10.6.3 retail DVD
3) open MultiBeast
4) 10.6.7 ComboUpdate
5) run MultiBeast
6) be happy

Machine spec:
Mobo - Intel DG41RQ Raisin City
CPU - Intel Q6600 (2,4GHz quad core)
Display - nVidia 9800GTX
RAM - 2GB DDR2-800 Hynix

This time, same hardware, same software, no go.
The moment I start any ComboUpdate (I have a choice of 10.6.6, 10.6.7 and 10.6.8), the update stops immediately and says there was some sort of problem (doesn't specify).
MultiBeast works after that, but I can never update to anywhere above 10.6.3.
I really like 10.6.7 (most stable to my mind), and would love to get there again.

Any sugg?

Greets
Kpt_SuperSkoot (Hackintosh semi-n00b)

 

[iUserosx]

Seems the certificate of ur combo updates has been expired.....just check(click on the small square on upper right corner of the installer window) and re download them if required..

I've faced the same problem which solved by re download

 

[Kpt_Superskoot]

Thank you, kind sir.
I shall try that directly, and see if it is indeed an expiration issue.
That would blow; we don't have cheap high-speed home lines in my fold of the world.
It'll have to trickle in over the weekend...
But thanks, I'll check it out.

 

[potemkin]

It's been a year since I 've used Snow Leopard.
The last few updates would hang during install or fail.
I had two partitions on disk both bootable.
Say part a and part b.
To make update work and save a download try this.
Boot part a and have downloaded update on it.
Launch update and install it on Part b.
Test it thoroughly.
When you feel safe simply do the process again.
Copy update to part B
Boot part B
Run update with Part A as target.

Not familiar with date issue.
When you run update do not skip verify download step.
Maybe your disk corruption affected the process.

 

[Kpt_Superskoot]

Yep, the expiry dates were 23 March 2012.
What BS is that, letting an update expire?
I don't want to necessarily go to Lion or beyond on a FakeMac, I just want what I like, which happens to be 10.6.7.
Now every time some little thing goes wrong I have to re-download a Gig of data.
Even M$ doesn't let their updates expire, you can keep them on disk or DVD for ever.
But hey, I got the update (again!), and it worked.
So thanks for the suggestion on the expiry date.
Like a frikkin' milk carton, I tell ya, Best Before March 2012.

 

[iUserosx]

In that case set ur system clock to a date before the expiry......... and try update

 

[l1nkdna]

In that case set ur system clock to a date before the expiry......... and try update

i keep forgetting this

 

[totenkopf4]

i keep forgetting this

This is kinda a normal prople now w OSX 10.6 updates - that their experiation dates are past due on the downloads and in general they dont stay to current when Apple updates them - I think they want you to say - Gee better get a new Mac.


FYI
You also should know that its been over 4 years since OSX10.6 was released - June 8 2009 - the last update for it was 10.6.8 v1.1 (July 25, 2011; 14 months ago)