Recommended Posts

I call fake on that. There has been numerous claims that 10a435 was the final build as well. Nothing but fakes

The Version that Ships with the MacMini will be a specific build for the Mini. I guess there will be a different build number for each model.

Look here http://support.apple.com/kb/HT1159 There are loads of different build numvers for the same os version.

The Version that Ships with the MacMini will be a specific build for the Mini. I guess there will be a different build number for each model.

Look here http://support.apple.com/kb/HT1159 There are loads of different build numvers for the same os version.

You are correct there, and I have heard that 10a435 is actually going to be 10.6.1

You are correct there, and I have heard that 10a435 is actually going to be 10.6.1

That, IMO, would be VERY surprising.

They're not at 10.6.1 yet, they might have just started shipping 10.6 and they have no idea how many builds it will take until it becomes a 10.6.1

I have ran Windows 7 64 bit under BootCamp from the first build made available to developers after WWDC and never had a problem with it. The 3.0 drivers work very well.

That's good to know.

Must be something I did wrong on my end. Thanks. ;)

Help I have Snow Leopard 104A32 and when I go to logmein.com and login to one of my computers and I get a error

https://secure.logmein.com

Unknown error while loading browser plugin, please restart your browser! choice ok so I did and no luck same error I rebooted mac pro and same thing. Also ran software update and had new version of safari installed it and same error also it happens on safari, firefox also it work on windows parallells on Internet Explorer and not Safari for windows on the mac it worked on Leopard flawless.

Please Advise

Thanks Jeff

Error1.tiff

That, IMO, would be VERY surprising.

They're not at 10.6.1 yet, they might have just started shipping 10.6 and they have no idea how many builds it will take until it becomes a 10.6.1

Yeah. I'd be very surprised if they managed to get to a minor release in so few builds.

That, IMO, would be VERY surprising.

They're not at 10.6.1 yet, they might have just started shipping 10.6 and they have no idea how many builds it will take until it becomes a 10.6.1

Why? As it happened before. From what I recall there were rumors about the Leopard GM not being the GM and that a newer build leaked. As it turned out the newer build was actually the first beta of the v10.5.1 update.

same, and i remember my MBP had the big 64Bit thing plasterd all over it, but still have the 32bit memory limitation and 32 bit EFI. got it from Apple direct. because of that and refusing to fix my iPod touch w/applecare that dies in 30 min. refusing to buy another apple branded thing again.

feels like Obi-Wan and Yoda concerning Truth from certain points of view

i am still kinda peeved at the fact my macbook won't run the OS in 64 bit mode even though i have 64 bit CPU...
Yea, that's what I was thinking. And I did check: Finder does have the option just like all the other 64-bit apps in Snow Leopard. We'll just have to see if it helps .Neo any.

Can't get the Finder to start in 32-bit mode even when ticking the checkbox. According to Activity Monitor the Finder still runs in 64-bit mode. :/

Help I have Snow Leopard 104A32 and when I go to logmein.com and login to one of my computers and I get a error

https://secure.logmein.com

Unknown error while loading browser plugin, please restart your browser! choice ok so I did and no luck same error I rebooted mac pro and same thing. Also ran software update and had new version of safari installed it and same error also it happens on safari, firefox also it work on windows parallells on Internet Explorer and not Safari for windows on the mac it worked on Leopard flawless.

Please Advise

Thanks Jeff

Could it be incompatible with 64bit Safari/FF? You should be able to change the preferences from what I understand (Haven't touched Snow Leopard yet), to start Safari in 32bit mode.

Also, can try to see if this is the case and boot into 32-bit mode to see if it works using the tool found here. It says for 10.5/10.6 but surely 10.6 at this point. :)

Can't get the Finder to start in 32-bit mode even when ticking the checkbox. According to Activity Monitor the Finder still runs in 64-bit mode. :/

Even if you kill it and restart it?

Even if you reboot?

Why? As it happened before. From what I recall there were rumors about the Leopard GM not being the GM and that a newer build leaked. As it turned out the newer build was actually the first beta of the v10.5.1 update.

Yeah, maybe it can be a beta of 10.6.1, but it cannot be 10.6.1, it would be just 3 builds away from the official release and it'd be released like ... before the official product ships. I would accept that a security fix is out before the product is out, but a 10.6.x version, never.

Spanish site Applesfera reports [Google translation] that a Tumblr/Twitter user by the name of pedro10 has received a retail copy of Mac OS X Snow Leopard in advance of Friday's official launch.

After installing Snow Leopard, pedro10 reports that the retail disc does in fact contain Build 10A432, which had been rumored to be the "Golden Master" version sent to manufacturing for retail distribution. Some unconfirmed reports in recent days had suggested that a different build might have been the shipping version of Snow Leopard, but this appears to not be the case.

Source:http://www.macrumors.com/2009/08/25/os-x-snow-leopard-retail-disc-contains-build-10a432/

that doesn't mean that there couldn't be an update waiting for release day and they just used 10a432 for GM as to make sure they didn't miss the release date

Incase anyone would like some help with 64bit or 32bit modes here is a neat free little app i found

http://www.ahatfullofsky.comuv.com/English...ms/SMS/SMS.html Startup Mode Selector "SMS"

Edited by Phantom Helix
that doesn't mean that there couldn't be an update waiting for release day and they just used 10a432 for GM as to make sure they didn't miss the release date

There will be some updates, but I don't think a "build update" would be one of them. Any time the OS gets a build update, it always comes with a 10.6.1 or whatever update, which probably shouldn't happen on the first day.

If I remember correctly, Leopard was updated to 10.5.1 within a few weeks of release. Any bugs discovered over the past month while 432 has been floating around, will most likely be addressed in a 10.6.1 upgrade before Thanksgiving.

Also, I suspect Apple made a decision to not enable the 64bit kernel for a reason and will make that change in a 10.6.x release in the near future. While many will argue back and forth about releasing this early (just look at the past 80 pages), they did it for a reason. :p

If I remember correctly, Leopard was updated to 10.5.1 within a few weeks of release. Any bugs discovered over the past month while 432 has been floating around, will most likely be addressed in a 10.6.1 upgrade before Thanksgiving.

Also, I suspect Apple made a decision to not enable the 64bit kernel for a reason and will make that change in a 10.6.x release in the near future. While many will argue back and forth about releasing this early (just look at the past 80 pages), they did it for a reason. :p

http://en.wikipedia.org/wiki/Mac_OS_X_v10.5#Version_history

  • 10.5.0 9A581 26 October 2007
  • 10.5.1 9B18 15 November 2007

So about 3 weeks, hopefully its quicker than that :p

Also, I suspect Apple made a decision to not enable the 64bit kernel for a reason and will make that change in a 10.6.x release in the near future. While many will argue back and forth about releasing this early (just look at the past 80 pages), they did it for a reason. :p

The 64-bit kernel isn't buggy. If it was, it wouldn't be default on Xserves. That'd be a very bad idea.

No, the reason is that the 64-bit kernel can't load 32-bit kernel extensions, which a few third party vendors use (mouse drivers, webcams, etc). They'll wait quite a while before flipping the switch (if they ever do).

The 64-bit kernel isn't buggy. If it was, it wouldn't be default on Xserves. That'd be a very bad idea.

No, the reason is that the 64-bit kernel can't load 32-bit kernel extensions, which a few third party vendors use (mouse drivers, webcams, etc). They'll wait quite a while before flipping the switch (if they ever do).

Right, all I was getting at was, Apple did it for a reason, not as an oversight. They will switch all the kernels to 64 when they feel it will be beneficial to the avg. user.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.