Jump to content
xpamamadeus

Ozmosis

6,214 posts in this topic

Recommended Posts

No i've extracted it "as is" using UEFITool and no raw body or something else, now here's uncompressed one using MMTool

 

OzmosisBlackTheme.zip

Edited by fantomas1
All posts must be clearly written and easy to read.

Share this post


Link to post
Share on other sites
Advertisement

Well my tool will be a Windows executable though it could also run on a mac since I'm using QT. Its almost done just needs the code cleaned up and error checking. All it does it does is spit out the PNG and Plist files. Nothing more. Pretty simple at the moment but I suppose it could do more if I had more time. I also may enable it to be able to open up the firmware image itself without having to extract the them.bin file but I would have to borrow OZMTool for that and expand it if the author not mind. 

 

As far as testing out those themes you guys have posted haven't had the chance. At work now and would be prefer to be playing with code..

 

Thanks.

Share this post


Link to post
Share on other sites

Playing around with the Theme package the King posted and feel like a kid in a candy store.. but was wondering

what pre-requesites are required to compile the files as on my system it completely failed to pack them all...

 

Thanks

Share this post


Link to post
Share on other sites

Playing around with the Theme package the King posted and feel like a kid in a candy store..

Haha same for me :D Thanks a lot!

 

There are some folders that are required for the script to work. If you take a look into compile.sh these are:

 

Type | Folder | Name of file

