Customized OpenCore with additional features

[ameenjuz]

 

33 minutes ago, davidm71 said:

@n.d.k

 

I think theres a bug with latest fork release. I checked the spelling and case of 'OpenShell.efi' and have it registered in the plist file such that the main branch has no issues displaying it on the boot gui menu. And its where its suppose to be in the Tools folder. So wonder why it works with main branch and not with the fork?

 

Thanks

 

replace these two attached file in correct location

i hope that your windows will work

make sure you are using ndk version of OpenCore

set like this

BOOT.zip

Edited April 27, 2020 by anmool

[n.d.k]

33 minutes ago, davidm71 said:

@n.d.k

 

I think theres a bug with latest fork release. I checked the spelling and case of 'OpenShell.efi' and have it registered in the plist file such that the main branch has no issues displaying it on the boot gui menu. And its where its suppose to be in the Tools folder. So wonder why it works with main branch and not with the fork?

 

Thanks

 

 

With latest commit, You can now skip the custom/tools entry file checks with Misc->Boot->SkipCustomEntryCheck = YES.

fyi, original OC doesn't check custom/tool entries before they are added to boot menu.

[davidm71]

1 minute ago, anmool said:

 

replace these two attached file in correct location

i hope that your windows will work

set to 

BOOT.zip

 

Windows works now. Was able to fix it earlier. See my last couple posts. Just having issue with OpenShell being recognized with NDK fork off of usb stick. Maybe its because its off of a Usb stick but   it works completely with the main Opencore branch. So not sure why NDK doesnt want to display the openshell. Maybe i have to clean nvram. Idk.

3 minutes ago, n.d.k said:

 

With latest commit, You can now skip the custom/tools entry file checks with Misc->Boot->SkipCustomEntryCheck = YES.

fyi, original OC doesn't check custom/tool entries before they are added to boot menu.

Good to know. Thank you!

 

Will try it out soon!

 

Thanks

 

Btw: Default behavior must be true?

[ameenjuz]

14 minutes ago, n.d.k said:

 

With latest commit, You can now skip the custom/tools entry file checks with Misc->Boot->SkipCustomEntryCheck = YES.

fyi, original OC doesn't check custom/tool entries before they are added to boot menu.

@n.d.k windows blue screen issue during windows boot 

this issue is appear in latest commit changes 

i think that this is bug of BootProtect option

anyidea

[ken394]

2 hours ago, MacNB said:

 

Thx. Yes I know there some SSDT's provided with OC and know the PDF very well.

I was asking if you would share what modifications you made to your SSDT's to be able to boot Windows. 

I only added the If (_OSI ("Darwin")) to EC-USBX after mapping USP ports and seeing a reference in one of the PDF

Guides, getting windows to boot was hope and poke till it worked. The CPU management SSDT works either way which makes sense.

  What I tried and I have no idea which one or both 

Blessing window thru terminal and Startup Disk after getting NVRAM sorted

BootCamp

0. What additional software do I need?

   To enable operating system switching and install relevant drivers in the majority of cases you will need Windows support software from Boot Camp. For simplicity of the download process or when configuring an already installed Windows version a third-party utility, Brigadier, can be used successfully. Note, that you may have to download and install 7-Zip prior to using Brigadier.

   Remember to always use the latest version of Windows support software from Boot Camp, as versions prior to 6.1 do not support APFS, and thus will not function correctly. To download newest software pass most recent Mac model to Brigadier, for example ./brigadier.exe -m iMac19,1. To install Boot Camp on an unsupported Mac model afterwards run PowerShell as Administrator and enter msiexec /i BootCamp.msi. In case you already have a previous version of Boot Camp installed you will have to remove it first by running msiexec /x BootCamp.msi command. BootCamp.msi file is located in BootCamp/Drivers/Apple directory and can be reached through Windows Explorer.

   While Windows support software from Boot Camp solves most of compatibility problems, sometimes you may have to address some of them manually:

SSDT-EC-USBX.aml

!-5 9600K SSDT.aml

[ameenjuz]

only this word -flto caused  windows to boot and disappear
i removed this word -flto from OpenCorePkg.dsc and compiled worked
i solved my problem removing this word -flto
windows icon appearing and booting worked fine like before
close this conversation
mark solved

[btwise]

1 hour ago, anmool said:

only this word -flto caused  windows to boot and disappear
i removed this word -flto from OpenCorePkg.dsc and compiled worked
i solved my problem removing this word -flto
windows icon appearing and booting worked fine like before
close this conversation
mark solved

Is this parameter related to displaying Windows startup items?

[davidm71]

3 hours ago, anmool said:

 

