Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

apianti
apianti
Posted
Posted
Just now, chris1111 said:

I am not confused, I know that for long time so Why in the new change  VBoxHfs-64.efi is not mandatory?

 

No, it is mandatory, if you don't have HFSPlus.efi then it will install VBoxHfs. It's a preferential thing, HFSPlus is better, more optimized and more features, so that will be chosen over VBoxHfs. Move HFSPlus.efi somewhere else and install, I bet you will get VBoxHfs. Also you never want these two drivers together, they are conflicting and whichever happens to load last will be the file system driver. Or depending on your hardware it may have no idea what to do and allow both drivers to create file system interfaces, which would be bad.

chris1111
chris1111
Posted
Posted (edited)
30 minutes ago, apianti said:

 

No, it is mandatory, if you don't have HFSPlus.efi then it will install VBoxHfs. It's a preferential thing, HFSPlus is better, more optimized and more features, so that will be chosen over VBoxHfs. Move HFSPlus.efi somewhere else and install, I bet you will get VBoxHfs. Also you never want these two drivers together, they are conflicting and whichever happens to load last will be the file system driver. Or depending on your hardware it may have no idea what to do and allow both drivers to create file system interfaces, which would be bad.

I told You after commit 4502 See commits 

If you compile and create Package

This Drivers is selectable now so is not mandatory

 

EDIT ****

I have created my package based on being mandatory as it should be but it is not the case if you compile Clover at the last revision and create your package
this is not good for those who do not know, because they have to select the Drivers in the list but in fact it would not even have to appear as on the Official SF 4497 package

 

EDIT 2***

this is the latest Official SF Package

This Drivers is not mandatory :D because mandatory Drivers should be not visible

 

Capture.png.ef200606ce9fc93abb6dc8dc26e100e0.png

 

Edited by chris1111
apianti
apianti
Posted
Posted (edited)
31 minutes ago, chris1111 said:

I told You after commit 4502 See commits 

If you compile and create Package

This Drivers is selectable now so is not mandatory

 

EDIT ****

I have created my package based on being mandatory as it should be but it is not the case if you compile Clover at the last revision and create your package
this is not good for those who do not know, because they have to select the Drivers in the list but in fact it would not even have to appear as on the Official SF 4497 package

 

EDIT 2***

this is the latest Official SF Package

This Drivers is not mandatory :D

 

Did you try removing both drivers and unchecking the box then installing? Is there no hfs driver then? Because yes it should be mandatory unless HFSPlus exists, but maybe it will install HFSPlus if you don't check VBoxHfs. I have no idea. If that's the case that's for @Slice to explain, as I imagine he made the change..? Also, Chris, if you want I can add you as a developer if you want to fix the package, I know Philip is already there but there are some open tickets. You seem to find more bugs in it than anyone, and it really needs cleaned up. I'll just move you from member to developer, please just don't destroy everything, lol.

 

EDIT: Done, you are developer, fix the package, lol.

Edited by apianti
chris1111
chris1111
Posted
Posted (edited)
8 minutes ago, apianti said:

 

Did you try removing both drivers and unchecking the box then installing? Is there no hfs driver then? Because yes it should be mandatory unless HFSPlus exists, but maybe it will install HFSPlus if you don't check VBoxHfs. I have no idea. If that's the case that's for @Slice to explain, as I imagine he made the change..? Also, Chris, if you want I can add you as a developer if you want to fix the package, I know Philip is already there but there are some open tickets. You seem to find more bugs in it than anyone, and it really needs cleaned up. I'll just move you from member to developer, please just don't destroy everything, lol.

 

EDIT: Done, you are developer, fix the package, lol.

OK thanks but I going to work now, my  new job 1 PM at 9 PM 

I will see tomorrow

and Yes if you uncheck Drivers is not install if don't have it (Exemple Fresh install)

it was put in DriversOFF, thats why is appear in the list

 and should be in src / UDK2018 / Clover / CloverPackage / CloverV2 / EFI / CLOVER / Drivers64UEFI

 

This is my point of view

Edited by chris1111
apianti
apianti
Posted
Posted
3 minutes ago, chris1111 said:

OK thanks but I going to work now, my  new job 1 PM at 9 PM 

I will see tomorrow

and Yes if you uncheck Drivers is not install if don't have it (Exemple Fresh install)

it was put in DriversOFF and should be in src / UDK2018 / Clover / CloverPackage / CloverV2 / EFI / CLOVER / Drivers64UEFI

 

This is my point of view

 

I think you are correct, it should be mandatory but only install if HFSPlus is not present. Take your time, do it when you can, you already know more than me. I treat the package like a leper, haha.

  • Like 1
chris1111
chris1111
Posted
Posted
1 minute ago, apianti said:

 

I think you are correct, it should be mandatory but only install if HFSPlus is not present. Take your time, do it when you can, you already know more than me. I treat the package like a leper, haha.

it's the changes 4502 that made it, you're not responsible

