Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If another version comes out, can't you just install it on top of this one or just software update it? I'm not seeing the big deal.

There is no guarantee that this build will be updateable by software update or if the build will have to be re-downloaded (assuming that there is another one)

Of course if you are not a developer, you should just wait for it to be in stores.
 
The RC driver from Intel definitely has "pre-release WDDM 1.1" in its ID string.

BTW, I've never had a BSOD from the driver. Just random pixel noise that is fixed by refreshing or minimizing/restoring the window in question.
That's pretty much what I've seen as well. The driver is pre-release with some flickering but it works without a hitch regardless.
 
64-bit support list please and documentation on this new update management system.


you can go to the following dir and update the following and you folks have 64bit by default.

Library\Preferences\SystemConfiguration\ and select

com.apple.Boot.plist

when you open you should have the following code..

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
</dict>
</plist>



You need the following code to run snow leopard in 64 bit by default

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>arch=x86_64</string>
</dict>
</plist>



Note: when you try to save it may wont allow you to save as you need to to give rights to the folder where you can read and write as at the moment its only READ! only mode


let me know how you guys get on.
 
You'd think it would be possible right? My restore button is disabled out. I tried to restore on a hard drive that already has a partition of SL and on a flash. Neither of them seemed to work. I'll give it another go.

You have to drag and drop the drive icon to the destination input field.
 
you can go to the following dir and update the following and you folks have 64bit by default.

Library\Preferences\SystemConfiguration\ and select

com.apple.Boot.plist

when you open you should have the following code..

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string></string>
</dict>
</plist>



You need the following code to run snow leopard in 64 bit by default

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>arch=x86_64</string>
</dict>
</plist>



Note: when you try to save it may wont allow you to save as you need to to give rights to the folder where you can read and write as at the moment its only READ! only mode


let me know how you guys get on.

You have to save it to your desktop then copy it to the folder.
 
Not saying what he hasn't heard is true or false but I don't think it is accurate. I do believe this is the gold master. There simply isn't enough time to go through another build, test that build, then go gold, press discs, package, ship to stores/users in a little more than a month. I don't believe Amazon would be allowed to take pre-orders unless a date was firm.

Now, this could be out there for devs to test and expect an update on the day of release. That would make more sense.

Why isn't there time? they still have another month to go; 2 weeks for packaging up, which leaves another 2 weeks for small adjustments. It wouldn't be the first time Apple has made modifications at the last minute.

i got an email that 10A433 has been seeded

I've have had a look and now some websites are claiming 10A433 is now the 'golden master' - so I can't work out why people are putting John Gruber up as some sort of Jesus Christ of the computer world - he is but one person making a guess as the release date.

Its a guess at the moment - as I said, Apple still refers to 10A432 and 10A433 as 'pre-releases'. Until that label comes off it - they're still pre-releases (shock! horror!)
 
Yep. A typo on the author's part.

So if 10A432 is the golden master - then the only computers booting into 64bit by default are XServe's - the rest are only 'capable' but not enabled by default if one goes by the Seed Notes that were included with 10A432. I wonder whether Apple has realised that even if they did go fully 64bit with all their drivers whether issues would end up rising with 3rd parties who aren't up to speed yet.

I had a look further into the whole x86-64 design and how Mac OS X boots - from what I understand the kernel is 32bit but Apple has enabled kernel access to the 64bit features such as 48bit addressing, extra registers and so forth forth. So it isn't a pure 32bit or 64bit kernel. The way the x86-64 documentation describes it - if you're in long mode, when you run a 32bit piece of software, it will run as it normally wood, however, you can access many (if not all) of the long mode features by hard coding them into your software so that you get the benefits of Long mode but without having to port the whole software to 64bit.

If that is the case then it explains why a 64bit application can run on a 32bit kernel and can also address 48bits of memory even though the kernel is 32bit.
 
Okay so i have the latest builds, I haven't seen any differences between the last build and this latest build...

can anyone tell me what has changed??
 
