Jump to content

tuxuser

Members
  • Content Count

    61
  • Joined

  • Last visited

About tuxuser

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

2,911 profile views
  1. Wow, awesome work! Finally somebody created such nice application!
  2. tuxuser

    OZMTool - An Ozmosis Toolbox

    Well, actions like modifying a BIOS image and flashing it afterwards is already dangerous, I agree. For commandline-Tools in general, I disagree - why should they be generally considered dangerous ? Specific case OZMTool vs. UEFITool though => OZMTool tries to be as verbose as possible by showing info for each file injected / deleted / compressed... HOWEVER: You should always verify the proper condition of the output image by yourself! OZMTool tried to warn the user if something failed - but such information is only as valuable as the code behind it... Oh and about the resizing of Volumes: Yes, it's UEFITool under the hood, all the magic (except Kext / Dsdt actions) are possible due the magic work of CodeRush
  3. tuxuser

    OZMTool - An Ozmosis Toolbox

    I compiled the releases with Qt 4.8.3 iirc - natively built on the target OS. Sorry guys, I am short on time lately, and I am very unhappy with the code layout of OZMTool.. Only real option would be a full rewrite imho..
  4. tuxuser

    Server migration

    Thanks Smx! You are my personal hero. <3
  5. tuxuser

    OZMTool - An Ozmosis Toolbox

    NOTE: 'parseInputFile: descriptor parsing failed, descriptor region has intersection with bios region' can be ignored.. It already says to ignore that... so just do.. It just happens cause gigabyte does not follow the specs 100% Really nothin critical
  6. tuxuser

    [GUIDE] Dell L701X (xps 17 late 2010)

    you need to patch IntelHD 1st Generation Kexts
  7. tuxuser

    [GUIDE] Dell L701X (xps 17 late 2010)

    try the other usb ports. the non-USB 3.0 should work
  8. tuxuser

    Ozmosis

    Use OZMTool... thats why it was created... ./OZMTool --ozmextract -i QUO.ROM -o oz1479ffs
  9. tuxuser

    OZMTool - An Ozmosis Toolbox

    Bump to v0.3 Windows version will follow when I find the time for it... Edit: windows version attached
  10. tuxuser

    OZMTool - An Ozmosis Toolbox

    afaik every Motherboard uses an bios? But I think that you mean non-UEFI bios?! no, that won't work... osmosis only works with AMI UEFI Bios
  11. tuxuser

    OZMTool - An Ozmosis Toolbox

    WTH, where did I implement such bug... crappy developer who wrote that tool
  12. tuxuser

    Ozmosis

    To reduce failure due byteswapping, I would recommend converting the Hexvalue to decimal integer. That's failproof Thx Pavo and THe KiNG for the golden hint
  13. tuxuser

    Ozmosis

    Thx for the golden hint - the screenshoot - made me realize I gotta byteswap the value.. Works fine now!
  14. tuxuser

    Ozmosis

    Yes, that works -> no more kernel panic However, no QeCI with stock ig-platform-id.. am not using a custom DSDT or SSDT... everything integrated into BIOS, Devicetables are stock...
  15. tuxuser

    Ozmosis

    Via Terminal in NVRam sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=XXXXXXXXXXXXXXXXX sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:HardwareAddress=00:01:02:03:04:05 sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:HardwareSignature=564D0764-CB64-4330-ABFB-357CEE624DAF Via Defaults.plist <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BaseBoardSerial</key> <string>XXXXXXXXXXXXXXXXX</string> <key>HardwareAddress</key> <string>00:01:02:03:04:05</string> <key>HardwareSignature</key> <string>564D0764-CB64-4330-ABFB-357CEE624DAF</string> </dict> greetz
×