Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About MrUnknown

  • Rank
    InsanelyMac Protégé
  1. DiskWarrior 4 Patcher for Hackint0sh

    The patcher has been updated to v1.02 and works with the following versions of DiskWarrior: DW v4.0(40) DW v4.0(41) DW v4.1(42) See first posting for links. .
  2. DiskWarrior 4 Patcher for Hackint0sh

    The DiskWarrior patcher has been updated to work with DiskWarrior 4.0 v40 and v41. See first posting above. .
  3. Hackint0sh Patcher for DiskWarrior 4 by Alsoft http://www.alsoft.com/DiskWarrior For many years, DiskWarrior has been the premier Macintosh utility to repair disk drive directory structures and the files in them. If Disk Utility cannot repair your drive, then DiskWarrior can probably do the job. Unfortunately, on a Hackint0sh, DiskWarrior sees the MBR partition scheme as something that needs to be repaired. Allowing DiskWarrior to make this repair would render the Hackint0sh unbootable. In addition, DiskWarrior has no feature to allow the user to select which repairs he wishes to make. The user can choose to make all repairs or no repairs. This patch to DiskWarrior only prevents it from repairing the MBR partition scheme used on a Hackint0sh. According to Alsoft, DiskWarrior 4 has some inherent restrictions: • It cannot repair the booted volume. The same restriction as Disk Utility. • It cannot repair the volume on which the running DiskWarrior application is located. Versions 4.0(40) and 4.0(41) have a restriction with Leopard (version 4.1(42) is OK with Leopard) • Alsoft highly recommends that DiskWarrior should not be run from a booted Leopard volume to make repairs. DiskWarrior can repair Leopard volumes. Therefore, DiskWarrior should be run from a separate booted volume which is not the target for the repair. For versions 4.0(40) and 4.0(41), this should be a Tiger volume, not a Leopard volume. If the patcher is ever updated, links to the new version will be posted here. Comments should be posted in this thread. Bugs may be sent in a PM to MrUnknown. The patcher comes with no warranties. Use it at your own risk. The patch is known to work on DiskWarrior 4 -- v4.0(40), v4.0(41) and v4.1(42). It may or may not work for newer versions. Update: new version (1.02) of patcher can handle DiskWarrior 4 -- v4.0(40), v4.0(41) and v4.1(v42). Download it here: http://www.mediafire.com/?9pl1ije3ldx http://rapidshare.com/files/90507514/DWpatch102.zip.html .
  4. Marvin's AMD Utility

    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.
  5. Marvin's AMD Utility

    DON'T PANIC! Folks - let's put on our thinking caps. Marvin's utility runs on OSX. So, to run it, you need to have a running OSX installation. And if it is running, it doesn't need Marvin's utility. So, you need an installation of OSX that isn't running for Marvin's utility to patch. To summarize - one OSX partition with OSX that runs and another partition with an OSX installation that needs to be patched. And neither partition has to be Leopard. You can patch 10.4.6 if that is what you desire.
  6. To allow OSX to run on your AMD machine, your new installation of OSX must have the encrypted binaries decrypted and the cpuids in the binaries patched. Don't Panic. Marvin has just the utility for you. Check out Marvin's utility here: http://forum.insanelymac.com/index.php?showtopic=67917
  7. Marvin's AMD Utility

    DON'T PANIC ! Marvin's AMD Utility For AMD users, this utility allows you to locate the binaries in your OSX installation which are encrypted or have cpuids. Then it will permit you to patch them so that they will operate on your AMD system. Choose from the following 4 options: Make Lists of Binaries The utility will locate all binaries that are encrypted and those which have cpuids and will provide lists of them to use as you choose. Create Patcher Package This creates the standard patcher package for use in single user mode. The utility provides a folder containing: A folder of decrypts (decrypted binaries) A script that installs the decrypts for you (replace.sh) A data file containing the addresses of cpuids needing to be patched (cpuid.txt) The Maxxuss Patcher which is used to patch the cpuids listed in the data file. Patch all cpuids using a cpuid data file This allows you to patch all of your cpuids using a cpuid data file that you specify. Where you got the data file is hard to know. Maybe you got it from Marvin's utility. Or maybe it was just floating around the galaxy somewhere. If this type of operation makes you panic, never fear - just click the "simulation" button. The cpuids won't be patched but you will be informed about what would happen if you tried. Oh, you did patch the cpuids and it didn't go as planned. Don't Panic. Just click the "undo" button and try it again. Patch all binaries Now you are being bold. Just click that button and let Marvin have his way with your precious binaries. If you are lucky, all of the encrypted ones will be decrypted and all of those pesky cpuids will be patched. Marvin says that you can find his utility here: http://rapidshare.com/files/65445720/Don_t_Panic.zip.html http://www.mediafire.com/?avncvt42nbk http://www.megaupload.com/?d=3U8IRVC7 And the answer? - 42 of course.