I work for Apple in London & i can confirm that build 10a432 is not the Golden Master it has just been given to select devs to test a few expert issues. 10A433 is on it's way (for server at least) and with uncomplete features like no prefs for quicktime and no default 64-bit for capable machines (i mean that not even the extensions are 64-bit by default). The installation has been polished and is being tested by the chosen devs. As i have heard there will be 1 or 2 more builds before it gets to golden master. There is still a bit of testing going on with the new bootcamp drivers but other than that it's basically there. i hope this corrects a few things, i'm not sure how pretty much the entire internet has got this wrong but none the less mistakes happen. :apple:

http://imattic.co.uk/

If that were even remotely true, congrats you just lost your job as you just violated your employee contract. And the whole internet getting it wrong is far more common than you think.
 
No Apple can address more than 35-bits of memory - what did you mean to say?

Pardon? your Engrish makes little sense to me. If you took the time to read the WHOLE post and read the PREVIOUS posts where I made a direct link to x86-64, then you'd understand what I was talking about.

Goto page 7: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/x86-64_wp.pdf

Read the part about defaults. Couple that with the fact that Mac's load straight into Long mode - then you'll see what I am getting at.
 
Why isn't there time? they still have another month to go; 2 weeks for packaging up, which leaves another 2 weeks for small adjustments. It wouldn't be the first time Apple has made modifications at the last minute.



I've have had a look and now some websites are claiming 10A433 is now the 'golden master' - so I can't work out why people are putting John Gruber up as some sort of Jesus Christ of the computer world - he is but one person making a guess as the release date.

Its a guess at the moment - as I said, Apple still refers to 10A432 and 10A433 as 'pre-releases'. Until that label comes off it - they're still pre-releases (shock! horror!)

There's rumors going around that they found issues with the 432 installer, so I wouldn't be very surprised at all if there was a small bump in the release.
 
Pardon? your Engrish makes little sense to me. If you took the time to read the WHOLE post and read the PREVIOUS posts where I made a direct link to x86-64, then you'd understand what I was talking about.

Goto page 7: http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/x86-64_wp.pdf

Read the part about defaults. Couple that with the fact that Mac's load straight into Long mode - then you'll see what I am getting at.

Thanks for the pointer, but the racial slur was unnecessary.

Page 7 does say that a 64-bit kernel is required to run 32-bit programs in compatibility mode, though. Where's a good resource to explain how Apple manages to run a 32-bit kernel?

It would also be nice to see something other than a 10 year old whitepaper from AMD, since Apple is using current Intel processors.
 
Thanks for the pointer, but the racial slur was unnecessary.

Page 7 does say that a 64-bit kernel is required to run 32-bit programs in compatibility mode, though. Where's a good resource to explain how Apple manages to run a 32-bit kernel?

Where is the racial slur? I don't even know what race you are - I use the word 'Engrish' to point to any bad use of English; the race person saying it has nothing to do with it. But then again, you're resorting to name calling and labelling anyone you disagree with as 'racist' doesn't surprise me.

Here it is: http://events.ccc.de/congress/2007/Fahrplan/attachments/986_inside_the_mac_osx_kernel.pdf

There is just a single kernel image for 32 and 64 bit Intel: It is loaded as a 32 bit process in 32 bit protected mode on both kinds of machines, and if 64 bit support is detected, the kernel switches into long mode compatibility mode - a mode that supports running 32 bit code, but also allows easy switching to 64 bit code. So the whole kernel code is still unmodified 32 bit code, but tiny stubs that deal with copying between user address spaces (which can be 64 bit), and the syscall and trap handlers are 64 bit code. Next to being an easy port, this has the extra advantages that the 64 bit capable kernel can still easily support 32 bit KEXTs, and conserves memory by being able to use 32 bit pointers throughout a large part of kernel code. On the flip side, the kernel cannot use the extended x86_64 register set and is restricted to a 32 bit address space.

But the understanding from the x86-64 is that Apple can tweak the kernel so that it goes beyond the defaults as mentioned in the x86-64 pdf I linked to earlier. If he is wrong - then you should contact the author directly.
 
