Open esafeddie opened 4 weeks ago
I had the same problem. Did you solve it
@coutureone Here is a temporary solution, please watch and download the latest beta version:
In general, the latest beta version will be shown in the link below, please feel free to leave a message if you have any questions.
Problem solved thanks to the Dev.
Problem solved thanks to the Dev.
thank you,i had solved it
@coutureone Here is a temporary solution, please watch and download the latest beta version:
In general, the latest beta version will be shown in the link below, please feel free to leave a message if you have any questions.
thank you, i had solved it
@ic005k hi error is not shown anymore but i cant see on OCAT Uefi interface Unload tab Or maybe am i missing something? Thank you
error is not shown anymore but i cant see on OCAT Uefi interface Unload tab Or maybe am i missing something?
Yes, but I don't know how to use this Unload at the moment, so I don't display things like tables on the OCAT interface.
If you know how to use it, please give an example, I will refer to your example. (Since I haven't used a Hackintosh system in a long time, I can't test these things)
error is not shown anymore but i cant see on OCAT Uefi interface Unload tab Or maybe am i missing something?
Yes, but I don't know how to use this Unload at the moment, so I don't display things like tables on the OCAT interface.
If you know how to use it, please give an example, I will refer to your example. (Since I haven't used a Hackintosh system in a long time, I can't test these things)
Unload Type: plist array Failsafe: Empty Description: Unload specified firmware drivers.~ Io be filled with plist string entries containing the names of firmware drivers to unload before loading the Drivers section. This setting is typically only reguired if a user-provided driver is a variant of an existing system firmware driver, and if the new driver would detect itself as partially loaded, or otherwise fail to operate correctly. if the old driver is not unloaded first. Warning: Unloading system firmware drivers is usually not required and not recommended. Poorly written drivers may crash when unloaded, or cause subseguent crashes leg by allowing themselves to be unloaded even though they have active dependencies). However standard VEFI network stack drivers should unload cleanly. Note L: See SysReport Drivers Driver ImageNames. txt for the list of drivers which this option can attempt to unload. The relevant name is the driver component name. Drivers are only listed if they implement DriverBindingProtecol and Loaded ImageProtocol, and have an available component name. Note 2: The NVRAM Lang and Platformlang variables are ignored when determining the driver component names recognised by this option, and listed in the Sysheport file. This is in order to make unloading images stable across changes in these variables. The UEFI Shell dh command takes account of these variables, so in some circumstances may display different driver component names from those listed for this option, unless these variables are cleared
maybe it is not only hackintosh related but i could be wrong
maybe it is not only hackintosh related but i could be wrong
Please download the latest OCAT development version to test, I have done further work on Unload:
maybe it is not only hackintosh related but i could be wrong
Please download the latest OCAT development version to test, I have done further work on Unload:
Do you mean this?
Do you mean this?
Yes, but I don't know what to fill in, that is, how to use Unload.
Do you mean this?
Yes, but I don't know what to fill in, that is, how to use Unload.
it seems you did well @ic005k https://www.hackintosh-forum.de/forum/thread/42354-opencore-sammelthread-hilfe-und-diskussion/?postID=796279#post796279
thanks at cobanramo from hackitosh-forum de
OCvalidate app needs updating to add the missing line in the newly released Opencore config.plist (See attached example)