FONTS=$THEME/Fonts/*

LOGOS=$THEME/Logos/*.png

POINTERS=$THEME/Pointers/*.png

BUTTONS=$THEME/Icons/Button_*.png

DEVICES=$THEME/Icons/Device_*.png

BADGES=$THEME/Icons/Badge_*.png

SELECTORS=$THEME/Icons/Selector_*.png

SPECIAL=$THEME/Icons/Special_*.png

BUS=$THEME/Icons/Bus_*.png

BACKGROUNDS=$THEME/Background/*.png

+ Theme.plist in $THEME Folder.

 

And there we also have a directory for a background image, everything you asked for ;)

 

Also make sure you name the files right:

# extract type, name, id and frame from filename ie Device_01_00_InternalDisk.png
  # type  = Device
  # id    = 01
  # frame = 00
  # name  = InternalDisk
I hope that I didn't missunderstand you :/ :)

Share this post


Link to post
Share on other sites

Hi,

 

I finally was able to load the OzmosisBlackTheme from the EFI parition and I have some interesting findings. The Oz Black Theme seems not to have keyboard support in my case and all my partitions are spaced too far apart to show all at once. The other finding has to do with where Oz was loading the Theme.bin file from. I assumed it was my Sierra partition running off of the first Sata0 cable but it turns out that I also had an Oz EFI partition on my NVME PCI-E drive that hosts Windows 10. This EFI parition is also completely hidden from OSX as its on a NVME drive and I didn't install any NVME drivers on purpose. Needed Hermit Shell for that and  looking into BdMesg Oz log reported finding the GUID of the Windows NVME first so I assumed thats where to copy the Theme.bin and what do you know it worked! It didn't need a four finger reset either!

 

This opens up an interesting possibility... Loading Sierra from the NVME drive. The only problem in the past I had was that  Oz wouldn't create a boot menu with out a Sata drive but maybe thats changed. Anyhow now thats out of the way time to make some custom themed mods!

 

Thanks

Share this post


Link to post
Share on other sites

Haha same for me :D Thanks a lot!

 

There are some folders that are required for the script to work. If you take a look into compile.sh these are:

 

Type | Folder | Name of file

FONTS=$THEME/Fonts/*

LOGOS=$THEME/Logos/*.png

POINTERS=$THEME/Pointers/*.png

BUTTONS=$THEME/Icons/Button_*.png

DEVICES=$THEME/Icons/Device_*.png

BADGES=$THEME/Icons/Badge_*.png

SELECTORS=$THEME/Icons/Selector_*.png

SPECIAL=$THEME/Icons/Special_*.png

BUS=$THEME/Icons/Bus_*.png

BACKGROUNDS=$THEME/Background/*.png

+ Theme.plist in $THEME Folder.

 

And there we also have a directory for a background image, everything you asked for ;)

 

Also make sure you name the files right:

# extract type, name, id and frame from filename ie Device_01_00_InternalDisk.png
  # type  = Device
  # id    = 01
  # frame = 00
  # name  = InternalDisk
I hope that I didn't missunderstand you :/ :)

 

 

 

Just confused about how to name the Background.png file so it can get included in the theme.bin file. I now have The King's script working perfectly and it adds every included png file however skips the Background.png file. Suspect either I've named it wrong or have incorrect header info.

 

Thanks

Share this post


Link to post
Share on other sites

"*" stands for a random name so the background picture could have any name, as long as it has the right suffix and is placed in the folder called "Background".

 

What have you changed to the script to make it work perfectly?

Share this post


Link to post
Share on other sites

"*" stands for a random name so the background picture could have any name, as long as it has the right suffix and is placed in the folder called "Background".

What have you changed to the script to make it work perfectly?

I just found all the required dependencies and put them in a folder called Tools. Then i created a Windows environment variable called %TOOLS% and pointed it to my c:\tools folder and edited the script to look in %Tools% for the files. I named the background png file 'Background_00_00_Default.png' and placed it in the background folder. Also goto rename logo folder to logos as script looks in logos not logo. Then I ran the script and it worked by doing 'compile.bat nameoffolder'. The script even adds the appropriate tEXT header info. Only thing is the background doesnt work or Oz doesnt know what to do with it because bdmesg certainly says it got loaded. Maybe i got the name wrong or the numbers wrong or the plist needs to mention it I dont know. Only The King could possibly know. Cecekpown said its probably not implemented or was going to be in a later release.

 

Besides that I've gotten close to understanding why after my first cmos clearing why Hermitshell doesnt load. Apparently thats the only time i can get into my firmware volume memory mapped shell... After a reboot it no longer works and I'm forced to use bcfg boot add to create a link onto the hard drive. However doing a Bcfg rm for removing the hermitshell FV built-in volume restores functionality until the next reboot. My feeling is that the pointer to the volume gets lost somehow due to bios bug or something. Anyhow I wish I knew how to create my own FFS auto loading shell driver. Even better if you could convert the Clover efi boot file into an autoloading firmware volume driver the skys the limit..

 

Wish i knew how..

 

Thanks.

 

PS: Will post those tools files later if anyone wants them.

Tools.zip

Share this post


Link to post
Share on other sites

I don't if it's the right thing, but as I look into the QUO ROM, the module that contain MoBo Manufacturer Logo was deleted from it but steel present in the non Ozmosis ROM. If I'm not wrong, and if we delete it from the ROM as i did 6 months ago, at the boot screen no Logo appear only Black Screen! But my question is, did the QUO Board show the right Logo and background at the boot screen, because the old background with: QUO your configuration. .... your choice. is no more present in XMASS one?

 

@davidm71: Have a look at the Oz-QUO-AOS.ROM and MX-QUO-AOS.ROM, it can help you maybe to know something!

Edited by ammoune78

Share this post


Link to post
Share on other sites

I don't if it's the right thing, but as I look into the QUO ROM, the module that contain MoBo Manufacturer Logo was deleted from it but steel present in the non Ozmosis ROM. If I'm not wrong, and if we delete it from the ROM as i did 6 months ago, at the boot screen no Logo appear only Black Screen! But my question is, did the QUO Board show the right Logo and background at the boot screen, because the old background with: QUO your configuration. .... your choice. is no more present in XMASS one?

 

 

Since I don't have a Quo system I'm not sure. All I can tell you is that the Theme package The King posted last week has one called 'OzThemeH256' that has the selection icons twice as large as before, and two extra icons on the top toolbar including an 'About' and 'Config' icon besides the 'CMos' and 'EDKII' icons of which they are non functional. I'll post a picture for you guys later if I can. Unfortunately have no idea how to get the background working. Only can set three colors on the background of the top, mid, and bottom thirds of the screen. If there is a way to enable a background image I bet it needs to be set in the plist file...

 

FullSizeRender.jpg?raw=1

Share this post


Link to post
Share on other sites

I think the OzThemeH256 was never been released for public, it's THe KiNG Theme project, we need someone who have QUO board, maybe I'll ask IronManJFF? And if you look at the plist file you only'll see Background:#xxxxx, but no Background PNG instead. That explain, what i was meaning, Background is only color with Ozmosis icon, and this is why cecekpawon maybe asking a year ago for someone to make logo!

 

There's no Background PNG like Clover or Chameleon because as I said it was deleted from the Oz QUO AOS.ROM, this and it's what I think, but I'm still 75% sure.

Share this post


Link to post
Share on other sites

I think the OzThemeH256 was never been released for public,

That is correct but is not my project. H256 was designed for high DPI displays and was supposed to be implemented the same way Apple have, i.e. if high DPI resolution found load high resolution images if not smaller one, this is very helpful to have a nice looking theme on high DPI displays and also  on tablets/touch screen displays(yes  Ozmosis have touch screen support) where on small display size with high DPI small icons are almost impossible to touch...

Interface is the work of main developer not mine, I had an attempt with it but had luck and I was saved by BlackFrog who designed and implemented the current theme.

As far I know background image is not implemented yet, only color.

 

P.S. While om UI(UserInterface) pressing F10 will take screenshot on the root of EFI partition...

Share this post


Link to post
Share on other sites

@davidm71 You should be able to change the height and width of the background sections and also add sections. Have you tried that?

 

I don't know if this helps but the Theme.plist of the theme called "Standard" refers to the pointer picture using a GUID. It looks like this:

<key>Pointer</key>
	<dict>
		<key>ImageFile</key>
		<string>2CF68EED-7DDB-4784-9EDB-C1CF119483AE</string>
	</dict>
Maybe you could try to implement these lines into the Background section of the plist to point to a custom background picture. No idea if that will work though.

Share this post


Link to post
Share on other sites

@ammoune78 We are not talking about the BIOS splashscreen image, we are trying to figure out if there's a way to set an image as background for the OzmosisGUI. If you look at the image that david posted above, the idea is to replace the blue background behind the displayed boot options. That has nothing to do with the OEM Logo in the UEFI but with image data within the OzmosisHorizontalTheme ;)

 

Btw: Does this theme actually exist? http://www.insanelymac.com/forum/index.php?app=forums&module=forums&section=findpost&pid=2193678

Or is it just a mockup? I would love to know what options you can find behind the toolbar buttons :D

Share this post


Link to post
Share on other sites

I tried adding:

<key>Id</key>
<string>0</string>
<key>Image</key>
<string>0</string>

to:

<key>Screen</key>
	<dict>
		<key>Background</key>
		<string>#66ff33</string>
		<key>BottomMargin</key>
		<string>0%</string>
		<key>Height</key>
		<string>100%</string>
		<key>LeftMargin</key>
		<string>0%</string>
		<key>RightMargin</key>
		<string>0%</string>
		<key>TopMargin</key>
		<string>0%</string>
		<key>Width</key>
		<string>100%</string>
		<key>X</key>
		<string>0</string>
		<key>Y</key>
		<string>0</string>
	</dict>

Because I noticed the other icons were referenced by id and image number but that didn't work. I can only assume either its not implemented or the developer just didn't get around to adding it in there. Would bet anything that the original source code probably had it but commented it out. I mean why go through the trouble of writing a script that looks in a 'Background' sub-folder and compiles the file taking into account how many characters were in the word 'background' to parse out the id numbers out of the file name and not bother to include that feature?!

 

My only solution at this point is to use another boot loader like 'Refind' which allows custom background images and turn off the Ozmosis GUI. Only thing is I'm not sure if the Mac emulation would carry forward into another bootloader like Refind. In anycase I'll keep on experimenting on my free time. Only wish we knew who developed it so we could ask him ourselves. Maybe 'Blackfrog' could help?

 

Thanks

Share this post


Link to post
Share on other sites

^_^

 

THe KiNG you're exactly right: God gives, but do not put in bags.

Edited by ammoune78

Share this post


Link to post
Share on other sites

You can add icons on that OzmosisGUI, or link the OEM SplashScreen which we can replace with Background image that we are looking to add to the gui by entering it's Guid or put it on ESP or directly in the Theme.bin.

How can you link the OEM Splashscreen to the GUI and use it as background? I've never seen that and the Gigabyte Splashscreen doesn't get displayed either. So I don't get what you're saying or I'm just missunderstanding you...

The GUID I was talking about is for the pointer image which can be found in the Theme file. That's also why you can't find the ID in the UEFI.

 

 

I tried adding:

<key>Id</key>
<string>0</string>
<key>Image</key>
<string>0</string>
to:
<key>Screen</key>
	<dict>
		<key>Background</key>
		<string>#66ff33</string>
		<key>BottomMargin</key>
		<string>0%</string>
		<key>Height</key>
		<string>100%</string>
		<key>LeftMargin</key>
		<string>0%</string>
		<key>RightMargin</key>
		<string>0%</string>
		<key>TopMargin</key>
		<string>0%</string>
		<key>Width</key>
		<string>100%</string>
		<key>X</key>
		<string>0</string>
		<key>Y</key>
		<string>0</string>
	</dict>
If you look close, you'll see that

<key>Id</key>
<string></string>
<key>Image</key>
<string></string>
is always within a
<dict> </dict>
Also the only places where you can find "Id" and "Image" as the link to a certain picture is within the "Windows" section of the plist.

 

So I would suggest to try to add a background picture by implementing that into the Windows section. To try it out I would delete everything within the "Windows"-Plist-part but keep the "Selector"-section for example. Then change Top- and BottomMargin of that Section (i.e of Selector) so that it fills out the whole display.

Afterwards add

<dict>
	<key>Enable</key>
	<true/>
	<key>Id</key>
	<string></string>
	<key>Image</key>
	<string></string>
</dict>
to

<key>Selector</key>
<dict>
	<key>Background</key>
			<string>#2c364f</string>
instead of the "<string>#2c364f</string>" part. Maybe that'll work or is worth a try.

Share this post


Link to post
Share on other sites

How can you link the OEM Splashscreen to the GUI and use it as background? I've never seen that and the Gigabyte Splashscreen doesn't get displayed either. So I don't get what you're saying or I'm just missunderstanding you...

The GUID I was talking about is for the pointer image which can be found in the Theme file. That's also why you can't find the ID in the UEFI.

 

Forget what I said, because i was wondering to put my Profil Logo that i use as splashscreen in my ROM and put it it in the Theme/Icons/ folder, and pointing that Theme.plist to use it with black color background! Problem here is that it need to change the placement of the drives icons and all icons size, after that and finally will have a screengui with to much icons, this is why Hermit developer stuffs maybe decided to leave that damn background gui.

 

I just want to know how to compile it, because I have PNG missing when i'm trying to do it, I can try to change the icons size to have smaller icons and after that the Logo can be fitted discretly, and this is only what i need.

 

Excuse me if I wasn't clear!  

Edited by ammoune78

Share this post


Link to post
Share on other sites

@ammoune78 We are not talking about the BIOS splashscreen image, we are trying to figure out if there's a way to set an image as background for the OzmosisGUI. If you look at the image that david posted above, the idea is to replace the blue background behind the displayed boot options. That has nothing to do with the OEM Logo in the UEFI but with image data within the OzmosisHorizontalTheme ;)

 

Btw: Does this theme actually exist? http://www.insanelymac.com/forum/index.php?app=forums&module=forums&section=findpost&pid=2193678

Or is it just a mockup? I would love to know what options you can find behind the toolbar buttons :D

 

Good thing will be to contact BlackFrog maybe?

Share this post


Link to post
Share on other sites

HS DP6  install Success on QUO SysDef iMac 13,2 after changing Defaults.plist

		<key>BiosDate</key>
		<string>08/08/2017</string>
		<key>BiosVersion</key>
		<string>IM131.88Z.010F.B00.1708080805</string>

Share this post


Link to post
Share on other sites

Good thing will be to contact BlackFrog maybe?

 

Do you know how to get in touch with BlackFrog? Anyone know?

Share this post


Link to post
Share on other sites

You need to understand that theme is strict relation with Ozmosis Interface implementation, so all you can do is to use existing features that are implemented already, or wait for future implementations/releases.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By heiza
      Ryzen 7 2700X
      ASUS Prime X470 Pro
      32GB G.Skill Ripjaws V DDR4-3200
      ASRock Phantom Gaming Vega 56
       
      My motherboard doesn’t have an option for 4G encoding. And boot modes are listed as ”Windows UEFI Mode” and “Other OS”.
       
    • By blackosx
      Do you want to quickly find your boot log, or ever wanted to know which version of bootloader is installed on your disk(s), had the need to dump your BIOS from OS X, just curious about your own system setup or been asked to provide your setup information to others when asking for assistance?
       
      DarwinDumper is a useful collection of readily available tools, and scripts wrapped in an application framework giving you a convenient method to quickly gather a system overview of your hack or Mac. And rest assured that enabling the privacy option will mask sensitive data like the IOPlatformSerialNumber, IOPlatformUUID, IOMACAddress(s), USB Serial Number(s), SystemSerialNumber, serial-number, fmm-mobileme-token-FMM, MLB and ROM efi vars and CustomUUID in the dumped files and report.
       
      Current Release Version: 3.0.4, though latest beta DarwinDumper_v3.1.0b6


      The system dumps are saved to a folder or your choice, but defaulting to the same directory as the main application. You can choose to setup a symlink to make it simple to run DarwinDumper from the Terminal.
       
      There is an option to create an html report showing a complete overview of the dumps. This report will mostly just contain the text dumps as you'll find in the main dump directory, but for some dumps there is extra processing to try to present the information in a better way. For example, the Disk Partitions and Unique ID's dump will show a visual map of the disk layout, and the DMI Tables (SMBIOS) dump will show the data split by table type.
       

       
      Note: The html report does not contain all files from a complete dump so if seeking assistance for a problem and you wish to send someone a DarwinDump then you will want to send the complete dump directory and not just the .html report file.
       
      The following can be read and dumped by DarwinDumper:
      - ACPI tables.
      - Audio codec and further info.
      - Boot loaders and configuration files.
      - CPU info.
      - Device-properties.
      - Disk partition structure / info.
      - Disk sectors (hex).
      - DMI (SMBIOS).
      - EDID.
      - I/O Kit Registry.
      - EFI Memory Map.
      - EFI vars (some).
      - Kernel information
      - Kexts - (list of currently loaded kexts).
      - Memory.
      - NVRAM (both Apple specific and UEFI firmware variables).
      - SMC Keys.
      - LSPCI (PCI vendor & device codes) dumps.
      - Power (Sleep/Hibernate) settings.
      - RTC.
      - System Profiler.
      - System BIOS.
      - System Log(s).
      - Video BIOS.
       
      License:
      DarwinDumper is licensed under GNU General Public License, version 3.0 (GPLv3).
       
      Tools included:
      AnalyseVBIOS
      Copyright: Not Known. License: Not known Source: http://www.insanelymac.com/forum/topic/211294-information-on-vesa-modes-in-atinvidia-bios/   AppleIntelInfo Copyright: © 2012-2017 Pike R. Alpha. All rights reserved. License: Creative Commons Attribution-NonCommercial https://github.com/Piker-Alpha/AppleIntelInfo   atomdis Copyright: Michael Larabel @ Phoronix.com License: GPL Version 2 Source: http://www.phoronix.com/scan.php?page=article&item=amd_atombios_dumper   bgrep Copyright 2009 Felix Domke <tmbinc@elitedvb.net>. All rights reserved.   Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:      1. Redistributions of source code must retain the above copyright notice, this list of       conditions and the following disclaimer.      2. Redistributions in binary form must reproduce the above copyright notice, this list       of conditions and the following disclaimer in the documentation and/or other materials       provided with the distribution.   THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.   The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the copyright holder.   Source: https://github.com/tmbinc/bgrep   bdmesg Copyright 2010 by Islam M. Ahmed Zaid. All rights reserved. License: GPL Version 2 Source: http://forge.voodooprojects.org/p/chameleon/source/tree/HEAD/trunk/i386/util/bdmesg.c   cmosDumperForOsx Created by rafirafi, revised extensively by STLVNUB License: Information not available Source: http://www.projectosx.com/forum/index.php?showtopic=2432&st=0&p=21522&&do=findComment&comment=21522   csrstat Created by Piker-Alpha Copyright: © 2015-2017) by Pike R. Alpha License: Information not available Source: https://github.com/Piker-Alpha/csrstat   dmidecode http://www.nongnu.org/dmidecode/ License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2488   dumpACPI Created by blackosx. Idea taken from PHPdev32's MacIASL. Source: https://bitbucket.org/blackosx/dumpacpi   edid-decode Created by Adam Jackson, revised by Andy Vandijck License: Information not available Original Source: http://cgit.freedesktop.org/xorg/app/edid-decode Revised Source: http://bit.ly/1qAzqxb   fdisk440 Apple Computer, Inc. License: APSL v2.0 Source: http://forge.voodooprojects.org/p/chameleonApplications/source/tree/HEAD/trunk/fdisk.tproj   FirmwareMemoryMap script Amit Singh (showbootermemorymap) License: Information not available Source: http://www.projectosx.com/forum/index.php?showtopic=2447&st=120&p=19329&&do=findComment&comment=19329   flashrom http://flashrom.org/Flashrom License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2485&view=findpost&p=40285   getcodecid Copyright © 2012 AnV Software. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/285277-getcodecid-command-line-tool-to-detect-codec-id/   getdump Created by fassl?, modifications by Slice and AutumnRain? License: Information not available Source: https://svn.code.sf.net/p/voodoohda/code/tranc/getdump.c   gfxutil Copyright 2008 mcmatrix. All rights reserved. License: Information not available http://forum.netkas.org/index.php?PHPSESSID=q2isd338ihjjpcgbng7tne08pdv7tr4f&topic=64.0 Source: https://dl.dropbox.com/u/222155/gfxutil_source.zip   iasl Copyright © 2000 – 2014 Intel Corporation. License: Information not available Source: https://github.com/acpica/acpica   ioregwv Apple Computer, Inc. License: APSL v2.0 Source: https://bitbucket.org/blackosx/ioregwv   lzma Copyright © 2013 Igor Pavlov. License: GNU Lesser General Public License Source: http://www.7-zip.org/sdk.html   lzvn Copyright: © 2014 Apple Computer, Inc. All rights reserved. License: APSL Credit: Piker-Alpha, Andy Vandijck, MinusZwei. https://github.com/Piker-Alpha/LZVN   MacGap2 Created by Tim Debo. All rights reserved. License: MIT Source: https://github.com/MacGapProject/MacGap2   nvram Apple Computer, Inc. License: APSL v2.0 Source: https://bitbucket.org/blackosx/nvram   oclinfo Copyright © 2009 cmf License: GPL Version 2 Source: http://www.insanelymac.com/forum/topic/170796-opencl-info/   pciutils driver (DirectHW.kext) DirectHW is Copyright © 2008-2010 coresystems GmbH License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2480   pciutils lspci Copyright © 1997--2008 Martin Mares License: GPL Version 2 Source Code: https://kernel.googlesource.com/pub/scm/utils/pciutils/pciutils.git/+/master   Macpmem driver (Macpmem.kext) Copyright © 2007-2011 Volatile Systems. Copyright 2013-2014 Google Inc. All Rights Reserved. License: GPL Version 2 Source Code: https://github.com/google/rekall/tree/master/tools/osx/MacPmem]https://github.com/google/rekall/tree/master/tools/osx/MacPmem   RadeonDump Created by Dong Luo. Copyright 2008. All rights reserved. Modified by Andy Vandijck License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068   radeon_bios_decode Created by Dong Luo. Copyright 2008. All rights reserved. License: Information not available Source: http://www.insanelymac.com/forum/topic/282794-darwindumper/page__st__120?do=findComment&comment=1920068   smbios-reader http://www.nongnu.org/dmidecode/ License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?showtopic=2208   SMC_util3 Copyright © 2006 devnull  License: GPL Version 2 Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=23230   VoodooHDA.kext Created by fassl?, modifications by Slice and AutumnRain? License: https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h]https://sourceforge.net/p/voodoohda/code/HEAD/tree/tranc/License.h Source: https://sourceforge.net/p/voodoohda/code/HEAD/tree/]https://sourceforge.net/p/voodoohda/code/HEAD/tree/   x86info Written to succeed CPUID by Phil Karn (KA9Q). Contributed to by various people. OS X compatability by Slice License: GPL Version 2 Original Source: https://github.com/kernelslacker/x86info Revised Source: http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=41134  
       
      Running DarwinDumper from the command line:
      From Terminal, you can initiate DarwinDumper by running the following script directly.
       
       
       
      /DarwinDumper.app/Contents/Resources/public/bash/script.sh To help with this, the UI has a Symlink option which you can click to create a symbolic link which points to the above script. DarwinDumper can then be subsequently run from the command-line by loading a new Terminal window and typing darwindumper followed by return.

      Credits (in alphabetical order):
      Adam Jackson, Amit Singh, Andy Vandijck, Apple Inc., arsradu, bcc9, blackosx, cmf, DieBuche, dmazar, Dong Luo, droplets, ErmaC, Felix Domke, Google Inc., Intel Corporation, InsanelyDeepak, JrCs, Kabyl, Kynnder, Martin Mareš, mcmatrix, Michael Larabel, Mickey1979, phcoder, Phil Karn, Piker-Alpha, rafirafi, гык-sse2, Slice ,sonotone, STLVNUB, THe KiNG, Trauma, Volatile Systems, xsmile, !Xabbu.
       
      DarwinDumper was originally inspired as an open project by Trauma, it has remained an open project and please keep it an open project, so if you make any changes or additions to it then please share your work here.
       
      Please report any feedback, requests or bugs.
       
      Please note:
      DarwinDumper v3 requires OS X 10.9 and newer to run in the Finder, though it should work from the command line okay on older OS versions.

      The following link retains the download for v2.9.9.2 for older OS versions.

      DarwinDumper Download
    • By ErmaC
      Slice is glad to present a new EFI bootloader.

      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      https://sourceforge.net/projects/cloverefiboot/?source=directory
      There is a WIKI 
      http://clover-wiki.zetam.org/
      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      Post#2 CloverGrower - create Clover by yourself Post#3 Downloads Post#4 Installation of the bootloader Post#5 How to do UEFI boot Post#6 How to use - common words Post#7 Calculator for Automatic DSDT fix Post#8 Instructions for GraphicsInjector Post#9 ATIConnector patching Post#10 Any kexts patching with some Samples Post#11 CustomEDID Post#12 Hiding unnecessary menu entries Post#13 Instruction for DSDT corrections to do DeviceInjection works Post#14 Development Post#15 Themes Post#16 About kexts injection Post#17 Instructions for P- and C-states generator Post#18 Patching DSDT to get Sleep working Post#19 CPU settings and geekbench Post#20 ACPI tables loading Post#21 DSDTmini Post#22 Custom SMBios Post#23 F.A.Q. Post#24 iCloudFix Post#25 Using mouse. Post#26 How to make orange icons to be metallic Post#27 How to make software RAID (by Magnifico) Post#28 How to modify InstallESD.dmg (by shiecldk) Post#29 Config.plist settings Post#30 Using extra kexts and skipping kernelcache Post#31 Choosing EFI drivers Post#32 Configuration files Post#33 Automatic config.plist creating Post#34 Custom DSDT patches Post#35 How to do sleep/wake working with UEFI BOOT Post#36 DeviceID substitution (FakeID) Post#37 Using Custom OS Icons Post#38 Hibernation Post#39 Floating regions Post#41 Property List Editor Post#42 Blocking Bad Kext Post#43 AAPL,slot-name Post#44 FakeCPUID for unsupported CPU Post#45 Multiple Boot Options - to write into UEFI BIOS boot menu Post#46 How to install Windows UEFI Post#47 How to speedup Clover boot Post#48 Info.plist patching Post#49 Arbitrary device injection Post#50 Non-Standard Legacy Boot Files Post#51 Reboot to Windows UEFI from Mac OSX Post#52 Deprecated Features, part 1 Post#53 Using UDK2018 Post#54 Device Properties Post#55 Scalable themes Post#56 How to search Clover mistakes (bisection) Post#57 Deprecated features, part 2 Post#58 Programming Code Style -----------------
       
      Slice:
      I edited all posts in the thread to correspond to actual Clover revision.
      Please install Clover at least 2652 and use new instructions.
    • By Amedeo95
      Ciao, ho un hackintosh da anni e funzionava bene, come da titolo ho aggiornato clover, e l'aggiornamento non è andato a buon fine, ho quindi provato a riavviare il pc e mi trovo bloccato nella schermata in allegato.
      Vi sarei grato se mi riuscite a dare qualche indicazione.
      Resto a disposizione per ulteriori informazioni necessarie.
      Grazie in anticipo.

    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
×