Jump to content

391 posts in this topic

Recommended Posts

Ah...
Edit the theme.svg file in a text editor and look for a line near the top of the file that defines the background scaling.

BackgroundScale="scale"

If it’s set to scale then change it to crop, or vice versa.

Share this post


Link to post
Share on other sites
Advertisement
10 minutes ago, blackosx said:

Ah...
Edit the theme.svg file in a text editor and look for a line near the top of the file that defines the background scaling.

BackgroundScale="scale"

If it’s set to scale then change it to crop, or vice versa.

 

BackgroundScale="scale" is the right parameters for my system. Now I don't understand why I can't see icons completely

Capture d’écran 2019-01-16 à 18.04.15.png

Share this post


Link to post
Share on other sites

Lol. That’s my carefully crafted icon design so they’re supposed to be like that. I like my MacOS icons to be distinguishable from each other and not all the same.

If you would prefer a simple Apple logo then you can edit the file and change each mac icon (os_moja, os_HighSierra, os_Sierra etc.) to use the default ImageMacOS (I think as I’m not at my computer) image.

Share this post


Link to post
Share on other sites
3 hours ago, blackosx said:

 

EDIT3: Maybe we could look at some Clover colour cycling for effects?....

 

Same way we can move or rotate or transform Banner .

The problem is we rendered all images before enter GUI. Except text.

May be we can remake Clover to render SVG images at draw time then we will have dynamic picture.

Share this post


Link to post
Share on other sites

It was just an idea that I was throwing out there :)

 

Drawing directly to the video buffer would be amazing but how much work would that require? and would it be worth the changes? Would people make use of if?

Share this post


Link to post
Share on other sites

You wouldn't be changing the image size, right? So you could actually just rasterize right back into the same image buffer since you wouldn't need the old image anymore and just continue to render using image buffer.

Share this post


Link to post
Share on other sites

Here's a revised version of the silver theme I posted the other day but this time is uses simple flat coloured icons on a flat coloured background. Its pink for now, but the user can easily set it to whatever colour they wish.

 

image1.thumb.jpg.5254899e9d5a7d05ee8862918d05c0a1.jpg

image2.thumb.jpg.795d7cc17b94cff5681c1d00eb1a1f2d.jpg

 

The idea here is the theme colours can be easily changed by the user by editing only the following values near the top of the theme.svg file. Far easier than searching and replacing different elements through the whole file for different settings.

 

This setting will change the colour of the menu selector.

<clover:theme
  SelectionColor="0xb20068FF"
/>

And these settings css classes can be used to change the other colours.

