Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
What is the error?
Screen Shot 2020-03-28 at 02.09.59.png



btw it is the disk that I am using partially with Catalina , I did the vdml code with partitions extension.
 
Downloaded latest Microsoft link Still same error , is it something with pcie ssd or being partitioned?
I have an existing Windows UEFI installed on an NVME PCIE drive. I used the same guide to attach the NVME drive and I am currently in a process of upgrading Windows to the latest version as I could not upgrade it in a normal way. It is still in a process of installing, but I have managed to use it in the VirtualBox.
 
I have an existing Windows UEFI installed on an NVME PCIE drive. I used the same guide to attach the NVME drive and I am currently in a process of upgrading Windows to the latest version as I could not upgrade it in a normal way. It is still in a process of installing, but I have managed to use it in the VirtualBox.

did you use Pcie ssd for 2 OSes or just for Windows?



also the disk0 is seeing like that. there is a missing partition there. I will try to erase all disk and stall Catalina again.

Screen Shot 2020-03-28 at 03.31.35.png
 
did you use Pcie ssd for 2 OSes or just for Windows?



also the disk0 is seeing like that. there is a missing partition there. I will try to erase all disk and stall Catalina again.

View attachment 901823
No Windows is installed on a separate drive. I have not tested it with Windows+OSX on the same drive yet:
Code:
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                                                   *512.1 GB   disk2
This is my NVME currently in use by Virtualbox.
Code:
/dev/disk7 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *250.0 GB   disk7
   1:                        EFI EFI                     209.7 MB   disk7s1
   2:         Microsoft Reserved                         16.8 MB    disk7s2
   3:       Microsoft Basic Data                         249.8 GB   disk7s3
This is an internal SATA where I installed Win10 from Virtualbox.
 
No Windows is installed on a separate drive. I have not tested it with Windows+OSX on the same drive yet:
Code:
/dev/disk2 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: *512.1 GB disk2
This is my NVME currently in use by Virtualbox.
Code:
/dev/disk7 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *250.0 GB disk7
1: EFI EFI 209.7 MB disk7s1
2: Microsoft Reserved 16.8 MB disk7s2
3: Microsoft Basic Data 249.8 GB disk7s3
This is an internal SATA where I installed Win10 from Virtualbox.

All the problem here is being on pcie ssd. I was able to install OSx and windows 10 on the same drive but that was a sata ssd. On pcie nvme is problem with windows. Will turn back to dedicated sata ssd for windows. Thanks for helpin me. I will edit if i got any other conclusion about the process
 
roobarb!
How will my GTX680 (Has Apple Boot Screen) react with rEFInd?
Any issues, does Option Key still work in the normal way with Apple Boot Screen from my GPU?
Thanks for any info.
 
View attachment 901801
Just adjust drivers to your taste NdkBootPicker.efi (requires folder "icons") or OpenCanopy.efi (requires "Resources" folder). NdkBootPicker.efi is more mature than OpenCanopy.efi at the time of writing.
[automerge]1585349582[/automerge]

Just delete the partition and click Next.
bootscreen picker.jpeg

Hello, finally got it to work. Between which graphics did you use when you did the test? The only graphics I was able to get the BootPicker with was an Nvidia GT120 512MB without touching the keyboard. The picker came on its own.

So far I did not get anything with; RX580 Sapphire 8GB; GTX6804GB; GTX7704GB; RE Radeon VII. Black screen stayed space bar hit or not.

Thanks again...
 
Last edited:
I have a question - I've not read all 68 pages so apologies if this is already covered.

I have a MacPro 4,1 SC upgraded to 5.1 with a 6 Core XEON upgrade (forget the exact processor).

I have a clean Mojave HD setup

I have Catalina running on an internal PCI Mounted NVMe SSD - I used VMWare to install this and update to 10.15.2 but cannot use the VMWare route to update it any further - get a processor exception when I start up the VM

I am considering going down the OpenCore route. I've built a Hack' using Opencore and I think I understand the fundamentals. I am strangely cautious about using it on a real Mac.

Lets call the Mojave Disk B and the SSD A. Can I simply mount the existing EFI for A and overwrite it with Opencore as per post 1 of this thread, assume I need to do the recovery mode bless etc... whilst still maintaining the installed Catalina on the SSD then reboot the whole setup using Opencore instead of the apple EFI?

If that works I assume I can then just switch on VMM when I want to update to 10.15.4 do the update in place and the switch it off when I am done?
 
  • Like
Reactions: dabotsonline
Can I simply mount the existing EFI for A and overwrite it with Opencore as per post 1 of this thread, assume I need to do the recovery mode bless etc... whilst still maintaining the installed Catalina on the SSD then reboot the whole setup using Opencore instead of the apple EFI?
You have lost me here. What are you trying to achieve again?
 
Lets call the Mojave Disk B and the SSD A. Can I simply mount the existing EFI for A and overwrite it with Opencore as per post 1 of this thread, assume I need to do the recovery mode bless etc... whilst still maintaining the installed Catalina on the SSD then reboot the whole setup using Opencore instead of the apple EFI?

If that works I assume I can then just switch on VMM when I want to update to 10.15.4 do the update in place and the switch it off when I am done?

Yes, this will work.
 
You have lost me here. What are you trying to achieve again?

Simply put I have a working install of Catalina on a NVMe SSD - can/how do I convert it to use OpenCore so that I can update it - my original update approach using VMware raw disk no longer seems to work
 
Simply put I have a working install of Catalina on a NVMe SSD - can/how do I convert it to use OpenCore so that I can update it - my original update approach using VMware raw disk no longer seems to work
I would suggest formatting a USB as a GUID FAT32 and installing opencore in it's EFI partition then blessing the BOOTX64.EFI. Use the VMM flag before blessing and you should see the update in system updates upon boot.
 
  • Like
Reactions: cannfoddr
roobarb!
How will my GTX680 (Has Apple Boot Screen) react with rEFInd?
Should be fine, I used to use rEFInd for other purposes back when I had a GTX680.

Any issues, does Option Key still work in the normal way with Apple Boot Screen from my GPU?
Yup, if it supports those early boot screens before OC starts (which the GTX680 can do) then you should still get them.
 
HI All! I would like to update to Catalina by open core method.
as read the post, there is some questions:
1. must it be clean install? Can I upgrade my current Mojave drive by this method?
2. If it cannot, Can I install a clean Catalina and migrate my data from time machine? will it brick the system?
Thanks!
 
roobarb!
Thanks for all the HELP and time you have taken to try and set me straight!
Last piece for me is:
(Pardon My Ignorance) but how do I “Bless” the Partition?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.