Thanks ! But still the same .. I choose the dosdude catalina dmg, then repair, said it was succesfully done, but same problem. I was advised to start from scratch with Mojave .. What do you think ?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro
- Thread starter cdf
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
If your target is 10.15.7. No need to install Mojave.
Even there is no working Catalina recovery partition, you can still simply create a normal unpatched Catalina USB installer, boot to it via OpenCore, and make a clean 10.15.7 installation.
That's good news !
I'll try that ! Another challenge ; I had a working windows 10 on a ssd before installing OC, is there a way to get it working with OC or should I start from scratch ?
On the Crazy Colours, some GPUs have a physical switch that changes some display parameters.
Perhaps check whether yours does and try flipping it to see if it solves the issue.
That's good news !
How to: Boot Camp without a Boot Screen
Yes Intro : For install Win10 on cMP you need DVD bootable with Win10 and press "c" on cMP boot to start on DVD, and install Win10. Now I suppose as me you can boot on Win10 from your cMP, if not please remove all your other boot drive (Mac OS, ...) to be sure to boot only first on Win10. 1)...
forums.macrumors.com
Raaaaahhh Catalina updates installed (10.15.7) then I tried Reset NVRAM to get windows 10 drive showing in OC, and now I got blackscreen and shutdownHow to: Boot Camp without a Boot Screen
Yes Intro : For install Win10 on cMP you need DVD bootable with Win10 and press "c" on cMP boot to start on DVD, and install Win10. Now I suppose as me you can boot on Win10 from your cMP, if not please remove all your other boot drive (Mac OS, ...) to be sure to boot only first on Win10. 1)...
EDIT: Did NVRAM reset 3 times in a row, now OC back !
Last edited:
VMM is needed for Catalina updates. It is currently not needed for installing Big Sur.
With my method, it does not matter where it is.
Sorry, don’t know what you have done wrong. I got into some problems with things not working the first time. I started from scratch again and followed the instructions on page 1 and got it working.
If it is bootable, you will see it in System Preferences > Startup Disk. If it is there, choose it.
It appears you misidentified your disks. As mentioned in the guide:
The formatting or renaming of the EFI folder probably killed your macOS or OpenCore installation, so upon rebooting, your Mac shut off (a well-known behavior).
Replying to myself. If the above command is pasted in a single line "\" before "if" has to be omitted:
Code:
u=$(nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:boot-path | sed 's/.*GPT,\([^,]*\),.*/\1/'); if [ "$u" != "" ]; then sudo diskutil mount $u ; fi
Volume EFI on 25EADBC0-3BDE-48EF-840E-0D46566CBC46 mountedHi thanks for the reply, although I am not sure what you mean.... or where I went wrong following your guide.
If it is ok with you I am going to post that part of your guide and what I did so you can quickly see where I screwed up
Prepare two disks as follows:
Disk C should not be the same as Disk A. The volume of the USB disk will be referred to as USB.
* I did this, so going into this windows installation I had:
Add the exFat driver - Completed this step on Disk A with no issues
<string>ExFatDxeLegacy.efi</string>
to the array
Also, make sure that the VMM flag is off.
Verify the configuration - Completed this step on Disk Home folder on Disk B with no issues
Load the configuration - Completed this step on Disk A with no issues
Use the actual volumes names in the following step:
So when following the above instruction I entered into Terminal exactly was:
Proceed with the installation
The Windows installer should start.
Note the actual volume numbers and letters. Do not proceed if you are not sure! Replace the actual volume number of Disk C in the following step.
First time I hard powered down the CMP (I had forgotten to plug in a wired mouse so couldn't exit any other way), I then went through all the steps in the guide again.
Screenshots are from my second attempt that is why for the "ren efi efi.bak" command you see the "duplicate file name..." response.
Both Attempts ran into the "Error 126" response. For the second attempt I had realized I needed a wired mouse and "X'd" out and rebooted properly.... which then killed the reboot.
| Disk C | USB |
|---|---|
| Newly formatted exFat volume (GUID scheme) | Newly formatted exFat volume (MBR scheme) |
| This is where Windows will go | This is where the installer will go |
Disk C should not be the same as Disk A. The volume of the USB disk will be referred to as USB.
* I did this, so going into this windows installation I had:
- Disk A - "MacOS" - Where I had OpenCore and Catalina
- Disk B - "Macintosh HD" - Mojave / Recovery and where I configured OpenCore and this windows install
- Disk C - "Windows" - Newly Formatted exFat Vol (GUID) - where windows will go
- USB - "Installer" - External SSD Formatted exFat Vol where Installer would go
Add the exFat driver - Completed this step on Disk A with no issues
- Open Terminal
- Find the EFI volume of Disk A by entering: diskutil list
- Mount the EFI volume by entering: sudo diskutil mount /dev/diskAs1
- Copy OcBinaryData/Drivers/ExFatDxeLegacy.efi to EFI/OC/Drivers
- Navigate to /Volumes/EFI/EFI/OC and copy config.plist to your home folder
- Open config.plist in your home folder with TextEdit
- Find the Drivers key and add
<string>ExFatDxeLegacy.efi</string>
to the array
Also, make sure that the VMM flag is off.
Verify the configuration - Completed this step on Disk Home folder on Disk B with no issues
- Close config.plist
- In Terminal, enter: plutil -convert xml1 config.plist && plutil config.plist
Load the configuration - Completed this step on Disk A with no issues
- Copy config.plist back to /Volumes/EFI/EFI/OC
- Reboot
Use the actual volumes names in the following step:
- Enter: rsync -r /Volumes/CCCOMA_X64/ /Volumes/USB
- Windows ISO I downloaded was Windows 10 64bit
- Reading the instruction above I decided to mount the ISO and it showed on desktop of Disk B as "CCCOMA_X64FRE_EN-US_DV9"
So when following the above instruction I entered into Terminal exactly was:
- rsync -r /Volumes/CCCOMA_X64FRE_EN-US_DV9/ /Volumes/Installer
Proceed with the installation
- Reboot and select Windows (External) from the boot picker
The Windows installer should start.
- At the Windows Setup window, press Shift+F10 to open the Command Prompt - Completed
- Start diskpart by entering: diskpart - Completed
- Identify your disks by entering: list volume - Completed
Volume 1 C Disk C exFAT - Yes but replace "Disk C" with "Windows"
Volume 2 D USB exFAT - Yes but replace "USB" with "Installer"
Note the actual volume numbers and letters. Do not proceed if you are not sure! Replace the actual volume number of Disk C in the following step.
- Select Disk C by entering: select volume 1 - Yes, for me Disk C or "Windows" was the C: and was Volume 1
- Format the disk by entering: format quick fs=ntfs label=Windows - Yes, I did exactly this
- Enter: exit - Completed
- Enter: D: - Completed
- Backup the efi folder of the installer by entering: ren efi efi.bak - Completed
- Enter: cd sources - Completed
- Identify the version of Windows that you want to install by entering: dism /get-wiminfo /wimfile:install.wim
- This is where I ran into the error 126
- "An error occurred. DISM could not initialized in the local folder. Ensure DISM is installed correctly and all binaries are present"
First time I hard powered down the CMP (I had forgotten to plug in a wired mouse so couldn't exit any other way), I then went through all the steps in the guide again.
Screenshots are from my second attempt that is why for the "ren efi efi.bak" command you see the "duplicate file name..." response.
Both Attempts ran into the "Error 126" response. For the second attempt I had realized I needed a wired mouse and "X'd" out and rebooted properly.... which then killed the reboot.
So that's my run through of my doomed Windows install attempt. Hopefully I made it robust but concise enough for one of you helpful folks to quickly run through what I did and point to what I did wrong and importantly what I should do.
Thanks in Advance for any help provided
Also I am very hopeful one of you will be able to help me resolve the windows install by finding my error and showing me how to correct it. I strongly prefer to have this whole solution by following the guide on this thread, far less messy
In case I am not able to resolve the issue above using the Windows installation method in this guide, I did also see this other guide on these forums: https://forums.macrumors.com/threads/bare-metal-windows-on-cmp.2250317/
In case I am not able to resolve the issue above using the Windows installation method in this guide, I did also see this other guide on these forums: https://forums.macrumors.com/threads/bare-metal-windows-on-cmp.2250317/
- Is this other method compatible with the OpenCore setup I completed following this CDF guide?
- If it is compatible, that guide references installing windows in Legacy or UEFI. Which should I do for best compatibility with the OpenCore setup I successfully completed in this guide?
- Lastly are there any inherent issues following this Windows install? In my reading I heard about Boot Coups and other System Bricking dangers for some methods of Windows on CMP installs and if this is one of those then I probably won't chance it.
@RottenCotton
OpenCore can’t boot legacy Windows (Boot Camp), but only UEFI Windows. I can’t really provide any first-hand knowledge on how to get UEFI Windows set up. I tried once (not following the guide in post #1), but it failed badly. I currently run legacy Windows from the Startup Disk Manager, before OpenCore has a chance to control the boot process. I have a hunch, however, that reversible, successful conversion between legacy and UEFI Windows is achievable by simply using Winclone 9. If my hunch is correct, you can simply install Windows in legacy mode. Then, once it is set up and works as you wish, you can simply use Winclone to automatically convert it to UEFI mode, after which you would use OpenCore to start it up.
OpenCore can’t boot legacy Windows (Boot Camp), but only UEFI Windows. I can’t really provide any first-hand knowledge on how to get UEFI Windows set up. I tried once (not following the guide in post #1), but it failed badly. I currently run legacy Windows from the Startup Disk Manager, before OpenCore has a chance to control the boot process. I have a hunch, however, that reversible, successful conversion between legacy and UEFI Windows is achievable by simply using Winclone 9. If my hunch is correct, you can simply install Windows in legacy mode. Then, once it is set up and works as you wish, you can simply use Winclone to automatically convert it to UEFI mode, after which you would use OpenCore to start it up.
OpenCore on the Mac Pro
No VMM only firmware features and firmware mask from iMacPro1,1 (and board-id)
forums.macrumors.com
Thanks!
OpenCore on the Mac Pro
No VMM only firmware features and firmware mask from iMacPro1,1 (and board-id)
Just updated Big Sur with OC 0.6.3 without VMM. I just use h9826790 package, the first reboot will creat a macintosh HD for update no matter what is your main disk name. For second boot, it return to my default drive and it should boot inside OS, my monitor run at full resolution and loupdeck show normal activated. everything smooth and easy up to 11.0.1 RC. Thanks for all effort.
