Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

  • Days Won


uglyJoe last won the day on February 15 2016

uglyJoe had the most liked content!

About uglyJoe

  • Rank
    InsanelyMac Geek

Recent Profile Visitors

3,681 profile views
  1. uglyJoe


    Do you now some more about the "SystemSerial"? From ozmosis with a hex-editor: <key>SystemSerial</key> <string>CK84593EXYL</string> <key>BaseBoardSerial</key> <string>CK84593EXYL</string> <key>ProcessorSerial</key> <string>CK0020DZE1D</string> "SystemSerial" has the same value like "BaseBoardSerial". So MLB = SystemSerial = BaseBoardSerial and best to use BaseBoardSerial?
  2. uglyJoe


    @ammoune78 I'm sorry but I really don't understand, what's the problem here. My first post in this context was addressed at you and anybody following this thread because I "discovered" TheRacerMaster's super cool script some month ago and didn't found much about it on IM. If you are aware of this script already - it's fine but where is the problem? My second post was addressed to lexb because he posted a corrupt plist and ask some specific questions that are all covered in the link I posted. And lexb wrote, that he normally is good in puzzling things together. The third post was meant as a warning because lexb wrote that he has only one machine running and the file (you reposted!) was corrupt. In the forth post I tried to give some last hints that may be relevant and not answered until that. I wasn't aware of the 'ROM' key and never read about it in any of the guides and it doesn't make sense to have two keys for the same value and I really could believe this if I see it in source code
  3. uglyJoe


    Ok, thank you for pointing this out! So we can use ROM or HardwareAddress and MLB or BaseBoardSerial? I did a quick test with VirtualBox and it was loading hfsplus, apfs and ozmosis from path and array. Very cool! DBounce.plist stored in ESP/Efi. Is this working from the bios, too? If yes - can you build a version that is loading from path by default and debug / logging disabled. Than we need no config, dbounce in bios and other drivers like apfs in the ESP. Thank you!
  4. uglyJoe


    There is no 'ROM' key with Ozmosis. From Pavo's guide: You can use your MAC-Address for this. To get iMessage working it's may good to have a <key>HardwareSignature</key> <string>A2A353F1-8BE9-480F-9596-2C43EC9895E0</string> Generate a unique one with 'uuidgen' from Terminal.app SystemSKU is IMHO the Apple Part Number - something like MD389LL/A - and not really necessary.
  5. Yes: VDADecoderChecker.zip
  6. Ok. Just a thought and maybe nonsense, but: If the video resolution is bigger than the monitor resolution, it could be the same problem. In this case, a recent version of the VDADecoderChecker should give you 'Hardware acceleration is fully supported'.
  7. Do you use a recent version of the VDADecoderChecker? There was a bug that caused this error code -12473: https://github.com/cylonbrain/VDADecoderCheck/commit/75067cc6b3dc0984ff5cee71a68d715a4d1b7b16
  8. uglyJoe

    rEFInd feat. Ozmosis

    Update (14.12.07): - adaptable icon spacing - apfs.efi from macOS 10.13.2
  9. uglyJoe


    But this file is corrupt!
  10. uglyJoe


    https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/PropertyLists/UnderstandXMLPlist/UnderstandXMLPlist.html http://www.insanelymac.com/forum/topic/306744-ozmosis-uefi-bios-modding-guide/
  11. uglyJoe


    I like this one: https://github.com/al3xtjames/MacGen
  12. uglyJoe

    rEFInd feat. Ozmosis

    ​00:000 00:000 Ozmosis 1.03.167X-CPWN RELEASE (2015-12-24 09:12:07 VS2013x86) on 2017-12-09 06:52:59 Btw.:Apfs.efi is from macOS 10.13.1 and I applied this patch http://www.insanelymac.com/forum/topic/327584-apfsefi-without-verbose-boot/page-4?do=findComment&comment=2530477 For testing I use VirtualBox with a 1GB Fat formatted disk image. Developing / compiling and can be done in a 10GB Lubuntu image and gnu-efi or edk2 from tianocore. I used edk2. I just recognized that one script is missing in the archive above shell-mode.nsh from the tools folder. This is called from most of the other nsh scripts for setting the shell mode if the script is executed @echo -off mode 128 40 so create tools/shell-mode.nsh by yourself or uncomment the line in the other scripts if you get an error message.Maybe it is better this way because you can test which mode is supported with your setup and then adapt the script to fit best. And I know it now Edit: Not much interest on this topic but anyway, I update the archive with the missing nsh script and a new oz defaults.plist (removed CpuType). Some Tipps: To create unique serials for your defaults.plist: https://github.com/al3xtjames/MacGen A UUID for the HardwareSignature can be generated with 'uuidgen' from Terminal.app Don't forget to change HardwareAddress to your MAC address!