Closed Drovosek01 closed 1 year ago
Same for parametr EnableWriteUnprotector
Answers:
I think users must check every single key they don't understand and check whether they need it or not. As @PMheart stated, Sample.plist
isn't a reflection of the failsafe values, and - I wanna add - must be tweaked according to your needs.
Answers:
- We renamed "default" to "failsafe" many years ago, so you are correct.
- Our sample config is not a reflection of the failsafe values.
Thank you for the answers. Please add this info in OpenCore documentation
Not necessarily in my opinion - every user should refer to Configuration.pdf when setting up config.plist, while Sample[Custom].plist is not a necessity.
Not necessarily in my opinion - every user should refer to Configuration.pdf when setting up config.plist, while Sample[Custom].plist is not a necessity.
OK, in this case, please add the Failsafe.plist file to future releases, in which all parameters will be filled with failsafe values from the documentation. I think it will be convenient.
All failsafe values are clearly visible in Configuration.pdf, hence no need to maintain one more document.
In official documentation for latest release OpenCore (v0.87) https://github.com/acidanthera/OpenCorePkg/blob/10fc98fc5dd1fa569e988e0aef9ffe8e88ea74c7/Docs/Configuration.pdf for parametr FuzzyMatch failsafe value is false:
but it
Sample.plist
with same verion release parametr FuzzyMatch has value true. https://github.com/acidanthera/OpenCorePkg/releases/tag/0.8.7Questions: