reboot and check SLIC with Slictoolkit or with RW-Everything (upload RWE report or Slictoolkit's screens (Basic and Advanced tabs))
I'm soooo lost!!! Trying to get GA-Z87M-D3H to work... unsuccessfully I usually refrain from asking... hard headed... I like to find the solution my self by reading and what not... but after a few hrs trying to make sense of this (I've previously successfully modded Asus and MSI mbs) I give up and am now asking your help! Before I get into the hows and whats, here is a description of the MB i'm trying to mod: Manuf: Gigabyte Model name: Z87M-D3H Bios version: F9 Bios date: 2014-20-01 Bios ID: 8A02AG0A OS: Windows 7 pro (fresh copy) 1st hic I ran into was the fact that Gigabyte on their website identifies the Bios type as AMI... but the AMITOOL 1.63 doesn't see the original bios taken from the Gigabyte website as an AMI (file name Z87MD3H.F9 from the .exe extraction). Same deal if I try the AWARDTOOL, not an Award type. The phoenix SLIC mod v1.42 is able to read the original Bios file and IDs it as a EFI / Insyde BIOS I thus followed the instructions found here: (mydigitallife.net/threads/13358-How-to-Use-New-Phoenix-Bios-Mod-Tool-to-Modify-Phoenix-Dell-Insyde-EFI-Bios-Files). 1) Put original Bios (Z87MD3H.F9) ==> works 2) chose a Slic file (tried with each Gigabyte file under the Gigabyte folder and the 2.1/gigabyte folder (ex: GBT.BIN, Gigabyte[GBT-GBTUACPI-MSFT]2.1.BIN, etc...) 3) chose the RW file as dictated by the link mentionned earlier (ACCESS-ACP Tables ==> AcpiTbls.rw) 4) chose a certificate and verified it, the verification says it matches 5) Method used SSV2 when i hit "go" i get an error stating that "unable to add slic code". when i hit the "verify" i get "Error 5 - Specified argument was out of the range of valid values. Parameter name: index". Anyone know how I can achieve to have SLIC 2.1 integrated into my bios so i can put an OEM version of windows 7 pro. Big thanks in advance, and forgive any "noobness" on my part.
recent BIOS updates for Asus Z170 mobos state that "Modified OA key function in legacy OS" does this mean Legacy+MBR install no longer give XS/RSDT!=? any success case?