replace these two attached file in correct location

i hope that your windows will work

make sure you are using ndk version of OpenCore

set like this

BOOT.zip

 

Those boot files are from the standard fork and not the NDK source. Anyhow giving up on getting it to work. @n.d.k I'm sorry I tried everything to get your fork to recognize the OpenShell.efi. I mean it recognized the CleanNvram.efi utility and even posted whatever name I chose to give it on screen in the menu. I even tried two different versions of OpenShell and it completely got ignored. Tried setting SkipCustomBootEntries to false and made no difference. So going to use NDK fork on my main hard drive to multiboot and OC main source on my usb when I need a shell for those odd occasions. Wish it worked but it doesn't.

 

thanks

Edited April 28, 2020 by davidm71
Cleaned up text

[ameenjuz]

25 minutes ago, davidm71 said:

 

Those boot files are from the standard fork and not the NDK source. Anyhow giving up on getting it to work.

@n.d.k I'm sorry I tried everything to get your fork to recognize the OpenShell.efi. I mean it recognized 

the CleanNvram.efi utility and even posted whatever name I chose to give it on screen in the menu. I 

even tried two different versions of OpenShell and it completely got ignored. Tried setting SkipCustomBootEntries

and made no difference. So going to use NDK fork on my main hard drive to multiboot and OC main source

on my usb when I need a shell for those odd occasions. Wish it worked but it doesn't.

 

thanks

sorry for wrong file uploaded

try this ndk version with latest commit changes

 

NDK-OpenCore-0.5.8-RELEASE.zip

[davidm71]

2 hours ago, ameenjuz said:

sorry for wrong file uploaded

try this ndk version with latest commit changes

 

NDK-OpenCore-0.5.8-RELEASE.zip

 

Thanks. Will install it and take it for a test drive tomorrow. Looked at file size and the Opencore.efi + bootx64.efi files are rather large, at 586 + 32 kb large, compared to the one I compiled a couple days ago at 436 + 9 kb in size. Main fork is even smaller so I wonder if theres anyway to get those files smaller in size?

 

Any how will try them out tomorow. Thanks

[ameenjuz]

3 minutes ago, davidm71 said:

 

Thanks. Will install it and take it for a test drive tomorrow. Looked at file size and the Opencore.efi + bootx64.efi files are rather large, at 586 + 32 kb large, compared to the one I compiled a couple days ago at 436 + 9 kb in size. Main fork is even smaller so I wonder if theres anyway to get those files smaller in size?

 

Any how will try them out tomorow. Thanks

just replace bootx64.efi to bootx64.efi and OpenCore.efi to OpenCore.efi sample

don't touch your working config

 

[davidm71]

12 hours ago, ameenjuz said:

just replace bootx64.efi to bootx64.efi and OpenCore.efi to OpenCore.efi sample

don't touch your working config

 

 

Tried out your boot files and had same result. Also think your compiler needs to be optimized as those file sizes were kind of large compared to my NDK compiled files from couple days ago. Anyhow had no problem booting Windows up with your boot files but still no Openshell showing up in the menu..

 

@n.d.k

 

This explanation doesn't make sense: 

Quote

ACPI patches and Booter Quirks are optional for non macOS with setting ACPI->Quirks->EnableForAll / Booter->Quirks->EnableForAll to yes (default is no).
     - SMBIOS and Device Properties patches will only applied to macOS.

 

 

