Jump to content
5539 posts in this topic

Recommended Posts

4 minutes ago, Hifi33 said:

I didn't realize that.  Thanks! :)

By the way just so you know, the OpenCore EFI is indeed the release version of 0.5.7, hackintool is talking rubbish....:hysterical:

you can verify this For yourself at the bootpicker in the right corner it lists the version number and date. :thumbsup_anim:

  • Haha 1

 

3 minutes ago, AudioGod said:

By the way just so you know, the OpenCore EFI is indeed the release version of 0.5.7, hackintool is talking rubbish....:hysterical:

you can verify this For yourself at the bootpicker in the right corner it lists the version number and date. :thumbsup_anim:

 

I'll leave well enough alone, then. :hysterical:

Just now, Hifi33 said:

 

 

I'll leave well enough alone, then. :hysterical:

Hackintool is your friend, I have just never used it for upgrading OC or kexts. I do all that stuff direct from the GitHub only now days. I did used to use kext updater in the past though. That’s very good and doesn’t think my version of 0.5.7 isn’t release. (I just double checked) 

2 hours ago, eSaF said:

NDK OC - Dual Boot.webm

I shrunk the format as much as possible, hoping to show dual booting Catalina and Win 10 on a Gigabyte Z390 pro/wifi with AG's folder is definitely just fine.

Also YouTube Link 

 

Thank you very much Dear :lol:

6 hours ago, jimborae said:

 Yo uneed to install Thunderbolt Control Centre from the Microsoft App Store within Windows 10. Mine did the same although the drivers installed ok.  

 

I wouldn't have even thought of that. It would have been nice if the installer at least gave me a dialog box or a readme.txt tell me this! The driver installer behaves more like a Trojan Horse.

 

3 hours ago, eSaF said:

NDK OC - Dual Boot.webm

I shrunk the format as much as possible, hoping to show dual booting Catalina and Win 10 on a Gigabyte Z390 pro/wifi with AG's folder is definitely just fine.

Also YouTube Link 

 

could you pls send to me your bios setting file

big thanks

10 hours ago, AudioGod said:

To all the people having problems with windows using NDK OpenCore or Real OpenCore,

Myself, @texem @WizeMan @Tiem use OpenCore and @eSaF uses NDK OC as our daily bootloaders With no issues and I spend as much time in Windows as I do in Catalina and there is no problems what so ever with booting in any OS. If your having problems using my EFI then the chances are that there is something wrong with your setup somewhere like for example having your windows and Cat EFIs on the same partition will cause all sorts of problems or trying to reuse your old config.plist in the new EFI also will not work as to much have changed between 0.5.6 and 0.5.7

Same deal with NDK OpenCore.

FWIW I have never had a single issue using your EFIs. Even back when I literally knew nothing about Hacks, I just tossed your EFI onto my drive and boom, working macOS.

 

There were also a ton of changes between 0.5.6 and 0.5.7. It was a pretty difficult transition even if you kept up on the development. If you didn't, then yeah, upgrading OC isn't a cakewalk.

 

Never really had issues with Windows not booting either. With that said, one can always just hit F12 and use the MB EFI loader.

  • Like 1
10 hours ago, AudioGod said:

Sorry but You have lost me mate, start again and explain what the problem is exactly? LoL

Dear AudioGod,

 

My Windows 10 is installed on another disk (ADATA ssd nvme) and Catalina on another (Samsung Evo SSD).  The clover was on the Samsung efi.  It had a normal boot on both.  I installed Opencore pure and then immediately put the bootpicker of the NDK to improve the selection interface.  The opencore, like the Clover, is in Samsung's EFI.  However, when selecting Windows 10 in the Opencore menu, it is on a black screen and there is no boot. Catalina boot is ok. And is the os standard to boot. I selected it in macOS.

2 minutes ago, Praetorianus said:

Dear AudioGod,

 

My Windows 10 is installed on another disk (ADATA ssd nvme) and Catalina on another (Samsung Evo SSD).  The clover was on the Samsung efi.  It had a normal boot on both.  I installed Opencore pure and then immediately put the bootpicker of the NDK to improve the selection interface.  The opencore, like the Clover, is in Samsung's EFI.  However, when selecting Windows 10 in the Opencore menu, it is on a black screen and there is no boot. Catalina boot is ok. And is the os standard to boot. I selected it in macOS.

My problem is like yours, And waiting for a solution
12 minutes ago, Praetorianus said:

Dear AudioGod,

 

My Windows 10 is installed on another disk (ADATA ssd nvme) and Catalina on another (Samsung Evo SSD).  The clover was on the Samsung efi.  It had a normal boot on both.  I installed Opencore pure and then immediately put the bootpicker of the NDK to improve the selection interface.  The opencore, like the Clover, is in Samsung's EFI.  However, when selecting Windows 10 in the Opencore menu, it is on a black screen and there is no boot. Catalina boot is ok. And is the os standard to boot. I selected it in macOS.


Did it work before you put in NDKs bootpicker and also could you post for me a screen shot of your booter quirks for  OpenCore 0.5.7 please?

