Leaderboard

@cpla I am here to share my style with you! OpenCore-0.5.6-RELEASE.zip

@ AudioGod - To close the thread because of one person would be a great lost to me and many others. I've noticed over time you are even willing to tear down your setup to try different ideas and methods just to help find a solution to a problem someone would post - NOW THAT IS DEDICATION and I applaud you. @ Tiem - No two board are alike, there will be a difference no matter how slight and may offer a difference in performance, so what works for you will not necessary work for another. It's often said 'We are here to learn and help each other' being rude or abusive solves nothing. If you don't agree with an idea or method, no one is forcing you to adapt, just move on and stick with what works for you.

Xcode remains the best option to edit plist files because this is Apple's used files.

clover-genconfig wasn't building because of 'extern "C"'. Fixed.

I just tried adding OcQuirks.plist and change DevirtualiseMmio to true and ForceExitBootServices to false. Otherwise the same as your EFI (+battery clear). For now it has survived a few restarts and cold boots without errors, including with booting windows in between. Only time will tell if that was a good solution. And don't leave @AudioGod ! Thanks again

They are talking about the way Xcode handles some fields (like the data field). Xcode: Plist Editor Pro: Pretty trivial to change the value on PED. Not so much in Xcode. So yeah, for the majority of people, PED is a much better way to handle Hack plists. Not like they are anything special (binary plists). Just a basic text file. Notepad works just as well and you can use Hackintool to convert between Hex, Binary, etc.

100 microseconds are very small time.

you wanna stop right there mate. Your rude and arrogant and constantly talk down to people and your out of line. I never said being wrong wasn’t ok I said the way you come across is wrong as your talking down your nose at people does make you come across like you think people are talking {censored}, this place is meant to be a place of discussion and not a place for you to constantly ridicule people. You have been reported to the mods on various occasions by other people and I always find out about it because they come back to me so you can think what you like but it’s you who needs to fix up and be more polite and stop looking down on people. Its idiots like you who make me want to close down this thread and go elsewhere

Ok. I will test myself a little bit more. I'm still having a discussion with ASUS about the Bios 3003 and the locked MSR 0xE2 register. I still think this could be the culprit at least in our case.

It means you have a problem with an entry in your config file. Either it's in the wrong place, or has an invalid field. NP. OC does support proper Apple shortcuts for cleaning it (OPT + CMD + P + R). Another way is using Hackintool (NVRAM tab). Yet another way is using Terminal (nvram -c for a total wipe or you can use nvram -d x and delete specific entries, where 'x' is the specific variable).

Thanks for letting me know. I'am changing that debug code. Will commit very soon.

I have booted with this new Clover and it looks like all is fine. 0:103 0:000 Clover : Image base = 0xC3C06000 0:105 0:001 CTOR C3CDBEE0 -1009926432 0:105 0:000 CTOR C3C0642C -1010801620 0:106 0:000 atexit(C3C1C3BC, C3CDA780, C3CBCF38, 24) 0:107 0:001 atexit : allocate 0:108 0:000 atexit : exit (atexit_func_entry_count=1) 0:109 0:001 atexit(C3C1C3BC, C3CDA7A0, C3CBCF38, 24) 0:111 0:001 atexit : exit (atexit_func_entry_count=2) 0:112 0:001 atexit(C3C1C3BC, C3CDA7E0, C3CBCF38, 24) 0:113 0:001 atexit : exit (atexit_func_entry_count=3) 0:114 0:001 atexit(C3C1C3BC, C3CDA7C0, C3CBCF38, 24) 0:116 0:001 atexit : exit (atexit_func_entry_count=4) 0:117 0:001 g_str = g_str:foobar 0:118 0:000 g_str2 = g_str:foobar2 0:118 0:000 global_str1 = global_str1 0:119 0:000 global_str2 = global_str2 0:120 0:000 destruct_globals_objects: idx=3 -1010711620, C3CDA7C0, C3CBCF38 0:122 0:001 destruct_globals_objects: idx=2 -1010711620, C3CDA7E0, C3CBCF38 0:124 0:001 destruct_globals_objects: idx=1 -1010711620, C3CDA7A0, C3CBCF38 0:125 0:001 destruct_globals_objects: idx=0 -1010711620, C3CDA780, C3CBCF38

xcode is fine yes but there has been an issue with saving in the ESP a few others have encountered this issue as well so we found that plist editor pro a better option

Thanks, looks kick ass!

And now that makes 3 people that it’s helped. Baffle!

You are right and that's why I chose Xcode for editing first in place but lately, when I use Xcode it starts to convert <integer> to <real> and giving this error while boot "Failed to parse real field of type 1". I create a new config.plist and still giving the same error. And I don't know how to fix this problem on Xcode. But I create the same config files with the same settings on ProperTree "Failed to parse real field of type 1" error gone. Why Xcode doing that I don't get it?

Works thanks

Maybe, You've to reset NVRAM after this change. Just my opinion.

Remove the key entirely. Clear your NVRAM. It should not hold the variable: csr-active-config.

I've the same issue despite of the correction: OCS: failed to parse key field of type 0. config.plist SOLVED: "integer" instead of "boolean" on one key in config.plist

Looking at it briefly, the only thing I found was @pickermode. You have it as External but if you're using NDK fork ( as your ACPI quirks confirms ) that pickermode should be "builtin" and not external.

2nd Release i think is little faster but all tools is shown by default and hidden with spacebar i think the better to reverse it (to be hidden by default )

Thanks!

buildme should autodetect an old setup and clean the enviroment automatically for c++ Clover. All fine here.

change it too 9 seconds instead bud

I've committed the final step to switch to C++ compiler. I've tested gcc53, xcode5 and xcode8 compilation. Tomorrow, I'll remove the debug code displayed when you launch.

I am releasing the external GUI boot picker for the standard OC https://github.com/n-d-k/NdkBootPicker, Binary release are available as well, auto built by Travis ci server. it won't work with this fork, so don't even try.

Hola Valuito, tienes que poner el hardware en tu firma y el método de instalar, para quien pueda ayudarte tenga una idea de que puede ir mal...

We have successfully converted our database charset to utf8mb4 in addition to applying a fix to posts with accented or otherwise special characters. If you notice any information has been lost or content is appearing garbled please let us know and we can attempt to recover. This conversion also allows more modern emojis to be used in the forum. Known issues: -Some old posts containing � may have been converted to the incorrect character. No information previously displayed should have been lost however. -Emojis are not supported through the quick edit/reply boxes. If you edit a post containing such characters, they will vanish on submission.

5104 wouldn't open here either but 5103 from the first page of this thread does. I had to use the "xattr -rc" command to get 5104 to run.