AMD Patcher 0.31 다운로드 배포 (Zephyroth CPUID 자동 패처 유틸리티)

Looks great, but I get this error on startup:

Then it wont accept any file I drag&drop to the program interface.

I'm using Leopard 10.5.5.

I've tried to download but all I see is this.

Also, I posted the following over at IM but you seem like the person in the know.

I'm looking for a better (faster) way of removing CPUID checks from OSX binaries. I'm currently using a shellscript with otool and the Maxxuss patcher to do the job. There is a snip from the script I currently use below. It works okay but as you can see it involves creating a temporary configuration using otool and then writing it…

Your help and advice would be appreciated.

@maya77Looks great, but I get this error on startup: Then it wont accept any file I drag&drop to the program interface. I'm using Leopard 10.5.5.

Yup.

And if you fix that error, it goes to another and then another...

BUT, this app is really looking good and once you do get past those errors it works just fine. Also these errors seem like just an oversight that *should* be quick and easy to fix.

Only thing I really would have liked to see is an option to not inject kexts into the package.

Oh yeah, for anyone who just can't wait here's a workaround for the errors

rm -f ~/Library/Preferences/com.zephyroth.AMD-Patcher.plist
sudo -s
cd /Users/
mkdir -p zephyroth/Desktop
touch zephyroth/Desktop/log-AMD-patcher
chmod -R 755 zephyroth
cd /tmp
rm -rf ASvD67
mkdir ASvD67
chmod -R 755 ASvD67

You can just delete the zephyroth folder once your done.

I selected the download folder as destination, but now my download folder icon has been changed by the program.
Is there anyway to change this back to normal?
I tried Candybar but it didn't solve the problem...

Thnx!

Zephy, it opens fine now but I get another error when drag&drop file:

@maya77Zephy, it opens fine now but I get another error when drag&drop file:

Did you already try deleting your old preferences file?

rm -f ~/Library/Preferences/com.zephyroth.AMD-Patcher.plist

I haven't tried the new version yet, but I think that problem is just that there are different fields in the new file but if you already have an old file it of course tries to use it instead of creating a new one.

If that is the case, I'm not sure if it's even worth coding to check if it's an old style preference file or new...

Probably easier to just add a Readme telling people to delete it if they've ever used old versions of the program.

Great Job Zephyroth on this.
But I have no use for it now As I am running retail on AMD without patching and running 64 bit too

Great release none the less

Well thats nice BHAST but since no one is making the new voodoo kernel available except to the testers, you seem to be one of the few who has it. I just want to say thanks for pointing that out again and again (yes over at your site as well). Maybe you can help shed a little light on this new kernel.

Deleted pref file.

Next error:

Then program freezes with this message:

Then only Force Quit can close it.

It should cancel update check if internet is not responding for x seconds.

And it wont accept that I have no password when it goes to patch files. If I leave password field blank it says "password invalid". I have no password, please accept "".

@p-JI selected the download folder as destination, but now my download folder icon has been changed by the program. Is there anyway to change this back to normal?

Delete "Icon" file from "Downloads" folder.

Note: It's hidden file.

@zephyrothIf yes then I can prolly remove the code for detecting and patching cpuids ... Tell me.

Nah, don't do that...

Maybe make it optional?

IMO, even if Voodoo supports all AMD processors, your app is still far from useless.

Voodoo should make retail AMD installs a breeze but the thing I'm not clear on is whether Voodoo does the "on-the-fly" patching once as needed, or whether it just does it constantly, sounds like it does it constantly? Maybe bhast could chime in on that...

Personally, I would rather not have the kernel doing any extra lifting that it doesn't have to. I'm sure the performance hit, if any, isn't noticeable but still...

@maya77Delete "Icon" file from "Downloads" folder. Note: It's hidden file.

@nfoav8orWell thats nice BHAST but since no one is making the new voodoo kernel available except to the testers, you seem to be one of the few who has it. I just want to say thanks for pointing that out again and again (yes over at your site as well). Maybe you can help shed a little light on this new kernel.

"Release candidate should be out 24 Nov '08. Final release expected 1 Dec '08 if all goes well."
So we all know tomorrow?
http://code.google.com/p/xnu-dev/ ↗

WOW
I wasn't trying to tell you to stop making your apps
or trying to be mean
I was just saying
And I said great release
yes the beta kernel supports the all cpus
AMD and Intel

Thanks P-J. I've been following this site pretty close so its nice to see when I take a break from looking at it that something has changed. I agree with Dies on the cpuid issue... why have them there if the system can remove them and then run with minimal op-code patching.