we are talking about real Oc here and not NDKs fork right?

and your talking about your own config.plist not mine I’m guessing too?


@Olas Same thing for you, using plist pro open your config.plist and goto booter, Quirks and take a screen shot and post them on here for me please?

Edited by AudioGod
10 minutes ago, AudioGod said:


Did it work before you put in NDKs bootpicker and also could you post for me a screen shot of your booter quirks for  OpenCore 0.5.7 please?

we are talking about real Oc here and not NDKs fork right?

and your talking about your own config.plist not mine I’m guessing too?


@Olas Same thing for you, using plist pro open your config.plist and goto booter, Quirks and take a screen shot and post them on here for me please?

Big Thanks Dear

Screen Shot 2020-04-10 at 11.54.37 PM.png

7 minutes ago, Olas said:

Big Thanks Dear

Screen Shot 2020-04-10 at 11.54.37 PM.png


@Olas You are missing an entry in the booter quirks so add the following.

 

EnableForAll=yes

 

it should look like this buddy and no wonder it wouldn’t boot into windows for you. 
 

1810984074_Screenshot2020-04-05at23_47_44.thumb.png.cc8fc17ed602f1b2b4ca5dd81a58c588.png
 

If you had of used my NDK OC EFI including it’s Config.plist that’s included from the start and just added your details into it then it would of worked from the very start for you.
You made a booboo dear, :poster_oops: :frantics::hysterical:

Edited by AudioGod
6 minutes ago, AudioGod said:


@Olas You are missing an entry in the  booter quirks so add the following.

 

EnableForAll=yes

 

it should look like this buddy and no wonder it wouldn’t boot into windows for you. 
 

1810984074_Screenshot2020-04-05at23_47_44.thumb.png.cc8fc17ed602f1b2b4ca5dd81a58c588.png

EnableForAll=yes

I don't have this in the list

How to but

@Praetorianus Same deal for you too fella, don’t try and use your own config.plist for OpenCore and instead use my one that’s included with my EfI but if however your using your own EFI made yourself then use the same booter quirks as I posted a post ago but if using real OpenCore do not add the EnableForAll entry as this is strictly for NDKs version only.

 

8 minutes ago, Olas said:

EnableForAll=yes

I don't have this in the list

How to but

 

Either use my config.list that’s included inside my NDK EFI and just add your details to it or send me your config.plist and I will edit it for you.

 

@Olas thinking about it you must start again and download my NDK EFI and use everything that’s inside it including the plist and go into it and just add your serial number, uuid, mlb and Rom (mac address)

the config.plist for OpenCore and for NDK OpenCore are very different and so is the ACPI and files within it.

Edited by AudioGod
1 minute ago, Olas said:

No in the list EnableForAll=yes 

could you do it for me pls


that’s not the only problem you have in the config. Many things are wrong. I have left instructions in what to do already. Instead of fighting me try it and see. 

@Olas you must start again and download my NDK EFI and use everything that’s inside it including the plist and go into it and just add your serial number, uuid, mlb and Rom (mac address)

the config.plist for OpenCore and for NDK OpenCore are very different and so is the ACPI and files within it.

 

6 minutes ago, AudioGod said:

@Olas you must start again and download my NDK EFI and use everything that’s inside it including the plist and go into it and just add your serial number, uuid, mlb and Rom (mac address)

the config.plist for OpenCore and for NDK OpenCore are very different and so is the ACPI and files within it.

and go into it and just add your serial number, uuid, mlb and Rom (mac address) is there video 

Is there a video explaining this to me?
Edited by Olas
4 minutes ago, Olas said:

I take EFI from

 

and go into it and just add your serial number, uuid, mlb and Rom (mac address) is there video 


Is there a video explaining this to me?


OMG mate for the very last time, download the correct NDK EFI for your computer and then using the already supplied config.plist just add your details to it in the following areas.

 

Using PlistEdit Pro add your details by modifying the following 

453128831_Screenshot2020-01-16at19_25_01.thumb.png.7a9beac3ccc0096941fc4a0ec07b8248.png

 

If this is too difficult for you to do then I’m confused.

Edited by AudioGod
1 minute ago, AudioGod said:


OMG mate for the very last time, download the correct NDK EFI for your computer and then using the already supplied config.plist just add your details to it in the following areas.

 

Using PlistEdit Pro add your details by modifying the following 

453128831_Screenshot2020-01-16at19_25_01.thumb.png.7a9beac3ccc0096941fc4a0ec07b8248.png

 

PLEASE NOTE - These

Thanks my dear brother 

How do I get the my serial number, uuid, mlb and Rom from my pc to put 

copy them from your OpenCore plist into the NDK plist


@Olas have you not entered any details like that ever? :hysterical:
 

what gpu do you use?

Edited by AudioGod

Seriously @Olas have you ever generated your own set of details for Catalina so you have a serial number a uuid and a MLB and placed then into OpenCore?

this is very important.

 

What GPU are you using?

Edited by AudioGod
×
×
  • Create New...