Hey guys
all attempts and tricks to "add" a Windows 10 installation on an SSD in PCIe slot#2 (APRICORN VEL-SOLO-X2 in PCIe 2.0 x16) in my 2008 Mac Pro 3.1 (OS 10.11.6) have failed so far. Eventually I also had to bury my hopes that the relocation of the PCIe drives usually marked as "external" (regardless of whether SSD or NVME) to "internal" using "Innie.kext" would fix this problem and allow a Windows installation.
Of course, the problem does not exist in the SATA2 slots. A 10.11.6 / Windows 10 SSD installed here in one of the SATA slots was clearly recognized in the PCIe slot, 10.11.6 deliberately starts quickly, Windows, on the other hand, boots very briefly and then evaporates in Angel's share - nothing to be done.
The enormous speed advantage in the PCIe slot makes all MacOS, including the patched High Sierra/Mojave/Catalina, a real pleasure - only Windows doesn't want to keep up.
Maybe you have an idea, a solution for this very annoying circumstance ?!
Thank you and best regards
Manfred
all attempts and tricks to "add" a Windows 10 installation on an SSD in PCIe slot#2 (APRICORN VEL-SOLO-X2 in PCIe 2.0 x16) in my 2008 Mac Pro 3.1 (OS 10.11.6) have failed so far. Eventually I also had to bury my hopes that the relocation of the PCIe drives usually marked as "external" (regardless of whether SSD or NVME) to "internal" using "Innie.kext" would fix this problem and allow a Windows installation.
Of course, the problem does not exist in the SATA2 slots. A 10.11.6 / Windows 10 SSD installed here in one of the SATA slots was clearly recognized in the PCIe slot, 10.11.6 deliberately starts quickly, Windows, on the other hand, boots very briefly and then evaporates in Angel's share - nothing to be done.
The enormous speed advantage in the PCIe slot makes all MacOS, including the patched High Sierra/Mojave/Catalina, a real pleasure - only Windows doesn't want to keep up.
Maybe you have an idea, a solution for this very annoying circumstance ?!
Thank you and best regards
Manfred