|
11-20-2010, 03:05 AM
|
|
|
|
Join Date: Jul 2009
Location: Germany
Posts: 779
|
|
Quote:
Originally Posted by dawiinci
Why do we patch the dyld?
|
You do not need to patch /usr/lib/dyld itself using the latest Kernel Builds, only the /usr/lib/libSystem.B*.dylib files.
AMD CPU don't support SYSENTER Opcode, what is leading pure 32-Bit Apps into crash when running 64-Bit mode and causing some other problems, this resolves this issue.
Quote:
After upgrading to 10.6.5(6,7) do I have to do the dyld patching again?
After upgrading to 10.6.5(6,7) do I have to do the CPUID patching again and if so will the CPUID.txt change?
Updating iTunes or Quicktime can cause CPUID problems. Do I only need to patch the CPUID with a new CPUID.txt?
|
Well if one of the patched files gets overwritten by any update you'll ofcourse have to patch the new one. (In case of CPUID checks, only if those are still present.)
Quote:
|
Is CPUID patching really complete if I use this file [...]?
|
Propably not, as there are still more binaries, that contain CPUID checks, for example /System/Library/PreferencePanes/Spotlight.prefPane does - but those don't need to be patched when running -force64 mode, as those files are for both architectures and the 64-Bit part doesn't contain CPUID.
Quote:
|
Is it important which kernel version I use? (i.e. 10.4 with all patched to 10.6.5)]
|
The Kernel Version itself should not matter, but the kind of applied patching may do.
AMD Phenom II X4 955 - ASRock AM3A770DE - 8GB DDR3-1333 - Radeon HD 5570 1GB passiv - BCM4318 802.11b/g - Snow Leopard Retail
+++
AMD Phenom X3 8450 - ASRock AM2NF6G-VSTA (BIOS L2.39) - 4GB DDR2-800 - Radeon HD 4650 512MB - Snow Leopard Retail (retired) / OpenBSD
Last edited by Imkantus; 11-20-2010 at 03:09 AM.
|