Jump to content
xpamamadeus

Ozmosis

6,187 posts in this topic

Recommended Posts

"*" 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
Advertisement

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

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

Wa

 

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.

 

Thats good to know and appreciate the information you have provided. Was just hoping to discover an undocumented feature or two to spice up the interface. Though one cool thing I have discovered is that the Theme.Plist references FFS GUIDs under the 'Command' key for certain functions that do not exist for everyone. So was wondering if perhaps I could replace one of the GUIDS with the 'QFlash'  bios module or some other efi program?

 

As far as getting a custom background image patience will be a virtue here I guess..

 

Thank you.

Share this post


Link to post
Share on other sites

...So was wondering if perhaps I could replace one of the GUIDS with the 'QFlash'  bios module or some other efi program?

I think a better answer you will get after you try and share the result with everyone.

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.

 

My answer for you is a question! Why from the OzmosisGUI and when you double click on BIOS Chip icon it takes you to UEFI Settings after a reboot, or double click on HermitShell for example it takes you to it? How can it be possible, now you'll not misunderstand me!  :wink_anim:  ^_^

Share this post


Link to post
Share on other sites

That is possible because of the OzmosisUI Implemetation in Ozmosis itself. Both services have fixed file GUIDs which are set in the theme.plist under "Command". Ozmosis reads this value and starts the EFI Application with the GUID set in the propertylist.

An OEM splashscreen isn't an EFI Application, though...

Share this post


Link to post
Share on other sites

That is possible because of the OzmosisUI Implemetation in Ozmosis itself. Both services have fixed file GUIDs which are set in the theme.plist under "Command". Ozmosis reads this value and starts the EFI Application with the GUID set in the propertylist.

An OEM splashscreen isn't an EFI Application, though...

Not only that but in Ozmosis.ffs I have found the Hermitshell Guid referenced in code so its hardwired to load the shell. Unfortunately in my system i either have to do a cmos reset or delete HermitShell from the boot menu using bcfg so it is reinstated or else the reference is lost after a reboot. I dont know if references in theme.plist will make a difference in my case but going to try probably by Sunday. Stay tuned.

Share this post


Link to post
Share on other sites

Some things are referenced in ozmosis.efi. This way the command "Firmware" also works although its obviously not a File GUID... I don't think that these values in the Plist are only there to look good, they should serve a purpose unless it's not implemented (yet).

Do you use a shell where the File GUID matches the one in the Theme.plist?

Share this post


Link to post
Share on other sites

Some things are referenced in ozmosis.efi. This way the command "Firmware" also works although its obviously not a File GUID... I don't think that these values in the Plist are only there to look good, they should serve a purpose unless it's not implemented (yet).

Do you use a shell where the File GUID matches the one in the Theme.plist?

No I was forced to use bcfg boot add as I couldn't get the built in shell working. It would work only once then after reboot not work anymore. Ill try to alter theme.plist guids and see what can happen.

Share this post


Link to post
Share on other sites

No I was forced to use bcfg boot add as I couldn't get the built in shell working. It would work only once then after reboot not work anymore. Ill try to alter theme.plist guids and see what can happen.

what does not work after restart? Theme?

Share this post


Link to post
Share on other sites

@Crusher,

 

No not the theme. What doesn't work is the 'Builtin Shell' or Hermitshell from either the F12 boot menu or from the Oz GUI. Only works once. After reboot not work again when trying to load it from Firmware Volume. So I have to create a bcfg boot add to hermitshell off of my efi folder.

Share this post


Link to post
Share on other sites

@Crusher,

 

No not the theme. What doesn't work is the 'Builtin Shell' or Hermitshell from either the F12 boot menu or from the Oz GUI. Only works once. After reboot not work again when trying to load it from Firmware Volume. So I have to create a bcfg boot add to hermitshell off of my efi folder.

Try to add and hermitshell via bcfg like a boot.

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 Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By apianti
      Just so you all know I actually have done something. I have pushed the source to both my github and to sourceforge, please commit to the experimental branch and I will merge it into the stable branch once it is safe. Also, nothing meaningful happens yet so don't get too excited. Only the Visual studio build works right now. I haven't set up the Xcode or Makefile builds yet, I'm trying to do them now.
       
      https://github.com/apianti/Clover
      https://sourceforge.net/p/cloverefiboot/Clover
       
      IA32/X64/ARM/ARM64 testing ISO (6/7/2018): Clover-3.0-experimental.iso
    • By cvad
      Bootdisk Utility Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
×