New AMI BIOS tool for performing SSV2/3 and Dynamic SLIC Modification

Discussion in 'MDL Projects and Applications' started by andyp, Jan 7, 2009.

  1. kocoman

    kocoman MDL Senior Member

    May 16, 2007
    366
    7
    10
  2. domatlapuk

    domatlapuk MDL Expert

    Sep 12, 2009
    1,060
    16
    60
    Hi Andy or everyone,
    Can you upload the new version of the tools on rapidshare or hotfile, megaupload or any ftp links, coz mediafire and sendspace are currently blacklisted in china.. Thanks...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Interesting. Up to 20000h is blanked. NVRAM is after AMIBIOSC string.

    Try an SSV2 mod, tick use alternate method, tick manual address and use 3B800h. You may need to tick to allow in NVRAM also.

    Andy
     
  4. anonim1979

    anonim1979 MDL Novice

    Oct 12, 2009
    5
    0
    0
    I'm the kind of guy that like to check what is inside his new toy ;)

    M-board was fairly low cost, used one. Also I have practice in hot swaping BIOSes from Pentium I / K5 era :D

    Anyway the main reason was to test "how possibly dangerous the procedure is" - to know what to look for if I ever had to play with high cost/hard to fix mobos in laptops and/or soldered BIOS.

    PS.
    I'm willing to test "highly" experimental BIOS for that Asrock KT880 - I will make a backup for hot swap first :)
     
  5. kocoman

    kocoman MDL Senior Member

    May 16, 2007
    366
    7
    10
    I run your tool in XP. it does not complain about the 02 error if I turn off the use NVRAM, but I get 02 error when I turn it on?
    But I get another error (both check nvram or no nvram)

    Also I think its better if you put on "Page 1" of this thread that the .NET 2.0 is needed. I downloaded 1.1 but it say it need 2.0, then I download 3.5 via the Windows Update (there was no 2.0 in Windows update for some reason)

    Log

    Original BIOS size 262144 bytes (256K)
    30FC3 Module 2 Padded size 28699 (Actual size 28699 Original size 40464)
    308AD Module 8 Padded size 1802
    2CBCC Module 0 Padded size 15573 (Actual size 15573 Original size 19632)
    294E0 Module 3 Padded size 14048 (Actual size 14048 Original size 20598)
    2728B Module 4 Padded size 8777 (Actual size 8777 Original size 13928)
    25554 Module 1 Padded size 7467 (Actual size 7467 Original size 11940)
    24E79 Module 6 Padded size 1743
    1AA74 Module A Padded size 41977 (Actual size 41977 Original size 65536)
    15D8E Module D Padded size 19674 (Actual size 19674 Original size 26815)
    15AF1 Module F Padded size 657 (Actual size 657 Original size 49911)
    148F3 Module 10 Padded size 4594 (Actual size 4594 Original size 12510)
    13F2F Module 12 Padded size 2488 (Actual size 2488 Original size 2916)
    13556 Module 13 Padded size 2509 (Actual size 2509 Original size 3193)
    C542 Module 11 Padded size 28680
    C358 Module 32 Padded size 478 (Actual size 478 Original size 735)
    C344 Module C Padded size 8
    C1F8 Module 31 Padded size 320 (Actual size 320 Original size 470)
    9C75 Module 20 Padded size 9591 (Actual size 9591 Original size 16384)
    9C35 Module 50 Padded size 52
    9BEF Module 51 Padded size 58
    8AE3 Module 52 Padded size 4352 (Actual size 4352 Original size 10259)
    8954 Module 3B Padded size 387
    No extended headers
    Bootblock at 3C000 length 4000
    NVRAM at 38000 length 4000
    Main BIOS checksum is correct
    Dell Computer SLP 1.0 string added
    Module 02 written 40464 bytes
    Module 02 written
    New 02 Module is 11 bytes too big
    Zero area 1
    Module 02 written
    New 02 Module is 62 bytes too small
    Module 02 written
    New 02 Module is 45 bytes too small
    Module 02 written
    New 02 Module is 31 bytes too small
    Module 02 written
    New 02 Module is 22 bytes too small
    Module 02 written
    New 02 Module is 15 bytes too small
    Module 02 written
    New 02 Module is 9 bytes too small
    Module 02 written
    New 02 Module is 5 bytes too small
    Module 02 written
    New 02 Module is 8 bytes too small
    Module 02 written
    New 02 Module is 4 bytes too small
    Module 02 written
    New 02 Module is 5 bytes too small
    Module 02 written
    New 02 Module is 3 bytes too small
    Module 02 written
    New 02 Module is 2 bytes too small
    Module 02 written
    New 02 Module is 1 bytes too small
    Module 02 written
    New 02 Module is 1 bytes too small
    Module 02 written
    New 02 Module is correct size
    Successfully inserted 02 module containing SLP1.0 string (SSV2 style)
    0F module size is 49911 bytes
    SLIC module size is 374 bytes
    SLIC module checksum is 0
    OEM Activation 2.1 SLIC
    Scanning for space to insert SLIC
    There is space to insert SLIC in ROM image at 10
    Override to insert SLIC in ROM image at 3B800
    The offset specified is too close to (or beyond) the end of the image


    thanks
     
  6. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Fixed in 1.40

    Try same options as before, SSV2, alternate method, allow in NVRAM, manual address of 3B800.

    Third time lucky ;)

    Andy
     
  7. kocoman

    kocoman MDL Senior Member

    May 16, 2007
    366
    7
    10
    The 1.40 app works fine in XP, but not in Win7 (even if I set ie: C:\a - without any long filenames) - still get the "failed to extract 02.."

    But thats not a big problem, I still have xp machine I can use.

    So I flashed the patched bios (no more 'no space error', but still SLIC table not found (reported by Slic Dump toolkit) :(

    I compared the dumps, and there is a bit of difference..

    Comparing files dump.bin and DUMP2
    000F42F1: B5 AA
    000F42F2: 42 84
    000F42F3: 25 4A
    000F42F4: 12 25
    000F42F5: B9 72
    000F42F6: 56 AD
    000F42F7: C5 8A
    ...etc

    Is the 3B800 wrong or nvram problem? How can I diagnose it..

    thanks
     
  8. Flipp3r

    Flipp3r MDL Guru

    Feb 11, 2009
    2,008
    957
    90
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Thanks.

    Is it win7 x64 by chance.... the AMIMM tool needed in not win32. I can write this out but it would be a fair bit of work..... and as core 6/7 are old....

    Looking at the dump the area at 3b800 is overwritten with FF. I don't think this is doable...... there is no free space that is not overwritten..... the only other (very risky) option might be to put the SLIC table in the bootblock......... I could do this if you wanted to try but the risk would be high!

    Andy

     
  10. Flipp3r

    Flipp3r MDL Guru

    Feb 11, 2009
    2,008
    957
    90
    Thanks again Andy, that's worked!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Michel

    Michel MDL Expert

    Jul 29, 2009
    1,860
    262
    60
    Try slic dump tool kit 2.1
     
  12. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Nice one! Thanks for letting me know.
    Andy
     
  13. Chen

    Chen Guest

    thanks but i have it, is the same prob, test it on a 3 pc all the same.
     
  14. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    The real test is whether it activates XP..... does it?

    Andy
     
  15. domatlapuk

    domatlapuk MDL Expert

    Sep 12, 2009
    1,060
    16
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...