Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Mac OS X 10.5.2 Inches Closer... Build 9C23 Seeded
- Thread starter MacRumors
- Start date
- Sort by reaction score
The Macbook Airs have a shipping time of 2-3 weeks, the Mac Pro with 8800 GT has a shipping time of 2-3 weeks. People who ordered one of them all have a shipment date of February 15th. Coincidence? I think not, but I don't think Apple is going to wait two weeks with the release of 10.5.2. Doesn't seem like they're in a hurry, though, besides new seeds being pretty frequent.
Thanks for the suggestion, but I don't have .mac and I've never opened iSync. Sometimes the dock shows in fullscreen QT, sometimes not.
I'm waiting until 10.5.3 arrives. Too many issues with Installer.app and more that randomly likes and dislikes RAM and other package integrity checking.
They have to get that fixed.
And my main interest is XCode 3 and ObjC2.0.
When the increased UEFI PCI Express card options are available, then I'll buy a new Mac Pro.
They have to get that fixed.
And my main interest is XCode 3 and ObjC2.0.
When the increased UEFI PCI Express card options are available, then I'll buy a new Mac Pro.
Me too- I have kernel panics every day at the moment, doing things I did without problem with Tiger-
Using USB Drives Watching TV Letting my mac sleep / wakeMe too- I have kernel panics every day at the moment, doing things I did without problem with Tiger-
Installed any third-party RAM in your machine?
First keystroke bug NOT fixed in 10.5.2
Just got news from an ADC tester of 10.5.2 at Apples discussion forum and it seems the 'first keystroke not always registered' bug on MacBook Pros has NOT been fixed in the recent update. However one claims that an Apple supporter has said the problem is supposed to be fixed in either 10.5.2 or 10.5.3 - guess that would be 10.5.3
I recommend that you take a look at my page about the issue:
http://www.petergabriel.dk/mbp.html
Just got news from an ADC tester of 10.5.2 at Apples discussion forum and it seems the 'first keystroke not always registered' bug on MacBook Pros has NOT been fixed in the recent update. However one claims that an Apple supporter has said the problem is supposed to be fixed in either 10.5.2 or 10.5.3 - guess that would be 10.5.3
I recommend that you take a look at my page about the issue:
http://www.petergabriel.dk/mbp.html
Glad to help. Can't remember where I saw that tip but it has saved me digging manually through folders looking for .plist files.
-Kevin
Nope - 2x 512mb ddr sdram, factory installed when built!
I just realised that my old soap-bar apple branded mouse is a logitech on the inside, have swapped in a mighty mouse (which I really don't like), to see if that makes a difference.
Fact remains that Tiger didn't crash for me using exactly the same configuration...
Even Apple sells defective RAM, perhaps as often as other vendors. Thus, you should run the Apple Hardware Test. I ran fine with Tiger, but with 10.5.1 and QuickTime 7.3.1 updates ran into horrible problems. I found that my third-party RAM was defective by running the Apple Hardware Test. Apparently, the updates placed demands upon the RAM that the prior system did not. However, I'm now running fine with new third-party RAM. Thus, it is not third-party RAM, in and of itself, that causes the problem, but simply defective RAM.
The screams about third-party RAM start with Apple which would like all of us to pay eight times as much as RAM costs elsewhere. I'm sure Apple RAM comes from some of the same factories that make third-party RAM.
you're wrong. millions! millions are enjoying it.
i don't dispute the issues some people are having, but i'm betting its more 3rd party stuff causing most of the issues more so than leopard itself.
when people post their complaints, it would be nice if they would list any adds they have running as well. like all the people with mail complaints (i have no issues), did you install a junk filter or some add on?
that would be the stuff that is useful instead of just complaining. then everyone could say, hey ya, I have junkmatcher installed too. maybe that's it!
I'm not saying thats the only reason, as there are real issues for lots of users, but the outright winning is just not helpful to anyone.
Gotta say I'm not all that impressed with 10.5 so far either.
10.5 was the bumpiest transition since 10,0/10.1.
Half my widgets are stuck with no way short of logout or restart to get them back.
Safari crashes several times a day, mostly when I hit the "back" button.
Sure hope this crap clears up with the update,
I'm used to Apple's stuff "just working", this sux.
I don't even put any comments in the "crash reports" anymore, I just hit "send".
Zack
10.5 was the bumpiest transition since 10,0/10.1.
Half my widgets are stuck with no way short of logout or restart to get them back.
Safari crashes several times a day, mostly when I hit the "back" button.
Sure hope this crap clears up with the update,
I'm used to Apple's stuff "just working", this sux.
I don't even put any comments in the "crash reports" anymore, I just hit "send".
Zack
Guess I should clarify -
I have all these problems on my old G5 DP2.0 that has been virtually flawless till now.
Haven't noticed any trouble at all on my MBP 2.33 CD2.
Z
I have all these problems on my old G5 DP2.0 that has been virtually flawless till now.
Haven't noticed any trouble at all on my MBP 2.33 CD2.
Z
Every complaint I posted about upthread Apple is directly responsible for, either through neglect or willful action.
you're wrong. millions! millions are enjoying it.
i don't dispute the issues some people are having, but i'm betting its more 3rd party stuff causing most of the issues more so than leopard itself.
If that's the case, why is Apple releasing an update?
Exaggerating does not help your point. Anyone that used 10.0 knows it was almost unusable and very little software was available with it. More for looking at what was coming down the pike.
Me too- I have kernel panics every day at the moment, doing things I did without problem with Tiger-
Do you get those with a complete and pristine full fresh install (like out of the box with noting moved in or migrated?
Was wondering if something you have installed maybe interacting.
Also what about any hardware that you added to the system since you initially purchased it?
Remember that most Intel based system now days are 64 bit based and Apple has been adding more 64 bit code, so hardware, specially memory maybe being addressed differently and it may have worked before but that was because it was being addressed differently.
I would start with a fresh base system, like it came from the factory, and wipe everything including the disk and do a full install of Leopard, connect to the network and upgrade to 10.5.1. Without moving anything in, exercise the system and see if it still crash. If no crash then start installing any hardware differences and exercise and see what happens. Continue making one single change at a time and keep checking you stability until it start acting up, I think you will discover the issue.
lets say that this does come out today. For me that will be the middle of the night. Is there any way i could get this to download automatically for me. I thought about applescripting it or automata. But there is no way to get it to download it automatically, software update could run but it wouldnt start the download. And i dont know exactly what URL apple is going to use as the 10.5.2 download. They have a unique identifier in there download urls. It appears to be sequential but they could put out a number of updates. This isn't a full proof method. Any one have an ideas ?
Or will they ? i noticed that it says important updates will be downloaded automatically, however 10.5.1 was not downloaded for me i had to manually say download. Unless i am mistaken ?
Or will they ? i noticed that it says important updates will be downloaded automatically, however 10.5.1 was not downloaded for me i had to manually say download. Unless i am mistaken ?
Wirelessly posted (iPhone: Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420.1 (KHTML, like Gecko) Version/3.0 Mobile/4A93 Safari/419.3)
'it just works'
EagerDragon said:Me too- I have kernel panics every day at the moment, doing things I did without problem with Tiger-
Do you get those with a complete and pristine full fresh install (like out of the box with noting moved in or migrated?
Was wondering if something you have installed maybe interacting.
Also what about any hardware that you added to the system since you initially purchased it?
Remember that most Intel based system now days are 64 bit based and Apple has been adding more 64 bit code, so hardware, specially memory maybe being addressed differently and it may have worked before but that was because it was being addressed differently.
I would start with a fresh base system, like it came from the factory, and wipe everything including the disk and do a full install of Leopard, connect to the network and upgrade to 10.5.1. Without moving anything in, exercise the system and see if it still crash. If no crash then start installing any hardware differences and exercise and see what happens. Continue making one single change at a time and keep checking you stability until it start acting up, I think you will discover the issue.
'it just works'
Nope. No numbers prepared.
<guessing>A decade seems to feel like the time when discs will hit VHS status. Sure, like VHS (which is still available today) disc will exist for well more than a decade - but I could see about 10 years beginning a disc-less mainstream.</guessing>
Reminds me of a silly conversation I had with a friend. I said that one day, there would be no TV. He laughed and said that TV would be around forever. Well, it eventually got to the "one day we'll be floating, gaseous blobs and TV will not exist" part of the conversation... which is kind of all I was suggesting with discs. One day, gone. And with each passing day, they are closer to gone.
Sorry, not to be taken so literally.
Just fun conjecture. No stats.
Move along.
