no he didnt post the same, you went and change mobo model on your own, thus it will never work. There is no certificate for your X48 mobo, but there is certificate for X58 model. This was most obvious thing, ofc i dont know this strings from top of my head, so i cant be sure if anything else is wrong with it, but at least that part is wrong for sure
So if i mod with one of those names my mod will be finished ? (via bios) or do i still need HAL if i buy a nvidia card ? and yes i know asus is the best one to use for now. 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for GIGABYTE GA EX58-UD38432-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R) 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for ASUS RAMPAGE II EXT 3287-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R) 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for ASUS P6T Deluxe 0101-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R) 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for GIGABYTE GA EX58UD4P3287-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R) 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for DFI LP UT X58 T3EH8 0101-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R) 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for MSI X58 PLATINUM 0101-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R) 987134512781Genuine NVIDIA Certified SLI Ready Motherboard for FOXCONN BLOODRAGE 3287-Copyright 2008 NVIDIA Corporation All Rights Reserved-765289891023(R)
you will still need modifyed hal or drivers for now, because enabling sli preforms 2 checks and this string is only one of them.
Well for now i stick with my HD4870, might be handy in the future if i want to use SLI with NVIDIA cards.
You can test without nvidia cards and see the result in Everest. Replace the hal.dll and modify the dsdt table (for example slistringinstaller). That's all.
Now you come to mention it..... yes! Success on my p5k and phrunt has kindly tested a maximus formula..... I will try my prized (!) maximus 2 formula soon and then release a beta. Had to shrink the RSDT and XSDT tables to create space. Then need to patch code between OEMB and HPET tables as they have hard coded ACPI offsets. I guess the registry patch may be safer for AMI, but it wouldn't be hard I don't think for nVidia to bypass that........ Watch this space Andy
Your tool works great for my Gigabyte board, the only thing i don't understand with your tool is the first attempt i get this log. When i press the go button again i get a log without those errors. Also when i check those crc32 from both files they are diffrent. Both bios files are succesfully, so why is it diffrent after the second time ??? also if i restart the program and redo it again the attempts fails again.
For the main module to grow in the SSV3 method it inserts random bytes in the early padding..... as these bytes are random the compressibility alters each time... sometimes it overshoots and starts again.... with different random bytes. It always starts with the same random seed (0) when the program is loaded... just for some reproducibility to help me with bugfixing. Don't worry..... the logs are fine and expected behaviour. Andy
there is not big risk involved if someone did it before you (and aperantly it was tested on maximus formula), just standard "flash bios" risk that is minimal anyway. Otherwise you use that utility like for standard slic, it adds asus sli certificate automaticaly, im sure eventualy there will be some switches to turn it on/off and pick other brands as well.