You're right - that Apple's not supporting 64-bit kernels on all 64-bit capable Macs seems like an odd decision. Then again, remember when Boot Camp appeared, and not all Macs were ready to support it out of the box? Apple fixed that with a firmware update. If Apple intends to correct this oversight, they'll do it with a firmware update, not an OS update... that's my line of thought on this matter.
That seems especially tricky to me though.
If they let people install the 32-bit Kernel and then apps install their 32-bit KEXTs (quite logically) the user will be put in a situation where their apps/hardware expect a 32-bit system.
For a firmware update to come along and change that would obviously cause issues.
That's why I think doing it with a new OS is the best way forward.
No, while this is true in the generic case, x86-64 (the Intel 64-bit architecture) adds additional registers so some 64-bit apps will see a decent speedup.No point in running 64bit if you have less than 4Gb of RAM, 32bit runs just as fine.
Not a al lot of 3rd party apps in 64bit for now so it doesnt matter, but they are comming because of SL.![]()
No point in running 64bit if you have less than 4Gb of RAM, 32bit runs just as fine.
Not a al lot of 3rd party apps in 64bit for now so it doesnt matter, but they are comming because of SL.![]()
Hopefully handbrake comes out in 64bit soon
Following your logic it would not be possible to boot into 64-bit by holding down the '6' and the '4' keys - since it is possible then no hardware update is needed, it's all in software (and there is a software edit that can be done to permanently allow a 64-bit boot)
According to the Handbreak developer, there is no real benefit from a 64bit version of Handbreak, which is a shame.
Link: http://forum.handbrake.fr/viewtopic.php?f=22&t=10916&p=57114&hilit=64bit
not just consumer products. mac pro.
While the only Mac computer to automatically boot into 64-bit kernel mode is the Xserve, most of the other computers are able to boot into it with the key combination on boot (or edited preference file). That includes the Mac Pro, recent iMacs and MacBook Pros.
Some computers have been deliberately restricted (such as the Mac Mini and MacBook, as well as earlier iMac models) so that they can't/wont boot into the 64-bit kernel mode.
Most put this down to Apple not putting in the effort to make it work properly on these computers.
Other operating systems don't use similar methods to restrict 64-bit which is ironic given that Apple has total control over their hardware.
This is exactly why 10A432 is NOT the GM. Apple would never put out an O/S where a person had to hold down certain keys to boot into 64-bit mode.
Most people are going with the assumption that Apple simply isn't going to enable the 64-bit Kernel on every computer.
If you look carefully at the things Apple has stated, they haven't actually mentioned the Kernel being 64-bit.
If you've read all the white papers for developers you would know that the kernel is 64-bit. I've read all of them and I know.
my 2 cents worthI don't think you know what you're on about!
Snow Leopard features 2 Kernels:
A 32-bit and 64-bit kernel.
Some early Intel Macs (those with Core Solo and Duo processors) don't support 64-bit (and not due to an artificial limitation either, their design simply can't support it), so Apple MUST include a 32-bit kernel with Snow Leopard.
Newer Macs (Core 2 Duo, Xeon etc.) have processors that support 64-bit software. As such, they can run the 64-bit kernel, but so far Apple hasn't made it work by default on anything other than the Xserve.
The most logical assumption so far has been that Apple doesn't intend for most users to have the 64-bit kernel enabled, due to the potential compatibility issues vs. limited benefits.
The most logical assumption so far has been that Apple doesn't intend for most users to have the 64-bit kernel enabled, due to the potential compatibility issues vs. limited benefits.
I don't think 10A432 is the GM. It still has glitches, stuff not even 10.5.0 had.
That seems especially tricky to me though.
If they let people install the 32-bit Kernel and then apps install their 32-bit KEXTs (quite logically) the user will be put in a situation where their apps/hardware expect a 32-bit system.
For a firmware update to come along and change that would obviously cause issues.
That's why I think doing it with a new OS is the best way forward.
Could it be judged by the Welcome Video?
It is still the same as Leopard in 10A432.
This is exactly why 10A432 is NOT the GM. Apple would never put out an O/S where a person had to hold down certain keys to boot into 64-bit mode.
an update can eventually change this. for now it makes no sense to boot into 64 bit and cause problems for users. maybe a year from now when more 64bit apps are available it would make sense
If 10A432 isn't the GM, then wouldn't the developers by now have a newer version for testing that would roll into the GM?
Since nothing is in the pipe and every day is 1 day closer to the release of SN, I still think 10A432 is the GM.
Of course I could be dead wrong, because I know nothing about Apple's testing procedures leading up to GM releases.