All you see are numbers, letters, and symbols and that can be a bit daunting. However, hex editors have a lot of great uses such as being able to debug and edit files, figuring out file information among others. There are dozens of hex editors in the market out there, but among the free options, one stands out due to its versatility and flexibility. What does it have to offer that it’s being lauded as one of the best free programs for editing hexadecimals? Portability That hex editor is the XVI32 developed by Christian Maas. Probably the thing that most people appreciate about the XVI32 is the fact that it’s extremely portable. Unlike most programs that come with large installer packages, XVI32 only comes in a ZIP file that doesn’t even take up too much storage space. All you have to do is to extract the ZIP archive file and run the program directly from the folder you extracted it from. This makes it very easy to launch and use. You can keep it on your flash drives and take it with you everywhere.Īside from its portability, the XVI32 has a lot of features that any user of hex editors will really appreciate. One important feature is the ease of editing hexadecimals. You can edit directly onto the interface. Perhaps I'll be able to find a 32 bit kernel for Mountain Lion and then use the older Lion drivers in 10.8.Additionally, you can copy, replace, and search words quickly in the hex editor. I am in the process of upgrading my T60P to Lion 10.7.5, and once I have success there I want to take a stab at Mountain Lion, but I'm pretty sure 10.7.5 is the highest I can go because there is no ATIRadeonX1000.kext in Mountain Lion, and the version included in 10.7.x is a 32 bit driver. The upside to using EVOEnabler on Lion over the plist and hex edits with RadeonHD on Snow Leopard is that my computer uses the official ATI framebuffer and thus works better without some of the glitches I observed with RadeonHD.kext I had success by injecting my device ID into both ATIRadeonX1000.kext and ATI1600Controller.kext and using EVOEnabler with my custom EDID data (extracted using SwitchResX prefPane). You may want to boot with -v -f the first time to reindex your kext caches.įWIW, on my card I didn't actually have to do the hex edits to get QE/CI working. Then once you are done making your ist edits and hex edits, just install the kext with KextBeast (or KextHelper, KextUtility, etc.), fire up Disk Utility and fix permissions and then reboot. If it complains about permissions (which it probably SHOULD since /S/L/E should be owned by root) i would recommend copying the entire kext to a folder owned by you, eg your desktop, and then editing the kext from there. Just search for d571 and swap all of the values for d471 and save the binary file. If I recall correctly, this string should appear three times in the binary. Basically what that means is if you are trying to change the value "71d5" you need to search for the string "d571". The compiled code in the binary blob is byte-swapped with the way that you read it in source. So for your card, I believe that the closest devID is 71d5. For me, I had to look for 71c5 and swap all instances of 71c5 with 71c4. Open this file with your hex editor, (I used hex fiend) and search for the device ID that is closest to your actual device id. It is a "binary blob", meaning that it is a block of code that can't be properly opened by a text editor the way uncompiled source code can be. The file that you need to hex edit is located at /System/Library/Extensions/ATIRadeonX1000.kext/Contents/MacOS/ATIRadeonX1000 Once Finder reloads you should be able to see all the hidden files on your HD. Building a CustoMac Hackintosh: Buyer's Guideĭefaults write appleShowAllFiles true & killall Finder
0 Comments
Leave a Reply. |