Is this safe with opencore now?
Yes, as long as Windows is booted through OpenCore and ProtectSecureBoot is enabled (as in the configuration provided with the guide).
Is this safe with opencore now?
It is indeed. As long as the:I had previously read that UEFI installations of windows 10 can corrupt the NVRAM By adding additional boot certificates. Is this safe with opencore now? Thanks
@cdf Sorry I missed your response.Yes, as long as Windows is booted through OpenCore and ProtectSecureBoot is enabled (as in the configuration provided with the guide).
I have been reading a lot here about this particular problem. My windows 10 (bootcamp) is in Legacy BIOS Mode so I can not see Windows in the OpenCore Boot picker. I just can open windows because I still have a flashed GPU with EFI selector.
Can you please confirm us that procedure you mention in you EDIT2 (Microsoft MBR2GPT command line tool) transformed your Legacy BIOS windows to UEFI Mode without issues and from then you can open Windows from Opencore Boot picker?
My Bootcamp Windows 10 is in a Partition of one SSD (different drives for my Mojave and my Catalina with Opencore)
Sorry if something is not clear. I am just a nonprofressional user. I know this problem has been treated in many places here but not in the users level, I should say. Thank you all the people here!
How about multiple videocards? No wegtree? For external-->internal drives there is still need for something like Innie, right?How about DRM decoding?Big update: The guide now includes a how-to for hardware acceleration. No boot arguments needed
How about multiple videocards? No wegtree? For external-->internal drives there is still need for something like Innie, right?How about DRM decoding?
Working great, thank you! HWAccel and Night Shift, damn name typo.Big update: The guide now includes a how-to for hardware acceleration. No boot arguments needed
You forget to turn off SMBIOS spoofingHello guys, I´m on 10.14.6, everything works great so far!
When I try to download Mac OS Catalina using SoftwareUpdate I got the failure u see in Picture 1, I cannot Download the installer.
When I download the installer with the Dosdude tool I get another error...
I´m on Firmware 144.0.0.0.0
Can anybody help me to find a solution?
As far as I can see, that covered everything we did in the boot argument, but with specific device path. Still haveHow about multiple videocards? No wegtree? For external-->internal drives there is still need for something like Innie, right?How about DRM decoding?
agdpmod=pikera
, shikigva=80
, and -wegtree
. Just in another format. So, all functions should work properly.I am thinking, for multiple graphic cards setup, this should be a better approach, because we can specify which GPU to handle HWAccel.
Boot argument of course is easier, because WEG will automatically do all required patch for us, but we also have no control about which graphic card to do HWAccel.
I mean multiple different GPU. e.g. A RX580 + Radeon VIIActually, the device properties for one GPU provides the settings for all of them. Using device properties is a good practice that follows the OpenCore philosophy of reserving boot arguments for temporary configurations.
Should that make any difference?
I just noticed something:I mean multiple different GPU. e.g. A RX580 + Radeon VII
Should that make any difference?
Quick question for the NdkBootPicker, which is the name for external disk yellow icon, like in your screenshot? I'm about to install it and I need a dark theme that matches the dark boot blackground. I would like to delete the background and use a plain black color instead. If you know a clean basic black there of you have one in the works, please let me know. Your screenshot has beautiful text under icons, mines looks pixelated and way bigger.
Thank you for letting me know, I'll wait for the 0.5.9 release and try it. I switched for now to the black newer boot screen.The screenshot is actually of OpenCanopy (the official OpenCore graphical user interface), which is intended to replicate the look and feel of the native Startup Manager. HiDPI support for the legacy gray background and HiDPI fonts should be available in OpenCore version 0.5.9. You are of course free to experiment, but for now the guide will not cover this.
I'm sorry if I misunderstood, but I believe you downloaded a pre-packaged zip file from the HWAccel thread. Any reason why you did not follow the simple instructions provided by @cdf into OP for HWAccel? Personally I build everything from scratch and pull all files directly from developer repos. Even the provided config.plist should be looked at and compared with original documentation.Used the pre-configured 0.5.8 package provided in AMD HWAccel related topic.
Have you installed Lilu and Whatevergreen?Second.
Just before OC output switches to OS output there appear some graphical glitches for a few seconds on the top part of the screen (same on any of both displays). Horizontal black stripe and some minor coloured dashes and dots here and there around it. Maybe someone had the same issue and found any fix for that?
I get these with my MVC flashed EFI card and OC. Some incompatibility in the EFI header in my videocard vbios I guess.Second.
Just before OC output switches to OS output there appear some graphical glitches for a few seconds on the top part of the screen (same on any of both displays). Horizontal black stripe and some minor coloured dashes and dots here and there around it. Maybe someone had the same issue and found any fix for that?
Re-built everything from scratch. Updated the message.Any reason why you did not follow the simple instructions provided by @cdf into OP for HWAccel?
Of course. The latest versions (1.4.4 and 1.3.9 respectively). HWAccel works like a charm.Have you installed Lilu and Whatevergreen?
Depending on which GPU you have
I have AMD Vega Frontier Edition.I get these with my MVC flashed EFI card and OC.