have a nice day

arsradu
arsradu
Posted
Posted (edited)

I think the confusion here comes from the word "mandatory" itself. :)

 

If I got this right, I think the actual question was: is one of them selected by default in the UI, if it wasn't there before? And I think the answer here is: no, it is not. Which, could be indeed problematic for new users.

We're talking about that ticket that apianti was talking about on the previous page.

Re-quoting for your convenience:

 

Quote

When you install, a ticket is created for each item installed. If you start the installer again, the ticket will be found and the box will be auto ticked to upgrade. This prevents mismatched versions, also anything unchecked will be removed if it was checked before.

 

So, basically, if it's not a new Clover installation, if you had Clover installed before on that drive, and if you hadn't had that driver checked before (or if you were using HFSPlus.efi instead), it's not gonna be checked now (1. if you're still using HFSPlus, there's no need for VBoxHfs, 2. if you're already using VBoxHFs, it should be already checked, unless you want it removed now, in which case, you can uncheck it upon installation, and it will be removed). If you did have it before, it's gonna be kept like that (checked) when upgrading Clover.

Now, the possible problem comes for the new users who don't know what VBoxHfs/HFSPlus are, and whether or not they need any of them for their hackintosh to boot.

So, I think the question here is: for this particular case, if it's a new installation, if there's no HFSPlus already in place, will VBoxHfs be checked (and installed) by default so the user can boot?

Edited by arsradu
chris1111
chris1111
Posted
Posted (edited)
4 minutes ago, arsradu said:

I think the confusion here comes from the word "mandatory" itself. :)

 

If I got this right, I think the actual question was: is one of them selected by default in the UI, if it wasn't there before? And I think the answer here is: no, it is not.

 

We're talking about that ticket that apianti was talking about on the previous page.

 

Re-quoting for your convenience:

 

 

So, basically, if it's not a new Clover installation, if you had Clover installed before on that drive, and if you hadn't had that driver checked before (or if you were using HFSPlus.efi instead), it's not gonna be checked now (1. if you're still using HFSPlus, there's no need for VBoxHfs, 2. if you're already using VBoxHFs, it should be already checked, unless you want it removed now, in which case, you can uncheck it upon installation, and it will be removed). If you did have it before, it's gonna be kept like that (checked) when upgrading Clover.

 

Now, the possible problem comes for the new users who don't know what VBoxHfs/HFSPlus are, and whether or not they need any of them for their hackintosh to boot.

 

So, I think the question here is: for this particular case, if it's a new installation, if there's no HFSPlus already in place, will VBoxHfs be checked (and installed) by default so the user can boot?

Your not understanding the point 

EDIT ***

This Drivers  mandatory  should be not visible

 

 

Edited by chris1111
arsradu
arsradu
Posted
Posted (edited)
7 minutes ago, chris1111 said:

Your not understanding the point 

EDIT ***

This Drivers  mandatory  should be not visible

 

 

Visible or not visible, the idea is that it gets installed, on new systems, if there's nothing else already in place. :P

 

The fact that it's visible or not is not really important. If it's visible and it's also already checked by default so you can see that it's gonna be installed, that's even better, cause you can see exactly what will it install. You can make that checkbox greyed out for this case, if anything... :)

 

Edited by arsradu
chris1111
chris1111
Posted
Posted (edited)
23 minutes ago, arsradu said:

Visible or not visible, the idea is that it gets installed, on new systems, if there's nothing else already in place. :P

 

The fact that it's visible or not is not really important. If it's visible and it's also already checked by default so you can see that it's gonna be installed, that's even better, cause you can see exactly what it it installed. You can make that checkbox greyed out for this case, if anything... :)

 

Sorry but Your completely misunderstanding Clover package ( and why some Drivers is not visible and of course mandatory) :unsure:

Edited by chris1111
  • Like 1
SavageAUS
SavageAUS
Posted
Posted
8 hours ago, apianti said:

Oh, you need to fix you injections. They are no longer injected by default so you need to figure out which ones you need and enable them.

Are you able to be a little more specific? Is it the kexts that are not being injected or something else? Sorry I don't understand.

arsradu
arsradu
Posted
Posted (edited)

Speaking of mandatory vs non-mandatory drivers, shouldn't apfs.efi be one of the mandatory ones? I mean, I'm sure there are probably a lot of people still using HFS+. But the tendency seems to be towards switching to APFS. And, if I'm not mistaken, your drive is automatically converted to APFS if you're using an SSD anyway. There are ways around it. But, I mean, from a new user's perspective, that's the normal flow.

 

And...I suppose, just like with HFSPlus.efi, the problem here is the fact that this is not an open-source driver. So...if you have it, good. If not, well, c'est la vie. We can't build it to include it with Clover installer because there is no source for it (or it's under Apple's terms of use). But please, correct me if I'm wrong.

 

I suppose you can't boot an APFS volume with HFSPlus.efi or VBoxHfs.efi, right?

 