Where is the racial slur? I don't even know what race you are - I use the word 'Engrish' to point to any bad use of English; the race person saying it has nothing to do with it. But then again, you're resorting to name calling and labelling anyone you disagree with as 'racist' doesn't surprise me.

Do a web search for "engrish racist" - you'll get lots of hits like:

The second title [“Laugh at ‘Engrish’”], however, employs a commonly used racist way for white people to mock the way they think Asian people speak. Yeah, I know “Engrish” was in scare quotes. But I still think it’s racist. Poke around the net for any boards talking about Asian issues, and you’ll find some ******* writing a comment in which he/she switches her L’s and R’s. Because it’s so f#cking funny, you know? And so original.

http://resistracism.wordpress.com/2009/02/26/huh-4/

I didn't "name call", I simply said that insensitive racial slurs were unnecessary. Even if we don't intend something to be racist, a poor choice of words could lead the listener to make that conclusion.


But the understanding from the x86-64 is that Apple can tweak the kernel so that it goes beyond the defaults as mentioned in the x86-64 pdf I linked to earlier. If he is wrong - then you should contact the author directly.

That makes sense - and means that Apple must be supporting 3 different kernels for 10.6.

However, my original comment was where "48-bit" came from, when no Apple supports more than 35-bits (32 GiB) of RAM.
 
Do a web search for "engrish racist" - you'll get lots of hits like:

The second title [“Laugh at ‘Engrish’”], however, employs a commonly used racist way for white people to mock the way they think Asian people speak. Yeah, I know “Engrish” was in scare quotes. But I still think it’s racist. Poke around the net for any boards talking about Asian issues, and you’ll find some ******* writing a comment in which he/she switches her L’s and R’s. Because it’s so f#cking funny, you know? And so original.

http://resistracism.wordpress.com/2009/02/26/huh-4/

I didn't "name call", I simply said that insensitive racial slurs were unnecessary. Even if we don't intend something to be racist, a poor choice of words could lead the listener to make that conclusion.

Mate, you judge word or words being used on the intended purpose by the person saying them - stop this post modernist horse crap of judging everything based on how YOU feel. How YOU feel is irrelevant - the only thing that is relevant is the motivation behind the words. The onus is on you to prove that there was racist motivation behind what I said - to which you cannot prove.

Btw, it was name calling - or more correctly, attempting to win a debate through intimidation. Use an emotionally loaded word, throw it around and then hope that the moderator will ban me.
That makes sense - and means that Apple must be supporting 3 different kernels for 10.6.

However, my original comment was where "48-bit" came from, when no Apple supports more than 35-bits (32 GiB) of RAM.

I just had a read through the segment on Mac OS X Internals which talks about the VM Subsystem. From what I understand now, after more reading, the lack of a 64bit kernel means very little considering that a 32bit kernel using Apples arrangement still allows huge amounts of memory to be accessed and 64bit applications can still access amounts larger than 4GB - I originally assumed that a 64bit application running on a 32bit kernel was still restricted to the kernel limit of 4GB per application.

The whole process seems a little more complex than what is happening in the Windows world at the moment - I guess I need to do some more reading to wrap my head around the concepts. The more I read, the more I appreciate the decisions Apple made which gives me all the benefits of 64bit applications without losing compatibility in the process.
 
who cares..., don't worry, be happy...

it is just that historically MS delivers a lot of bloated crapware, and w7 may be no different...

to believe that w7 is good, is to believe that the chevy Volt can do 230 mpg. You need to get use to the thought... that is all.

Sorry, but I use both OS X and Windows (SL and 7) and that is just not true. An objective viewpoint is that both are very good and work very well. OS X has some stronger points and Windows has some stronger points. I would love to switch to OS X completely because I like the way it looks and works (mostly) but I always wind up needing or preferring Windows for some things. There is no wrong or right answer to the debate, there are good points to make on both sides. Being dismissive of the other side weakens your own arguments.

The new Ribbon in MS Office 2007 (and now available to all apps in Windows 7) is VERY nice to use and makes my life easier. It would be nice if Apple would do something along those lines for their apps, it seems like an Apple kind of interface.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.