Jump to content
Sign in to follow this  
Followers 0

New OS X x86 build from Apple


omni

From Twin Mac:

 

Apple has seeded build 8B1027 to Apple Developer Platform owners. This build brings Transition Kit systems up to version 10.4.2, and in-sync with the current released version of Mac OS X.

 

This build includes new tatics to prevent piracy of Mac OS X. First and foremost, software built with 8B1027 will not run on previous Intel builds. Meaning, software built with 10.4.2 on Intel will not run on the current pirated copies. It is likely Apple will continue this procedure until the final candidate stage of Mac OS X for Intel.

 

In addition, future updates for Xcode for PowerPC Macs will likely prevent running software on older pre-release Intel builds.

 

Apple is expected to deploy much stronger TPM checks to final candidate builds, if not already implemented, in order to ensure the release versions of Universal Binary software will not run on non-authentic systems.

 

Joy...

Sign in to follow this  
Followers 0


User Feedback

Recommended Comments

Yeah, that came from some information posted here yesterday. It's still unconfirmed though - we'll have more information for you later on today!

Share this comment


Link to comment
Share on other sites

Oh, yep. Just saw it. I also posted our story in this forum. The breaking of the compatibility is very interesting - as a developer, I would be wondering if the apps I built on this build would be compatible with the next one...

Share this comment


Link to comment
Share on other sites

so when should we expect to see the next "scene" release of osx86 10.4.2 8B1027? ::rubs his hands together in excitment:: though unlikely, perhaps this version might have expanded support for ati and nvidia video? seems that even though intel is switching to x86 it will still presumably give comsumers the option of which cards they want in their workstations. it'd be nice to run osx86 with dual head displays instead of mirroring with a generc vesa 3.0 driver.

 

- aaron

Share this comment


Link to comment
Share on other sites

has this been dugg yet? i would know but im currently at school, i had to stay after for a club meeting :(. still trying to figure out a way around the windows firewall and blocked ports... im thinking linux live cd :-P

Share this comment


Link to comment
Share on other sites

I like it how the front page of this site is spreading baseless FUD. Saying that there are incompatabilities between pre-release builds, when it comes to application support, is trying to stop pirecy clearly has never used pre-release development tools before. I mean think about it would you want to purpesly sabatoge new code so it cant run for developers whom, as Apple admits, might not want to update.

Look at the known issues list, it says everything right there. If you are using a transition kit and using non-english as your primary language they give you issues. They note that they have updated the webkit and other development tools. Then they go on to say you may not want to use this incase of X.

People this is not rocket science. They finnished work on the development tools and some frameworks which broke compatability with the old non-universal system. So if you try to run the old universal systems it tries to use the old code that used some rosetta or not yet implemented code. OS X stops you.

Apple is doing this because it forces developers to use the new more optimal code and code paths. If you dont do something like this Developers will eventualy start abusing the old code. Just look at Windows9X a year or two after release. Developers started abusing left over code and compatability layers... that and because the OS trusted developers to know what they are doing.

 

I know this is over simplified and not exactly technicle but implying Apple is trying to do changes they needed to do anyways to stop piracy... well its like saying Microsoft releases security patches just to weed out the pirate copies using their genuine advantage system. Its a nice bonus but it probebly isnt even on their top ten list of reasons to release the patch.

Share this comment


Link to comment
Share on other sites

On the PPC side apple never released the FULL system as "patch" when a new 10.x system was still in development - there was never such issues (I allways use the pre releases of the system). OSX for x86 is in development since the first PPC Beta of 10.0 came out. forget it - this was made to keep the bad guys out.

Share this comment


Link to comment
Share on other sites

"tougher protections coming" ??? More like "*different* protections coming". For sure, some code changed, and new patches to oah740* will need to be made, but I don't think anyone's in a position to say (yet) that the protections are any harder to crack.

Share this comment


Link to comment
Share on other sites

Lets see, wait till u get your hands on that peice of software and you would be runing a better version of mac on your pc.It's a matter of time.

Share this comment


Link to comment
Share on other sites

Well lets see what could they have done...

 

* added more hardware specific calls

* embeded SSE3 deeper into the system.

* embeded TPM calls into more subsystems or even the main kernel itself

* removed "un-neccesary" kexts and broke compatability with generic darwin x86 kexts.

 

the list could go on. Dont underestimate what can happen now that the company can put its almost full weight behind it since they dont have to worry about news leaks.

Share this comment


Link to comment
Share on other sites

Folks, it is clear Apple is employing a strategy of dual-use. Apple did not take the time to secure Marklar because they knew the ABI's would not be permitted to run on builds that were not secured.

 

No report ever said that the updates to ABI's were intentionally to block piracy, simply that Apple ensured that the first post-WWDC seed was incompatible with the preceding leaked seed in order to minimize and wall off unsecured leaks.

Share this comment


Link to comment
Share on other sites

×