cheers for the replies guys. unfortunately that method is slightly different to what i wanted to do. little backstory- we have a database of dsdt.aml files from gigabyte which have been patched for use with osx. we are trying to do the same with asus 1155. however, with these asus 1155 insyde roms, i cant find a way to get at the dsdt.dsl. all the methods ive found online have either been for award bioses, or older ami bios. we need to get the dsdt from the actual rom, rather than on an individual board level. phoenixtool has a way to do it i believe, i just cant work out how
If ASUS, most likely they use AMI UEFI. If true then DSDT should be in 11D8AC35-FB8A-44D1-8D09-0B5606D321B9_X_XXX.ROM. DSDT file start with "DSDT". So, delete anything before "DSDT".
To serg008 Thanks your advice. I do the bios with your advice. I find, in H61MHVS Bios, Pubkey rom, Marker rom and 'SLIC' string rom are existing and paired with each other. In your mod bios, "Pubkey found in 996AA1E0-1E8C-4F36-B519-A170A206FC14_0_504.ROM at 4" and "Marker found in 69009842-63F2-43DB-964B-EFAD1C39EC85_0_502.ROM at 4" are extra and no needed and don't match / pair wth 'SLIC' string found in 4C494E55-5849-5342-4554-544552212121_1_326.ROM Thus, I use the method : Dyn (advance option - replace emptly + allow mannual modi module) + HEX (modi the 996AA1E0) and reinsert into the dump. ***the method is fully tested and confirmed working slic *** nel1156
To Andy Thanks for your great program and advice form Serg008. I find as follows : When origin M/B bios (Asrock H67M, H61M) have only one 'SLIC' string rom + NO / NIL Pubkey rom 996AA1E0 + NO / NIL Marker rom found in 69009842 The program works correctly by producing the correct mod bios. (tested with H67M and confirm working) When origin M/B bios ( Asrock H61MHVS, MSI H61P31 ) have ALL 3 ROMS, program seems know how to modify Marker rom and 'SLIC' string rom. But program seems DOESN'T know the need to modify the existing blank Pubkey rom 996AA1E0-XX.... Thus, following the Serg008's advice, when using ver 1.95, I suggest (which I fully tested and confirm working) that when origin M/B bios ( H61MHVS, H61P31 ) have ALL 3 ROMS ==> click advance - replace empty module + allow user modi + manually reinsert HEX modify the original rom 996AA1E0-1E8C-4F36-B519-A170A206FC14_0_XXX in dump ==> then let program continue assembly the UEFI bios. ==> will produce the correct rom. Besides, the program prompts the bios successfully mod that seems doesn't the check the above case (all exiting / blank 3 roms in UEFI bios). Thanks Andy's program and advice form serg008. nel1156
From Consumer 8 Product Guide Enhanced end-to-end security features From power-on to power-off, Windows 8 offers features that improve the security and reliability of the systems in your organization. From power-on to power-off, Windows 8 provides a more secure foundation to help keep your businesses running. Trusted boot process The Windows 8 boot process is signed and measured, helping to protect the PC from malware or viruses. Secure Boot validates the integrity of the entire boot process, including the hardware, boot loader, kernel, boot-related system files, and drivers. Antimalware is loaded in advance of all non-critical Windows components. This means that malware, such as rootkits, are less able to hijack the boot process, or hide from antimalware software. On appropriately configured platforms supporting the UEFI 2.3.1, firmware authenticates Windows boot components to help prevent any attempt to start malware before the operating system is up and running. If a component is not corr ectly signed by Microsoft, the operating system starts the Windows Recovery Environment (Windows RE) to automatically reinstall properly signed operating system components. Measured boot process On Trusted Platform Module (TPM)-based systems, Windows 8 can perform a comprehensive chain of measurements during the boot process that can be used to further validate the boot process beyond Secure Boot. Measured boot process enables all aspects of the boot process to be measured, signed, and stored in a Trusted Platform Module (TPM) chip. This information can be evaluated by a remote service to further validate a computer’s integrity. This process is called attestation. With strong checks to ensure that operating system components are kept safe, malware and other types of malicious software have much less of a chance taking over a PC than ever before.
Andy - Have you looked to see why the RW-Everything reports from v1.5.x cause problems? Is it something with parsing the 64-bit memory addresses?
Hi Andy, I used the 1.96 to modify d830 A16 bios with slic 2.1 but when you try to flash it, the .exe created doesn't work.
Andy Thanks for your follow up. But, for Asrock H61MHVS bios ver1.6 OR MSI H61 P31 which has 3 empty roms, the new 1.96 program NEED to go to ADVANCE and click REPLACE EMPTY MODULE, the program will give the correct UEFI bios with correct SLIC. Unlike 1.95, the manually HEX modded rom for Pubkey is needed to insert and replace the empty Pubkey rom. If use program 1.96 by default, it will output the wrong moded UEFI bios. nel1156