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. phoenix885

    phoenix885 MDL Novice

    Feb 23, 2009
    8
    0
    0
  2. urie

    urie retired mod

    May 21, 2007
    8,999
    3,381
    300
    @ AndyP just a question would it be possible to add slic identification to AMI and Award tools the same as you none in Pheonix tool i,e Manufacturer: SLP Version: OEMID: OEMTableID: and OEMCreatorID:

    Thanks
     
  3. urie

    urie retired mod

    May 21, 2007
    8,999
    3,381
    300
    @ aln688, have you ever used a loader if so i would try clean install.
     
  4. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Try 1.49
    The AMI (and Award) tools are not quite as sophisticated as the phoenix tool though.

    Andy
     
  5. urie

    urie retired mod

    May 21, 2007
    8,999
    3,381
    300
    Great work Thanks again Andy i take it when you mean not as sophisticated as pheonix tool it want grab say OEMCreatorID: MSFT for example just trying to get everything to match as much as existing bioses.
     
  6. aln688

    aln688 MDL Novice

    Feb 23, 2010
    7
    0
    0
    Nope, clean install. The Windows install I'm using now hasn't yet been activated, no loaders or softmods of any kind.

    I can't find anyone else with this problem. I haven't installed any loaders or softmods. I've tried the BIOS flash a few times now, using SSV3 and Dynamic, both results in the SLIC OEM string being the default, HPQOEM. I'll run the VOAK 2.5 tool to clean and try it again. If you've any other ideas, I'd appreciate knowing. I also have a RW-Everything dump if that would help.

    This is an Asus Rampage II Gene board, I was using BIOS 0904 but decided to upgrade to 1202, and it's the 1202 I modded with no success post-flashing. I may try one of the pre-modded BIOS's here, I think I saw 0904 somewhere. That'll eliminate my modding against some other problem.
     
  7. asmfan

    asmfan MDL Junior Member

    May 11, 2009
    72
    6
    0
    HI,
    could you please explain why OEM Table ID should be changed along with OEM ID? Do Table IDs of some tables should match to that in slic so that cert to contain proper hash? And why some table IDs are changed to that in slic and the others don't care or stay untouched? Why not to change only OEM ID?
    Why particulary these RSDT, XSDT, FACP changed while
    APIC, MCFG, AMI_OEM (table ID), HPET, OSFR - names (Table IDs) unchanged.
    So cert checking by os based also on table IDs of 3 tables not only slic inside? I understand matching by acpi OEM IDs of tables but what about table ids?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. NoJuan999

    NoJuan999 Experienced SLIC Tool Operator

    Jul 31, 2009
    9,917
    1,941
    300
  9. NoJuan999

    NoJuan999 Experienced SLIC Tool Operator

    Jul 31, 2009
    9,917
    1,941
    300
  10. Guenni007

    Guenni007 MDL Novice

    Mar 26, 2008
    28
    1
    0
    For now - yes it does not matter - but i guess that the intension of that KB 971033 is to get rid of all those loaders and Bios hacked "genuine" Win7
    And i believe that even if they want - the could not detect the dynamic method but the static i guess its possible to become aware of.
    So in my non expert mind i suspected above in my Screenshot a static comment. But i see even with the ssv a dynamic RunLoc
    My question for that is - where can i see the differences
     
  11. aln688

    aln688 MDL Novice

    Feb 23, 2010
    7
    0
    0
    Thanks NoJuan999, I'm making a package just now to post in that thread.
     
  12. aln688

    aln688 MDL Novice

    Feb 23, 2010
    7
    0
    0