Linked by Thom Holwerda on Tue 18th Aug 2009 18:46 UTC
Mac OS X Even though Apple has been hyping up the 64bit nature of its ucpoming Snow Leopard operating system, stating it will be the first Mac OS X release to be 64bit top-to-bottom, reality turns out to be a little bit different so far. With the current Snow Leopard seed, only Xserve users get the 64bit kernel and drivers - all other Macs default to 32bit. By holding down the '6' and '4' keys during boot, you can to boot into full 64bit mode - that is, if your Mac supports it. As it turns out, some Macs with 64bit processors cannot use the 64bit kernel because the EFI is 32bit. Note: I should have included in the article that 64bit applications will run just fine (including benefits) on a 32bit kernel in Mac OS X. Since this was already possible in Leopard, I assumed people were well aware of that. Turns out some were not, so my apologies for that.
Thread beginning with comment 379605
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Idiotic article
by Hakime on Thu 20th Aug 2009 09:44 UTC in reply to "RE[6]: Idiotic article"
Member since:

Then will you please leave OSNews or something? How am I supposed to have a discussion with someone who does not believe me when I specifically apologise for not including information which I believed everybody knew?

Leave OSNews? You should better do it, not me. Which apologize, i can still read on the article

So, even if you have a 64bit processor, and you thought you were in the clear, Apple might not give you the option to go 64bit.


That table above might be a bit cryptic, but it's technically pretty simple. Only Macintosh machines with a 64bit EFI are able to boot the 64bit Snow Leopard kernel and kexts; this is an artificially implemented limitation by Apple, as 32bit EFI can boot a 64bit kernel just fine. On top of that, even if your MacBook has a 64bit EFI, you will only be able to boot the 32bit version of Snow Leopard - again because of an artificial limitation by Apple for MacBooks. Probably the harshest consequence of this is that the original Mac Pro, discontinued January 8, 2008, cannot boot the 64bit kernel and drivers.

Are you still arguing that those statement are not intentionally misleading? If really i should believe you, if you really knew what you claim you do, why did not you correct the article or add the relevant information when it was clear that most of the people reacting on the forum got it wrong? Answer to this one please.

What about those statements:

However, in what probably rivals the Amazon Kindle 1984 thing in most ironic moment of 2009, the hackintosh community has come to the rescue. With netkas' pcefiv10.1 bootloader, you can boot into 64bi Snow Leopard even on 32bit EFI Macs.

ar, it's not yet known if Apple will enable owners of machines with 32bit EFI to boot into a 64bit kernel in Snow Leopard-final; Apple might offer an EFI update, or remove the artificial limitation.

This clearly sates that users will have to live with some sort of limitation because the 64 bits kernel is not loaded. Are you still arguing that it is the case? What are the artificial limitation that you are referring to? Why do you speak then about limitations?

What about this

The same applies to MacBooks; it might be that Apple is planning on using 64bit as a selling point to drive people to buy MacBook Pros instead of ordinary MacBooks.

What it is supposed to mean? You are clearly inferring that laptop users, particularly the macbook users will see any sort of drawback of not having a 64 bits kernel. Am i inventing the quotes above?

It is amazing to see that you can't even acknowledge what you wrote by yourself. I mean come on.... this is getting ridiculous.

If you think I left that out with malicious intent, then you are even more of an apple zealot than I already thought.

Sure anyone who criticizes you is an apple zealot. The point is that you know i am right and you can't accept that someone here puts some truth in the mass of nonsense that you write. You did not have malicious intent? Prove that i am wrong, correct the article.

I was pointing on the fact that Apple was heavily avertising it as a major feature, while in fact it was mostly unused.

Wait, unused? By who? The PowerMac G5 was advertised as high end machine that can run 64 bits applications. It did so and back then running 64 bits apps on Powerpc was more about getting more addressable memory. You would not get the speed up by the additional registers as in x86_64. The PowerPC was a 64 bit design from day-one, they did not need to add more registers to support the 64 bits addressing and the additional instructions. That means few people really could see the advantage of the added addressing space. Merely only scientific apps that needed to address more more than 4 GB of memory. The PowerMac G5 with Tiger did just that, you could run any unix app in 64 bits, a ton of scientists did do, i did and still do, so don't say that it was unused. Some other major apps got 64 bits support, it was the case for example of Mathematica which used the IPC approach for binding the 64 bits Mathematica kernel to the UI.

There were people who believed that everything they were doing was in 64 bit.

Who? What can make you think that it is the case? Do you have numbers, statistics, references? How could any person think that he/she was running a 64 bits app because he/she had to use then an app which needed more than 4 GB of addressable physical memory. Back then (and still now) who are those people, besides people in high end computing who anyway knew what the Tiger 64 bits implementation was?

Now, when you actually have the possibility to go full 64 bit, Apple itself is phasing out support for these wonderful (and pricey) machines.

Here we are, typical example of the misunderstanding that the article has produced. Yes i say you again, you don't know what are you talking about. For any PowerMac G5 user, 64 bits means the 64 bits addressing for all the OS stack and the extra security features. Did you read previous posts, god sake?

We still have PowerMac G5 running Leopard in my lab loaded with 16 GB of RAM, running 64 bits custom Cocoa applications and some X11 apps, like Tecplot. Right now a tecplot run is addressing 10 GB of RAM. How a hell is Apple is phasing out support for full 64 bits with those machines then? Full 64 bits (all OS stack 64 bits) is available since Leopard.

Could people here document themselves before throwing out non-sense?

Edited 2009-08-20 09:54 UTC

Reply Parent Score: 2

RE[8]: Idiotic article
by Thom_Holwerda on Thu 20th Aug 2009 09:53 in reply to "RE[7]: Idiotic article"
Thom_Holwerda Member since:

You are assuming malicious intent on my end on all those statements. Those statements, however, are all still 100% correct, and nowhere am I insinuating anything about it being a drawback to users. You are seeing insinuations that aren't there.

The ONLY thing I left out, which I should have added, is that 64bit apps will run on a 32bit kernel. I'm starting to repeat myself, but oh well.

Hakime, let's just get it out in the open here: you think my sole purpose int his world is to put Apple in a negative light, and because of that, you will twist everything I say and do in such a way as to support your view on the world. Of couse, I've written a whole boatload of positive Apple articles, but you conveniently ignore those because they don't fit in with your view on the world.

I'm getting tired of this pointless discussion. The article is 100% correct on all the facts, but as I have already apologised for, I should have added specifically that 64bit apps will still run fine on a 32bit kernel. I assumed everybody would know that, but I was wrong. I am deeply sorry if I offended you.

Reply Parent Score: 1