edmund - Marvin patches Leo after it has been installed onto a partition. It is run from another known working OSX installation. You need two partitions. An iso or dmg could be patched, but it would be a very difficult thing to do. All of the installer packages on the disk image would have to be expanded (basically they would be installed into folders). Then run Marvin to patch whatever it finds inside those folders. Then the folders would need to be recompressed into their original packages and placed onto a new iso or dmg. The amount of work involved is essentially the same as installing it onto a partition - that is how far you would be breaking down the installation packages for patching. Yes, if you knew which packages contained binaries with encryption or cpuids, you could just expand those. But Marvin is designed to work on any current or future OSX release for which the location of encryption and cpuids is not known. Therefore, all packages would need to be expanded to find which files Apple decided to encrypt or embed cpuids.
ptesone - The status from Marvin should have said: - Encrypted: 0 and CPUID: 1. NVDAResman.kext does not have an encrypted binary - there is nothing to decrypt. But it does have a CPUID that needs to be patched. The CPUID is code that checks for an Intel processor before it will run. Unfortunately, there is a known problem patching cpuids in kexts. It is being worked on, but the method is entirely different. Marvin will patch the kext using the standard method, but this may not help - try it out. If Marvin did not find NVDAResman.kext as having a cpuid (look in the cpuid.txt file or the log file), then you need to change the permissions on the kext. Go to Terminal and type:
(you need to insert the name of the partition on which Leo is installed - like Leopard or OSX or whatever you called it - but without the "<" and ">")
(and use the quote marks for safety)
sudo chmod 755 "/Volumes/<your Leo partition name>/System/Library/Extensions/NVDAResman.kext/Contents/MacOS/NVDAResman"
(then type your password)
If you have already patched your Leo installation and you ask Marvin to do it again, he will get confused and stop - sorry about that. To patch NVDAResman.kext, point Marvin to the Extensions folder and run "Create a Patcher package". Then run again with "Patch all cpuids using cpuid file" and point Marvin to Leo and to the cpuid.txt file in the patcher package that was just created. Or, see if maybe a kext from 10.4.x will work. I examined most of the prerelease versions of Leo to see if one of them had a version of NVDAResman.kext without the cpuid, but no luck.
Nomade - I can't really think of a reason that Marvin is not working. It has been tested on both Intel and AMD machines running both Tiger and various versions of Leo including the final release. I just downloaded the file from Rapidshare and it worked just fine. One thought - did you expand the zip file in Windows? The zip was created on OSX and the Archive/Compress routine separates the original file into two parts to preserve them for later reconstruction - some OSX files are comprised of two parts and other OS's only recognize one part. In Windows, the two parts do not get combined and therefore the app probably won't run. In Windows, you might see two files in the folder - the second one would be called: "._Marvin's AMD Utility v.25" (there is a leading dot and underscore). That is the part that did not get recombined. The only solution it to expand the zip on OSX by double-clicking it or using a very recent version of Stuffit.