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.
I did not set myself such a task. Here is my script, it compiles and makes binaries and libraries dynamic, signs, etc. In general, it prepares for use in my program. You can try))) I think it is necessary to register the key in configure.
 

Attachments

  • New-build-libraries.zip
    3.6 KB · Views: 13
  • Like
Reactions: startergo
I see @chris1111 has created similar Apps:
 
I created with the app in the 5,1 and put it in my 2019 Mac Pro and it booted no prob which prooves the 5,1 is the problem, the app was not the issue, it's an issue with my 5,1 and maybe the latest Windows 11 build. I can still install Windows 11 using my 2022 Rufus created thumb drive on the 5,1 and get it up to date.
Lance, can you tell me if you look at the list of hardware and drivers in windows - does everything work correctly for you? Are there about 100 incorrect drivers for internal equipment like mine? I've been following your reviews on YouTube for many years, and I make many decisions only after carefully studying the experience of many people from the Macrumors community. I thought about it for about half a year and decided that it was time to upgrade to Mac Pro 7.1 (I bought two identical 7.1 instead of my two old 4.1/5.1.)
Now it's been almost a month since I've been trying to get all the programs working correctly. I couldn't do a simple SSD transfer with Windows from a 5.1 cmp to a 7.1 smp (it only worked for me with OpenCore - I configured the OCLP). But I immediately found about 100 non-working drivers in Windows - for pci and many many others, ethernet does not work - and neither bootcamp nor brigadier helped with this huge list. After working for almost a month, I decided to try to install a new version of Windows 10 Pro on a spare disk and see if there would be a list of non-working equipment. Sergey's program is very intuitive - despite the fact that I followed the discussion for six months - while deciding to buy a Mac Pro 7.1, but I did not have the task of installing Windows, and completely setting up all the programs and licenses from scratch. Today I decided to test the installation using Sergey's program: I carefully read the chat again in full, so as not to repeat the mistakes of everyone who took part in the beta testing.
1. as I expected, despite the fact that Sergey's program prepared disk for installing Legacy windows correctly, the installation process itself did not start on the Mac Pro - nowhere in the discussion did I find in which cases it is necessary to install UEFI, and in which cases Legacy. My cmp 7.1 simply did not start the installation - it does not consider this disk bootable
2. I confirm that the installation of Windows UEFI using CMP 7.1 with the help of Sergey's program was quick and correct ( in mac settings i set completely unsafe boot of any operating systems, and set boot from external usb)
3. despite the successful new installation and installation of bootcamp drivers, I have a huge list of non-working equipment, including the non-working Ethernet

as macschrauber mentioned:
if the opencor bootloader is used, then after updating windows it registers the boot folder - and then when you press alt and the boot option appears, in addition to loading opencor, there is also a direct boot to windows - and if you mistakenly click on direct boot, then a blue screen of death appears (Before loading you need to remove extra boot)
I completely damaged my Windows system disk with this error, I had to reformat it and clone it from my old working one.
another thing I found is that in EFI on the windows disk, when there are crashes and reboots, the apple folder is somehow written. and if it is there, then I also cannot boot into windows

I can't remember now all the cases and difficulties that I experienced in the process of setting up new cMPs. But what I can state is that Sergey's program is a very good and very simple solution for attentive and careful users.
 
Last edited:
  • Like
Reactions: Sergey-Galan
1. as I expected, despite the fact that Sergey's program prepared disk for installing Legacy windows correctly, the installation process itself did not start on the Mac Pro - nowhere in the discussion did I find in which cases it is necessary to install UEFI, and in which cases Legacy. My cmp 7.1 simply did not start the installation - it does not consider this disk bootable
Regarding the first point. Legacy Windows installation is relevant for Mac Pro 4.1/5.1, old iMacs and MacBooks that do not have the OCLP bootloader installed. The firmware of these computers does not know what UEFI Windows is.
 
Last edited:
There is no need to install Legacy Windows for Mac Pro 7.1, but it is possible.
UEFI Class 3 devices do not have the Compatibility Support Module (CSM) needed for Legacy BIOS Boot.

UEFI Class 3+ devices are Class 3 devices that additionally include a TPM.
The T2 chip is effectively a TPM and the MP71 therefore appears to be a UEFI Class 3+ device.

In simple terms therefore, the MP71 does not support Legacy Windows.
It is possible to install such indeed, but the MP71 will not and can not boot it.

This is all inferred btw as Apple does not specifically publicly define device UEFI Classes.

