Author: Fa1lson
Subject: [Z68 Extreme4] HD7850 -> RX480 upgrade woes
Posted: 22 Feb 2017 at 11:55am
Yes indeed.
I used an old spare HDD to successfully install win10, but will of course reinstall on SSD if I decide to accept win10 as my OS. But I had a fun old time getting the UEFI-prefixed entry to appear in the boot order. What ended up working was inserting a win7 install disk in my BD-ROM. With the freshly-burned win10 disc in the drive I actually got the 'no monitor signal' problem again, and had to clear CMOS data. With the drive empty, no amount of rebooting would persuade the UEFI prefix to appear. Weird, and glad I could work around it.
I want this to be the case so very much (as I have no interest in win10 aside from its support for the new card's DirectX 12 ability). But as mentioned in first post, Dr. Debug status code AE ('Legacy boot event') results when I attempt to boot my old win7 install. Am I missing something? I do hope so!
Subject: [Z68 Extreme4] HD7850 -> RX480 upgrade woes
Posted: 22 Feb 2017 at 11:55am
 parsec wrote:About updating the UEFI, just to check, you have the Z68 Extreme4, not the Z68 Extreme4 Gen3 board, correct? |
Yes indeed.
| Forgot to tell you some mandatory UEFI installation techniques that even Windows 10 will require. In case you aren't aware of this... Whatever Win 10 installation media you use, before the installation starts check the boot order and find the installation media. It should be the only other drive connected to (or powered up) in the PC besides the target OS drive. You should find an entry for the Win 10 installation media that looks something like this: "UEFI: <installation media name>". You need to select the boot order entry with the "UEFI:" prefix, which causes a UEFI booting Windows installation. Not sure if you are using an HDD or an SSD as the Windows 10 drive. I assume the SSD. No idea if any or all HDDs support using the EFI boot loader. |
I used an old spare HDD to successfully install win10, but will of course reinstall on SSD if I decide to accept win10 as my OS. But I had a fun old time getting the UEFI-prefixed entry to appear in the boot order. What ended up working was inserting a win7 install disk in my BD-ROM. With the freshly-burned win10 disc in the drive I actually got the 'no monitor signal' problem again, and had to clear CMOS data. With the drive empty, no amount of rebooting would persuade the UEFI prefix to appear. Weird, and glad I could work around it.
| If you are fine with using the Legacy ROM setting, then there is no reason to install Windows again, unless you simply want to use Windows 10. |
I want this to be the case so very much (as I have no interest in win10 aside from its support for the new card's DirectX 12 ability). But as mentioned in first post, Dr. Debug status code AE ('Legacy boot event') results when I attempt to boot my old win7 install. Am I missing something? I do hope so!