So...even if we make VBoxHfs.efi "mandatory", and install it no matter what, if you're using APFS, you're pretty much screwed anyway.

Edited by arsradu
  • Like 2
chris1111
chris1111
Posted
Posted (edited)
18 hours ago, Slice said:

Because some people have HFSPlus.efi flashed into ROM.

 

Ok your description SF Package

⬇︎

Spoiler

1Capture.png.d6b3756508f4e7b0c6e961675e61d38d.png

 

change for this 

⬇︎

Spoiler

2Capture.png.21bfeaa6f4b2f3d6fb6d11bac9634274.png

 

thats correct :D

Edited by chris1111
  • Like 1
jerryy2
jerryy2
Posted
Posted
17 hours ago, arsradu said:

Speaking of mandatory vs non-mandatory drivers, ...

 

I suppose you can't boot an APFS volume with HFSPlus.efi or VBoxHfs.efi, right?

 

So...even if we make VBoxHfs.efi "mandatory", and install it no matter what, if you're using APFS, you're pretty much screwed anyway.

 

I ran into this yesterday and not knowing what all of the options did (I am not well versed in what all of the options are, I tried two different installations. Both disks are APFS based. One (10.13.4) with just:

 

AppleImageCodec-64.efi

AppleUITheme-64.efi

DataHubDxe-64.efi

FirmwareVolume-64.efi

AppleKeyAggregator-64.efi

AptioMemoryFix.efi

FSInject-64.efi

apfs.efi

 

and one disk (10.13.5) with these same drivers as well as with the VBoxHfs.efi driver. Both drives cold and warm booted after the clover update to version 4509. I updated the 10.13.5 disk to 10.13.6, still with the VBoxHfs.efi as well as the apfs.efi driver. It still worked. I removed the VBoxHFS.efi driver and the 10.13.6 disk still booted.

 

So the mandatory inclusion may not be as much of a problem as long as the apfs driver is installed.

(Gigagyte Z370XP SLI and I5-8400).

Pavo
Pavo
Posted
Posted (edited)

VBoxHFS.efi or HFS+.efi is required just for install because macOS installer creates HFS+ partitions as RAM disk in order to continue with the installation of the OS. If you have completed install and only using APFS, APFS.efi is only required to booted the OS that is installed as APFS. but if you are like many hackintoshers in this community that has older versions of macOS installed (that do not have APFS) VBoxHFS.efi or HFS+.efi is required and as stated as (mandatory).Not trying to be offensive here but I don't understand how this is confusing......

Edited by Pavo
  • Like 3
jerryy2
jerryy2
Posted
Posted (edited)
1 hour ago, Pavo said:

VBoxHFS.efi or HFS+.efi is required just for install because macOS installer creates HFS+ partitions as RAM disk in order to continue with the installation of the OS. If you have completed install and only using APFS, APFS.efi is only required to booted the OS that is installed as APFS. but if you are like many hackintoshers in this community that has older versions of macOS installed (that do not have APFS) VBoxHFS.efi or HFS+.efi is required and as stated as (mandatory).Not trying to be offensive here but I don't understand how this is confusing......

 

Is the os installer still doing this (creating a hfs+ RAM disk) if you are entirely apfs based? I was not sure, so I that is why I left the vboxhfs.efi driver on the 10.13.5 disk so I would be 'safe' in doing the 10.13.6 upgrade/install.

Edited by jerryy2
elucidate the comment
Pavo
Pavo
Posted
Posted
13 minutes ago, jerryy2 said:

 

Is the os installer still doing this (creating a hfs+ RAM disk) if you are entirely apfs based? I was not sure, so I that is why I left the vboxhfs.efi driver on the 10.13.5 disk so I would be 'safe' in doing the 10.13.6 upgrade/install.

Yes the OS installer still uses HFS+ RAM disk and I would imagine that will not go away any time soon.

  • Like 1
apianti
apianti
Posted
Posted
On 5/31/2018 at 7:36 AM, chris1111 said:

 

Ok your description SF Package

⬇︎

  Hide contents

1Capture.png.d6b3756508f4e7b0c6e961675e61d38d.png

 

change for this 

⬇︎

  Hide contents

2Capture.png.21bfeaa6f4b2f3d6fb6d11bac9634274.png

 

thats correct :D

 

Please use the word firmware instead when referring to the bootstrap software. BIOS is not UEFI and vice versa, they are types of firmware. Try "This driver provides support for reading and booting from HFS+ volumes for macOS, do not install if you already have an alternate HFS+ driver or an HFS+ driver is flashed in your firmware."

 

9 hours ago, Pavo said:

Yes the OS installer still uses HFS+ RAM disk and I would imagine that will not go away any time soon.

 

Yeah, I think you are correct the installers wouldn't make sense to change to APFS. But, who really knows what Apple might do................ :worried_anim:

  • Like 1
 Share
Go to topic listing
×
×
  • Create New...