As an aside, cMP incidentally also do not have a UEFI CSM but have an equivalent in Boot Camp.
Note that what is typically refered to as "Boot Camp" is actually an application called the "Boot Camp Assistant"
"Boot Camp" itself lives in the firmware. The "Boot Camp Asisstant" sets things up for "Boot Camp" to use.
 
Last edited:
  • Like
Reactions: Sergey-Galan
UEFI Class 3 devices do not have the Compatibility Support Module (CSM) needed for Legacy BIOS Boot.

UEFI Class 3+ devices are Class 3 devices that additionally include a TPM.
The T2 chip is effectively a TPM and the MP71 therefore appears to be a UEFI Class 3+ device.

In simple terms therefore, the MP71 does not support Legacy Windows.
It is possible to install such indeed, but the MP71 will not and can not boot it.

This is all inferred btw as Apple does not specifically publicly define device UEFI Classes.
Thanks for the information.
 
These drivers are more than enough for Windows 10:
5.1.5621
And if you want the latest and greatest drivers you can always download the drivers for iMacPro from brigadier and install any missing driver. But I did not find any missing drivers in the device manager.
I had about 100 unrecognized devices on my Mac Pro 7.1. what bootcamp gives is little things - a mouse, a keyboard and all sorts of other insignificant Apple-specific little things. Ethernet didn't work. I spent a whole week reading various forums. First, I downloaded several Intel drivers from updates - the number of errors decreased by about 60. Then I downloaded Aquantia ethernet drivers from official site. Two more errors deleted. Ethernet works. Now I have PCI Data Acquisition and Signal Processing Controller error and SM Bus Controller driver error- there are about 10 errors left
following the official intel instructions, I launched some driver installers and got a blue screen of death
so everything is very confusing here
I wanted to specifically ask the experts
should I return the original BIOS of the video card instead of the one modified by syncretic?
because when I launched the AMD diagnostics - it gave an error - it wrote that the equipment is not recognized - not the original AMD
 
His question is completely off topic. The bootcamp for Mac Pro 7.1 may need to be downloaded onto the drive though unless Win11 is installed. @Sergey-Galan is there a way to download the bootcamp drivers during the process or the user has to download them on a separate USB?
 
@Sergey-Galan is there a way to download the bootcamp drivers during the process or the user has to download them on a separate USB?
A pre-prepared flash drive with bootcamp drivers. But the problem is that not all of his devices are updated, and when he tries to install drivers from other sources, he gets a blue screen.
Controller error and SM Bus Controller driver error- there are about 10 errors left
following the official intel instructions, I launched some driver installers and got a blue screen of death
so everything is very confusing here
In order not to start all over again, make a backup after each attempt to install drivers; the program has this option.
 
  • Like
Reactions: Gustav Holdoff
My question is not off-topic, but about the procedure
during the installation Windows on cMP 7.1, the Internet and Wi-Fi did not work - since I could download Bootcamp only after installation, the installation was done offline and the drivers were installed minimally. All hardware was not tested oline and the drivers were not installed correctly. And if Wi-Fi worked after installing Bootcamp, then I searched for Ethernet and about 100 more errors for a whole week.
My post is for all regular users who use the method, so that they are warned and not surprised. Because it is obvious that on earlier models the ethernet works and wifi can be launched without bootcamp. That's why the installation goes without any surprises
 
I wanted to specifically ask the experts
should I return the original BIOS of the video card instead of the one modified by syncretic?
because when I launched the AMD diagnostics - it gave an error - it wrote that the equipment is not recognized - not the original AMD
This is the off-topic question, and that appeared to be the only question you had.
As far as the Windows Install software goes there are no specific drivers installed by that software so if some drivers don't work out of the box it is recommended to provide the Bootcamp drivers on a USB drive. Just download the drivers through the Bootcamp assistant in the macOS and copy them to a fat formatted USB drive using rsync -r dir1/ dir2.
 
  • Like
Reactions: Gustav Holdoff
This is the off-topic question, and that appeared to be the only question you had.
As far as the Windows Install software goes there are no specific drivers installed by that software so if some drivers don't work out of the box it is recommended to provide the Bootcamp drivers on a USB drive. Just download the drivers through the Bootcamp assistant in the macOS and copy them to a fat formatted USB drive using rsync -r dir1/ dir2.
I don't know if it's a topic or not, but I reverted the GPU BIOS to non-flashed, and all my errors were removed
 
if a regular user uses a syncretic patch for gpu, or opencor or oclp is installed, then you should be warned that any interference in the operating system or bootloader can lead to consequences. I am just reporting that I encountered the consequences of this interference
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.