<style type="text/css">
  <!-- Change overall theme colours with these classes -->
  .FillColourContent{fill:#b20068;}
  .StrokeColourContent{fill:#b20068;}
  .FillColourBackground{fill:#380021;}
  .FontColour{fill:#f7a4d4;}
  .FontColourNight{fill:#f7a4d4;}
  <!-- -->
</style>

- FillColourContent will change colours of banner, badges, menu items and selectors.

- StrokeColourContent is just for Knoppix badge (for now - may need a re-work of this logo).

- FillColourBackground will change the background colour

- FontColour and FontColourNight as self explanatory. 

 

EDIT: The scroll bar, for now, takes it's colours from the FillColourContent and FontColour classes.

 

FlatCustom.zip

 

* This is still a work in progress but its completely useable as it is.

 

Edited by blackosx

Share this post


Link to post
Share on other sites

@Slice

New cesium theme has an issue with count down times, it cuts into the volume label. I took the screenshot with the times on the screen but its gone in the screenshot as you can see.

 

@Slice @blackosx

Also both Clovy and BGM_SVG themes freeze up if i let the countdown timer expire (10 seconds).

If this is just me it's happening too i will post files needed.

screenshot0.png

Edited by SavageAUS

Share this post


Link to post
Share on other sites

Yeah. I also experience a freeze with GUI using vector themes @SavageAUS.

 

I've been pretty busy recently so haven't run proper tests but using BGM_SVG I see freeze when:

- leaving timeout to countdown to zero.

- pressing return to boot selected boot device.

- pressing space and choosing to boot selected boot device from the menu.

 

I'll try to look in to it soon.

Share this post


Link to post
Share on other sites

@SavageAUS

The bug with messages on screen was resolved in Clover 4871.

May be the bug with freeze too. You should confirm it with recent clover.

 

I encounter some freezes that I can't still understand. It looks like vector theme rendering depends on hardware. I already reported that the same picture looks different with Intel and Nvidia cards. It's impossible because drawing performs same way as PNG theme, same procedures. The differencies only on image preparation, pure mathematics. But how mathematics may depends on graphics? I may suggest that float arithmetics run on Intel GPU :shock: if present. If it is true then it can be a reason why vector themes are not working on some hardware. For example, SavageAUS, did you have IGPU enabled in BIOS? What if reverse?

Share this post


Link to post
Share on other sites

Here, Clover will successfully load and draw both Clovy and BGM_SVG themes and present a working UI.


Testing with Clover r4871.

1 - If Theme entry in config.plist is BGM_SVG then on choosing to boot selected device, the GUI locks up.

2 - If Theme entry in config.plist is Clovy then on choosing to boot selected device, all is good and Mac OS boots.

3 - If Theme entry in config.plist is Clovy then I switch to BGM_SVG in Clover GUI, then on choosing to boot selected device, I sometimes get the GUI freeze, or I have sometimes see Clover successfully close and pass on to the next phase.

 

screen.jpg.a7360896f22ee2b241d3fd7264ed7b51.jpg

 

But I get a reboot after that.

 

Checking debug log, the last line is:

33:973  0:092  Finally: ExternalClock=26MHz BusSpeed=100001kHz CPUFreq=3400MHz PIS: hw.busfrequency=104000000Hz

 

Spoiler

28:215  0:002  Checking EFI partition Volume 15 for Clover
28:217  0:002  === [ GetEfiBootDeviceFromNvram ] =========================
28:276  0:059   - found entry 2. 'Boot macOS from HighSierra', Volume 'HighSierra', DevicePath 'PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0x0,0x0)\HD(2,GPT,CE7D0665-EFE8-47C0-83CE-BC89C9C1938C,0x64028,0xDE4A310)\System\Library\CoreServices\boot.efii'
28:278  0:002  DefaultIndex=2 and MainMenu.EntryCount=14
28:280  0:002  Use anime=<null string> frames=0
33:875  5:595  BootVariable of the entry is empty
33:881  0:005  === [ StartLoader ] =======================================
33:973  0:092  Finally: ExternalClock=26MHz BusSpeed=100001kHz CPUFreq=3400MHz PIS: hw.busfrequency=104000000Hz
0:100  0:100  MemLog inited, TSC freq: 3400032970
0:100  0:000  LegacyRegion2: Chipset/proc: 0x01008086
0:100  0:000   Next Generation Core processors (PAM 0x80-0x86)

 

Is this behaviour memory related?

Could there be something in BGM_SVG, which is not in Clovy, which uses a different drawing routine which is causing the issue? I may try to remove items from BGM_SVG, one by one, and see if it makes a difference.

Share this post


Link to post
Share on other sites

:blink:

I see something new on your screen

RegisterData protocol installed successfully

What is it? If 10.13.6 then I also use the system and see no such message.

What drivers do you use in drivers64UEFI folder?

 

About theme differences I am not sure if it will be very useful to know what picture causes the crash but yes it still looks like a serios bug in rendering engine.

I tested in windows in QEMU with Clover compiled under VS2012. Vector themes have no OS_icons. It may be a bug of VS2012 compilation. Or may be the bug of the render.

Share this post


Link to post
Share on other sites

I'm not sure exactly what drivers I have in my Clover sub directory. I can check when I get home tonight.

 

However, that protocol comes from boot.efi

$ strings /System/Library/CoreServices/boot.efi | grep RestartData
RegisterRestartDataProtocol
Failed to install the RestartData protocol.
RestartData protocol installed successfully.

I guess this triggers the reboot after presenting the screen messages in the photo. 

 

Would trying to identify what makes boot.efi load that protocol help narrow down the issue, though maybe boot.efi just loads that if 'anything' is wrong so it probably won't help.

Share this post


Link to post
Share on other sites
2 hours ago, blackosx said:

I'm not sure exactly what drivers I have in my Clover sub directory. I can check when I get home tonight.

 

However, that protocol comes from boot.efi


$ strings /System/Library/CoreServices/boot.efi | grep RestartData
RegisterRestartDataProtocol
Failed to install the RestartData protocol.
RestartData protocol installed successfully.

I guess this triggers the reboot after presenting the screen messages in the photo. 

 

Would trying to identify what makes boot.efi load that protocol help narrow down the issue, though maybe boot.efi just loads that if 'anything' is wrong so it probably won't help.

Usually boot.efi search for external protocols. If it embedded then it can't be failed!

So some efi driver or even UEFI BIOS should provide this protocol. Is it 10.13.6?

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 glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
×