Contribute
Register

[HOW TO] OpenCore 0.6.9 > 0.7.0 differences

Status
Not open for further replies.
Great info as usual @miliuco,

I've noticed that OpenCore v0.7.0 generates an additional Unix Executable file in my EFI named y that I know nothing about. Is this normal?
What is this Anyone?.png
 
CPU info for Hyper-V
  • Kernel > Quirks > added ProvideCustomCpuInfo (Boolean): Provides current CPU info to the kernel. This quirk currently provides correct TSC and FSB values to the kernel. It's for Hyper-V virtual machines. It can be False.
@miliuco I believe the entry is "ProvideCurrentCpuInfo", not Custom. OCvalidate gave me the ProvideCurrentCpuInfo error when I checked out my current config file as it's one of a number of entries missing after I updated to 0.7.0.
 
@Henties : did you check with ocvalidate? It found an error in my config.plist which didn't show when comparing it to sample.plist with OCConfigCompare.
ocvalidate is now my best friend for OC upgrades. I run the new OC's ocvalidate on my config.plist, review the errors and copy/paste the changes from the new sample.plist.
 
ocvalidate is now my best friend for OC upgrades. I run the new OC's ocvalidate on my config.plist, review the errors and copy/paste the changes from the new sample.plist.
Indeed! Yesterday I've modified my little guide, as I initially wrote it as "optional"... ;)
But as the last step of upgrading, it's a very healthy procedure instead. :thumbup:
 
Great info as usual @miliuco,

I've noticed that OpenCore v0.7.0 generates an additional Unix Executable file in my EFI named y that I know nothing about. Is this normal?...
I haven't seen this file in my EFIs ever. I don't know why its in your folder. As you say... WTF? :)
 
@miliuco I believe the entry is "ProvideCurrentCpuInfo", not Custom. OCvalidate gave me the ProvideCurrentCpuInfo error when I checked out my current config file as it's one of a number of entries missing after I updated to 0.7.0.
Yes, you're right, my mistake. Corrected in first post. Thanks!!!
 
ocvalidate is now my best friend for OC upgrades. I run the new OC's ocvalidate on my config.plist, review the errors and copy/paste the changes from the new sample.plist.
Yes, I agree. It's very very useful.
 
Great info as usual @miliuco,

I've noticed that OpenCore v0.7.0 generates an additional Unix Executable file in my EFI named y that I know nothing about. Is this normal?
I haven't seen anything like this with OC 0.7.0, but it sounds interesting. When you say OC "generates" the additonal file, when did you notice the "y" file? Is it possible that when you copied the OC 0.7.0 files to your EFI that you added "y" to your copy command and created the file yourself? Maybe you accidentally dragged and dropped another file or maybe you accidentally renamed an existing file? If you still have the file, it might be worth seeing what's in it (is it empty?).
 
I haven't seen anything like this with OC 0.7.0, but it sounds interesting...
Don't worry about it people, thanks, I've deleted it from my EFI and it's not re-appeared. I'll keep an eye on it though :thumbup:
 
As much as I love tinkering around with the various parts of what makes up a Hackintosh, OpenCore really needs to have an installer (OpenCanopy is about to the point of needing a graphical front-end, too) as well as some better way to handle all the changes and settings (too bad OC Configurator doesn't work nearly as well as the Clover version does).
 
Status
Not open for further replies.
Back
Top