And to Bhast. I was in a bad mood the other day when I saw that you had shown off the op-code patch here as well as over at Leo4All. I just want to run retail and not worry about it anymore... Oh well. it'll get here when it gets here.

Zeph. Don't ever think your work isn't appreciated. So many people are frustration free because of ASU and the Patcher apps. keep tinkering.

for one I am not showing off I am just trying to get the info out
that is why i posted about it on my site

Please Clarify the Purpose of AMD Patcher for Me

Does it perform the patching done by ASU, so I can download one of the MOX updates separately and patch it with this before installing it?

@zephyrothyes it performs the patching done by ASU.

Sweet! I tried to perform updates a couple times from a fresh install off the 10.5.2 rev.2 DVD, but the process seemed to hang both times (we're talking >10 hours here!).

Incidentally, could ASU be rewritten in Cocoa, please? It just takes too long like this.

On a related note, this is on an AMD 64 3000+ and my system's performance is horrible! CPU activity is at a constant 100%, system at 70%. Would anyone have an idea why and how to correct this?

A great many thanks to zephyroth and all who've made running MOX on my AMD possible. I can't adequately describe the elation I felt seeing the "Welcome to Macintosh" animation appear on my pc!

@zephyrothI plan to rewrite all my apps in Objective-C. But I don't know when it will be done.

No need to rush. I rebooted my system to load SMBIOSResolver (which didn't work, incidentally), and the performance problem went away! Now its speed is comparable to the 1.9GHz iMac G5 which I've had for years. I'll see how it fares as the updates are installed.

I suppose it isn't necessary to incrementally upgrade the system as the same kexts will be injected into each upgrade package anyway. I guess I'll have to activate TM before the jump.

Thanks again for all your work, Z!

AMD 64 3000+
Gigabyte K8-NSC-939
1GB RAM

Though I have 1 issue with MacOSXUpdate 10.5.5 pakage, it sort of stops on detecting cpuids (file 39 on small 322.1MB pkg, and file 310 on combo update, probably same file). The drop down log window says:
23:12:35 Encrypted file detected (Finder)
23:12:35 Encrypted file thinned to i386
23:12:35 Retrieving info about encrypted file ...

I'm using LawlessPPC 10.5.4 release to fix this issue

When trying to patch the iTunes 8.0.2.mpkg with AMD Patcher 0.31 I get this far (See attachment) then nothing.

Edit: didn't screen capture the right window!

@zephyrothAll I see is the interface ... Give at least the log ...

Yeah…Fixed

@lateralusmanWhen trying to patch the iTunes 8.0.2.mpkg with AMD Patcher 0.31 I get this far (See attachment) then nothing. Edit: didn't screen capture the right window!

Why are you patching this installer? it works without patching on AMD.

@nfoav8orWhy are you patching this installer? it works without patching on AMD.

Oh alrighty then.

So when AMD Patcher does that in the future that means the .pkg doesn't need patching?

@lateralusmanOh alrighty then. So when AMD Patcher does that in the future that means the .pkg doesn't need patching?

no. I was only telling you that this one in particular doesn't need patching... something else was causing this to occur with your system.

Alright.

Now when patching iPhoto_7.14.pkg

AMD Patcher 0.3 shows this:
################# AMD Patcher 0.3 #################

Monday, December 1, 2008 4:17:51 PM

16:18:09 Checking package iPhoto_714.pkg ...
16:18:09 The package is a folder containing an archive
16:18:09 Extracting Archive.pax.gz ... (iPhoto_714.pkg)
16:18:25 iPhoto_714.pkg extracted.
16:18:25 Detecting loaded kexts ...
16:18:25 Checking for unnecessary files ...
16:18:25 Patching NVidia kexts if needed ...
16:18:26 Detecting script ...
16:18:26 Creating list of files ... (iPhoto_714.pkg)
16:18:29 List created.
16:18:29 Detecting cpuids ...
16:18:46 No cpuid found !
16:18:46 Detection finished.

and when patching with AMD Patcher 0.31 is shows this:
################## AMD Patcher 0.31 ##################

Monday, December 1, 2008 4:13:43 PM

16:14:24 Checking package iPhoto_714.pkg ...
16:14:24 The package is a folder containing an archive
16:14:24 Extracting Archive.pax.gz ... (iPhoto_714.pkg)
16:14:40 iPhoto_714.pkg extracted.
16:14:40 Checking for unnecessary files ...
16:14:40 mach_kernel has been removed.
16:14:41 Patching NVidia kexts if needed ...
16:14:41 Detecting script ...
16:14:41 Creating list of files ... (iPhoto_714.pkg)
16:14:44 List created.
16:14:44 Detecting cpuids ...
16:14:54
16:14:54 Results:
16:14:54 No cpuids found !
16:14:54 No encrypted files found !
16:14:54
16:14:54 Detection finished.
16:14:54 Recreating Archive.pax.gz ... (iPhoto_714.pkg)
16:15:01 iPhoto_714.pkg recreated.

Patcher 0.31 also doubles the file size from 77.6 to 147.5

looks like it could have used the Archived pkg to create two (one within itself)... zeph, any thoughts?

It did the same with the CompatibilityUpdateforQT755.
Original file size is 3.5mb, Patcher 0.3 made it 4.6mb, Patcher .031 made it 9mb.

################# AMD Patcher 0.3 #################

Monday, December 1, 2008 4:43:49 PM

16:44:11 Checking package CompatibilityUpdateforQT755.pkg ...
16:44:11 The package is a folder containing an archive
16:44:11 Extracting Archive.pax.gz ... (CompatibilityUpdateforQT755.pkg)
16:44:12 CompatibilityUpdateforQT755.pkg extracted.
16:44:12 Detecting loaded kexts ...
16:44:12 Checking for unnecessary files ...
16:44:13 Patching NVidia kexts if needed ...
16:44:13 Detecting script ...
16:44:13 Creating list of files ... (CompatibilityUpdateforQT755.pkg)
16:44:14 List created.
16:44:14 Detecting cpuids ...
16:44:18
Maxxuss Mach-O Binary Patcher v1.0

Patching file: /tmp/ASvD67/Archive/System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar
8 of 8 patches applied

Statistics:
1 of 1 visited files were successfully patched.
8 of 8 found patches were successfully applied.
16:44:18 Detection finished.
16:44:18 Recreating Archive.pax.gz ... (CompatibilityUpdateforQT755.pkg)
16:44:19 CompatibilityUpdateforQT755.pkg recreated.

################## AMD Patcher 0.31 ##################

Monday, December 1, 2008 4:15:07 PM

16:16:29 Checking package CompatibilityUpdateforQT755.pkg ...
16:16:29 The package is a folder containing an archive
16:16:29 Extracting Archive.pax.gz ... (CompatibilityUpdateforQT755.pkg)
16:16:32 CompatibilityUpdateforQT755.pkg extracted.
16:16:32 Checking for unnecessary files ...
16:16:32 mach_kernel has been removed.
16:16:32 Patching NVidia kexts if needed ...
16:16:32 Detecting script ...
16:16:32 Creating list of files ... (CompatibilityUpdateforQT755.pkg)
16:16:33 List created.
16:16:33 Detecting cpuids ...
16:16:35 Patching CPUID protected binary:
16:16:35 /tmp/ASvD67/Archive/System/Library/QuickTime/QuickTimeH264.component/Contents/Resources/QuickTimeH264.scalar
16:16:36 8 cpuids patched.
16:16:36
16:16:36 Results:
16:16:36 1 file was patched.
16:16:36 No encrypted files found !
16:16:36
16:16:36 Detection finished.
16:16:36 Recreating Archive.pax.gz ... (CompatibilityUpdateforQT755.pkg)
16:16:37 CompatibilityUpdateforQT755.pkg recreated.

Excellent work, just beutiful. Now updated to 10.5.5. Flawless.

Patcher 0.31 Auto Update Delete-O-Thon

I am not sure what happened but I had the 0.30 Patcher in my Apps folder and it just prompted for an update. So I figured Id give it a try. When I did this I noticed the icon for my apps folder in my dock start cycling through apps. So I check and I watched as all my apps disappeared including utilities. I Force Quit the patcher and got an Applescript error that was extremely long with each line saying

rm "one of my apps"
rm "another of my apps"
..

Im sorry to not have saved the log but I was a bit jolted. I am in the process of replacing the apps folder with the one from my backup drive. If that doesn't work ill just restore the entire drive from the image.

Nothing else was running and the computer had been on for about an hour. So my guess is that it had something to do with me having the patcher in the apps folder and then the update wanting to rm the patcher and replace it with the update?

Is this something that anyone else has experienced? Or should I be looking for a different reason?

I in no way want to discourage anyone from using this app or zeph's asu as they are both wonderful apps. I am personally just a bit scared of the auto updater. : :