Jump to content

Leopard on my Macbook pro


Titan999
 Share

25 posts in this topic

Recommended Posts

I understand Leopard is 64-Bit after watching the WWDC 07 Keynote. I bought my Macbook pro LESS THAN A YEAR AGO!!! (Yup, its Core Duo), and it wont work on Leopard, is that correct? Leopard is only 64 bit? What about us!!! The transition to Core 2 Duo was very recent! (I remember it just to the end of last year)

Link to comment
Share on other sites

You misunderstood EVERYTHING. Leopard is BOTH 32bit and 64bit, but starting from 10.5 the 64bit support will be full, it means that every Carbon-Cocoa application can be written and compiled to take full advantages of 64bit. This DOESN'T mean that Leopard will be 64bit only.

Sherry Haibara

Link to comment
Share on other sites

You misunderstood EVERYTHING. Leopard is BOTH 32bit and 64bit, but starting from 10.5 the 64bit support will be full, it means that every Carbon-Cocoa application can be written and compiled to take full advantages of 64bit. This DOESN'T mean that Leopard will be 64bit only.

Sherry Haibara

 

Are you absolutely sure? I heard steve explicitly say there is no 32 bit version and "most" of the macs are 64 bit and hence leopard ready. It would also explain the sudden jump in Macbook Pros memory to 2GB minimum (since 64-bit allows more data to stay in RAM). They just switched to Intel and its not leopard ready then? I think i deleted the keynote after i watched it, but could someone check it up if they have the keynote?

Link to comment
Share on other sites

 

No.

 

http://www.apple.com/macosx/leopard/technology/64bit.html

 

64-bit Frameworks

In addition to the POSIX and math libraries supported in Tiger, Leopard enables developers to build complete 64-bit applications using the Cocoa, Quartz, OpenGL, and X11 GUI frameworks. You can even use 64-bit Java on capable Intel processors. And the 64-bit and 32-bit versions of the libraries are built from exactly the same code base, to ensure a consistent experience for both developers and users.

 

 

Leopard comes in 1 copy, and this 1 copy includes both the 32bit AND 64bit libraries, so the OS will run on from the old Powerbooks which were 32bit....to the Core Duo Macbook, Macbook Pros & iMacs to the new Core 2 Duo Macbook Pro's and Intel Xeon Mac Pros. Hence the ability in leopard to be able to run 32bit and 64bit applications side by side with full memory allocation.

Link to comment
Share on other sites

I heard steve explicitly say there is no 32 bit version

No, Steve said, that there won't be two platform dependend versions, like vista. Not one for 32bit and one for 64bit. Instead the one version will work on 32bit and 64bit Macs.

Link to comment
Share on other sites

Was that from last years WWDC? Last year the Core 2 Duo hadn't been released yet so it would have created a complication if leopard wasn't 32 bit compatible for developers. 32 Bit frameworks can also just mean 32 bit applications can be run on a 64 bit only OS (since 32 bit framework allows the 32 bit applications to run) - as in these new 64 bit x64 chips.

Link to comment
Share on other sites

Yoiu folks are stuck in PC land. Sun has been running 32/64 bit side by side for years. It is the basis of Solaris - apps compiled on Solaris 8 will, unless they access hardware directly, run un-recompiled on Solaris 10. Apple is simply taking a page from the book of Sun...

Link to comment
Share on other sites

Yes it is fine to run 32 bit and 64 bit side by side. But the "core" of the operating system must be in 64 bit since there are CPU instructions to execute 32 bit code seperately. That is to say the OS is 64 bit and able to run 32 bit applications and 64 bit applications side by side, its not new. The issue here is the OS is whether this core is 64 bit only or not, it can't be both otherwise apple would have to ship two Operating Systems..

Link to comment
Share on other sites

Oh, god, is this too difficult to understand?

The OS is cross-compiled. Its libraries are compiled for both 32bit AND 64bit. This means that if the OS is run on a 32bit machine, of course, it will load 32bit code and you'll cannot execute 64bit applications. On a 64bit machine, instead, you can use both 32bit AND 64bit applications.

However, THIS DOESN'T MEAN that OS needs to be compiled only for 64bit. In fact, actually, Tiger IS compiled for 64bit processors, but it hasn't the 64bit application layer upon the libraries. But Tiger can also run on 32bit processors, so, really, WHERE IS the problem?

Sherry Haibara

Link to comment
Share on other sites

Mainly the hardware problems.

Apple has quite a set platform, with a very limited number of possible, official changes (and DIYs are not supported), while MS has to support trillions of possible hardware combinations as well. As simple as that - Apple's work is easier, they just have to make jut one, well-fitting suit. MS has to prepare a whole-year collection of clothes for every imaginable activity.

Link to comment
Share on other sites

If apple can make their OS both 32bit/64bit in one OS, why didn't Microsoft do the same with Vista?

 

The $, in M$....is there for a reason. :blink:

 

 

Mainly the hardware problems.

Apple has quite a set platform, with a very limited number of possible, official changes (and DIYs are not supported), while MS has to support trillions of possible hardware combinations as well. As simple as that - Apple's work is easier, they just have to make jut one, well-fitting suit. MS has to prepare a whole-year collection of clothes for every imaginable activity.

 

Actually, its got nothing to do with the hardware beyond the processor support for 64bit. ;) Everything is handled by software, i.e drivers. It is the drivers that control the 32bit/64bit parallel adressing in Leopard...not the Mac hardware (other than the processor capibility. Apple could theoretically make Macs with as much hardware configurations as PC's...and Leopard could still run on them (1 hybrid version) regardless if they are 32bit/64bit. The hard part here, ofcourse is creating proper 32bit/64bit drivers. Leopard has the core archietechure to do this on the fly, so it is much easier on the developers to create true 64bit apps faster for OS X than they would be able to for Windows Vista. Moreover, since pretty much all PC's now come with C2D processors, the procsesor barrier for 64bit need not exists anymore....its all software (which includes the operating system) from here on.

Link to comment
Share on other sites

Yes it is fine to run 32 bit and 64 bit side by side. But the "core" of the operating system must be in 64 bit since there are CPU instructions to execute 32 bit code seperately. That is to say the OS is 64 bit and able to run 32 bit applications and 64 bit applications side by side, its not new. The issue here is the OS is whether this core is 64 bit only or not, it can't be both otherwise apple would have to ship two Operating Systems..

 

 

Oh, god, is this too difficult to understand?

The OS is cross-compiled. Its libraries are compiled for both 32bit AND 64bit. This means that if the OS is run on a 32bit machine, of course, it will load 32bit code and you'll cannot execute 64bit applications. On a 64bit machine, instead, you can use both 32bit AND 64bit applications.

However, THIS DOESN'T MEAN that OS needs to be compiled only for 64bit. In fact, actually, Tiger IS compiled for 64bit processors, but it hasn't the 64bit application layer upon the libraries. But Tiger can also run on 32bit processors, so, really, WHERE IS the problem?

Sherry Haibara

I think it's because of Windows being having a 32 and 64bit version.

 

Which by the way is on of the stupidest things I've ever seen, honestly...

Link to comment
Share on other sites

 Share

×
×
  • Create New...