I mean its counter intuitive to enable for all (meaning all OS's and setting them to true) the ACPI patches you would otherwise want to hide from Windows. Shouldn't it be set to NO? Or rather change the name in next release to 'ACPIPatchesOptional'..

 

Update: Was able to get Openshell in my boot menu but had to create a custom entry. Only one problem. When I go into the shell and then type 'EXIT' and return to the menu it becomes impossible to load up OS X and kernel panics. Possibly because ACPI data is shielded at this point?

 

Thanks

 

 

Edited April 28, 2020 by davidm71

[davidm71]

On 3/29/2020 at 7:07 AM, Pene said:

Hi,

Latest sources assert when starting shell with debug build.

Problem doesn't occur with release build.

 

And a couple of more questions, if I may:

- Mouse pointer is broken on my firmware. Is there a way to hide the cursor from appearing?

- When using HideAuxiliary=true, Shell entry is being hidden even if its entry specifies Auxiliary=false. Is this intentional? 

 

Thanks.

@Pene   Have you found a solution to the Shell entry being hidden? I have HideAuxiliary set to False and it still is not showing.

 

Thanks

[Matgen84]

19 minutes ago, davidm71 said:

@Pene   Have you found a solution to the Shell entry being hidden? I have HideAuxiliary set to False and it still is not showing.

 

Thanks

 

@davidm71

 

I've OpenShell when I press Space Bar using this settings:

 

            <key>HideAuxiliary</key>
            <true/>

             ....

           <key>Auxiliary</key>
            <true/>

 

[davidm71]

40 minutes ago, Matgen84 said:

 

@davidm71

 

I've OpenShell when I press Space Bar using this settings:

 

            <key>HideAuxiliary</key>
            <true/>

             ....

           <key>Auxiliary</key>
            <true/>

 

Ok Thanks. I will try it out. Assume the Auxiliary key is from the Entries section.

 

Thanks.

 

 

[francisjfl]

Desculpe pelo meu inglês, mas eu, como um usuário entusiasmado simples que adora ou hackintosh, tenho um problema aqui com o NDK aberto ainda em desenvolvimento, mas sei, mas na inicialização dupla catalítica 10.15.4 x Windows 10 x64. Toda vez que entra no Windows através do ícone, tudo bem, mas quando o computador é reiniciado, ele não entra mais na tela do OpenCore e vai diretamente para o SO de Bill. O que poderia estar acontecendo? A configuração do BIOS do meu sistema é a seguinte: gigabyte z170 gaming 6, I7 6700k, RX580 (8gb), 16gb memória Gskill red 2400mhz, monitor LG ultrawide 29 '2560 x1080

Edited April 29, 2020 by francisjfl

[btwise]

@ndk

In the latest build script,

cp -r "${selfdir}/Utilities/BootInstall" tmp/Utilities/ || exit 1

is invalid， because the Utilities/BootInstall folder not exists！

[Ellybz]

9 hours ago, francisjfl said:

Desculpe pelo meu inglês, mas eu, como um usuário entusiasmado simples que adora o hackintosh, tenho um problema aqui com o NDK opecore ainda em desenvolvimento, mas sei, mas na inicialização dupla catalina 10.15.4 x Windows 10 x64. Toda vez que entro no Windows através do ícone, tudo bem, mas quando reinicio o computador, ele não entra mais na tela do OpenCore e vai diretamente para o SO de Bill. O que poderia estar acontecendo? A configuração na BIOS do meu sistema é a seguinte: gigabyte z170 gaming 6, I7 6700k, RX580 (8gb), memória Gskill red 2400mhz, monitor LG ultrawide 29 '2560 x1080

If your Windows is booting thru a custom entry make sure the "Arguments" section inside Misc/Entries is empty.

Se o Windows estiver inicializando através de uma entrada personalizada, verifique se a seção "Argumentos" dentro de Misc / Entradas está vazia.

Edited April 29, 2020 by Ellybz

[davidm71]

Sounds like francisfjl's bios is resetting the boot order or something is tripping the change. I noticed mine did the samething couple times but in favor of opencore partition. Perhaps turn on SkipBootEntryCheck?

[francisjfl]

10 hours ago, Ellybz said:

Se o Windows estiver inicializando através de uma entrada personalizada, verifique se a seção "Argumentos" dentro de Misc / Entradas está vazia.

Se o Windows estiver inicializando através de uma entrada personalizada, verifique se a seção "Argumentos" dentro de Misc / Entradas está vazia.

Yes there is nothing there, this field is totally empty!

[francisjfl]

I have a hard time now finding the root pci address I tried a program but it doesn't seem to be working with Catalina

I would like to remember that with pure openCore release there is no such problem.

Edited April 29, 2020 by francisjfl

[davidm71]

You guys few pages back recommended an icon generator application?

 

Can't find it and not sure whats a good icon generator app?

 

Thanks

[MacNB]

7 minutes ago, davidm71 said:

You guys few pages back recommended an icon generator application?

 

Can't find it and not sure whats a good icon generator app?

 

Thanks

 

OC has one. See this

[AudioGod]

@eSaF is totally right so please People this is a thread for NDK OpenCore not being an absolute idiot on. Please take your bickering private and do not go off topic.

grow up you lot and show some respect to NDK and he’s thread please.

 

Thank you 

[LAbyOne]

On 4/29/2020 at 4:47 AM, btwise said:

@ndk

In the latest build script,

cp -r "${selfdir}/Utilities/BootInstall" tmp/Utilities/ || exit 1

is invalid， because the Utilities/BootInstall folder not exists！

 

it has been moved to Duetpkg

so now the new path is:  Opencorepkg/UDK/DuetPkg/BootLoader/bin

 

i suggest you wait for ndk to make the new modifications. 

Edited May 1, 2020 by LAbyOne