2009년 10월 10일 토요일

New Award BIOS tool for performing SLIC Insertion/Modification

A new tool to perform insert a SLIC table using one of a number methods.

To find best method:
1) Search this thread - http://forums.mydigitallife.info/showthread.php?t=2967 - and use a method that has previously been proven to work on an older BIOS revision for the same board.
2) Otherwise:

- Pubkey is best for ASUS
- SSV3 is best for Gigabyte
- Try ISA or 0+2 for everything else

There is an attempt to automatically identify the manufacturer from the BIOS. Please ensure the correct BIOS manufacturer is selected from the drop down list before modding. If your manufacturer is not listed then it is safe to select Other.

Notes:
- BIOS flashing is not for the faint hearted. There is ALWAYS an element of risk. Please ensure you are familiar with the procedure, and have necessary floppy disks etc., to allow a recovery in case of a flash failure.
- We assume you have a legitimate edition of Vista. Piracy is NOT condoned.
- Please remove any softmods. For Vistalo*der this includes repairing the boot sector and MBR of the hard disk.

Flash recovery information:
- Read here - http://www.biosman.com/biosrecovery.html - note that sometimes the filename needs to be different - the boot block error message may tell you, however this does mean you need a second machine to be able to change the file name.
- Also read here - http://forums.mydigitallife.info/showthread.php?t=2105
- Ensure that the version on the disk is the (unmodified) version you are trying to flash with SLIC - avoids problems with bootblock flashing.

SLIC and SLP files - The program needs:
- A 374 byte SLIC file (ASUS included, others available from other tools and softmod archives). Checksum is automatically corrected.
- A one line text file containing the SLP string you wish to be inserted. Again, ASUS is included. See http://www.msfn.org/board/index.php?...#entry53 4097 - only the text string (without ') after the hex numbers is needed in the TXT file
- 911medic has kindly uploaded his collection of SLIC .BIN files here - http://slics.myftp.org/slic.rar.

Vista Keys and Certificates
- Keys can be found here - http://forums.mydigitallife.info/showthread.php?t=2581
- Certificates can be found here - http://rapidshare.com/files/118119842/39-CERTS.zip

XP Keys and OEMBIOS files
- Keys can be foud here - http://forums.mydigitallife.info/showthread.php?t=2602

Method
1) Flash, using the manufacturers recommended method, the unmodified BIOS of the same version. This allows the bootblock etc. to be updated.
2) Mod the BIOS using the tool
3) Flash the SLIC'd BIOS from DOS. This ensures the bootblock is left intact and maximises the chance of a successful recovery if a problem was to occur.
4) You then still need to use the appropriate key and certificate for Vista, and key and OEMBIOS files for XP.

Many thanks to Zort and P4Spooky for their invaluable advice and feedback.

There is also the ability (based on the methodology here - http://forums.mydigitallife.info/showthread.php?t=4792) to see if a certificate matches a SLIC file or the existing SLIC table in an already modded BIOS. Just click the verify button adjacent to the certificate text box after selecting a pre-SLIC'd BIOS or SLIC file. This does not need to be done to mod a BIOS, it is completely independant.

--------------------------

Latest Version

1.27 - http://slics.myftp.org/Tools/Award_S...ardtool127.zip
Mirror - http://www.sendspace.com/file/4hpkhe

This is a rare error in versions prior to v1.22 that may leave the main module checksum uncorrected and may brick.

ADD: Experimental support for DSDT modification - insert SLI certificate
ADD: Experimental support for DSDT modification - remove CPU Aliases (for Mac OSX)

FIX: Improve DSDT prompts (now warns if ISA/Pubkey selected that DSDT is NOT modified)
FIX: Options display in log incorporates new options

For more information about the DSDT modification (for SLI) see - http://forums.mydigitallife.info/sho...d.php?p=151297

Note - DSDT modification options are not enabled by default and can be found in the advanced options. You will be warned prior to modification if you are going to alter the DSDT table.

Note - as ISA and pubkey methods don't alter the ACPI table they won't alter the DSDT table

Note - sometimes 0+2 will fail as the main module cannot be shrunk enough to compensate for the increase in ACPITBL size, best bet is SSV3 or OEM7 with ACPITBL at end.

댓글 없음:

댓글 쓰기