Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project

Discussion in 'MDL Projects and Applications' started by searchengine, Jan 30, 2010.

Thread Status:
Not open for further replies.
  1. fox85

    fox85 MDL Novice

    Dec 8, 2012
    8
    0
    0
    #1481 fox85, Dec 9, 2012
    Last edited: Dec 9, 2012
    hi guys,
    i have a problem...
    My mobo (z77 asrock extreme4) had not the slic 2.1, so i've modded the bios with ASUS SLIC 2.1 and now work correctly; infact slic_toolkit confirm it.
    I have put the $OEM$ folder in the "sources" directory and then i've create the bootable DVD for the preactivation.
    when i installed windows 7 with this DVD, i see that windows don't installed the ASUS certificate and key, infact the license works only for 3 days.
    Also all the OEM'S imagine (wallpaper, background, etc.) are not the ASUS, as my new modded bios, but the BEKO/GRUNDIG...:confused:

    Can you help me?

    P.S sorry for my english :p
     
  2. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    Run the $oem$ pre check tool included in the download package......then post detailed results. Helps the creator of this project pin point the issue.
     
  3. fox85

    fox85 MDL Novice

    Dec 8, 2012
    8
    0
    0
  4. fox85

    fox85 MDL Novice

    Dec 8, 2012
    8
    0
    0
    Can you help me, please? :biggrin:
     
  5. urie

    urie retired mod

    May 21, 2007
    8,996
    3,380
    300
    Try Daz loader it will install correct certificate but it won't install the loader because you have slic2.1 in bios. Not sure if it the way the script is detecting manufacturer. As you can see the pre check tool detects mines correctly
     
  6. fox85

    fox85 MDL Novice

    Dec 8, 2012
    8
    0
    0
    Infact it seems that the script can not detect my constructor. Perhaps the problem is that the manufacturer of my motherboard is ASROCK while the BIOS SLIC 2.1 is ASUS. Could this be the reason?
     
  7. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    Looks to me if the filtering part of script isnt filtering correctly with your custom board....should find ASUS from bios but doesnt. Will let the creator handle this from here for he knows his script. Sorry I couldnt help more but he is the one to talk to.
     
  8. urie

    urie retired mod

    May 21, 2007
    8,996
    3,380
    300
    ASRock is a spin off of ASUS the problem is it is detecting yours as BEKO. For the moment that is not your problem you just want to activate your machine as I said try Daz loader see if it detects it as ASUS
     
  9. fox85

    fox85 MDL Novice

    Dec 8, 2012
    8
    0
    0
    #1489 fox85, Dec 9, 2012
    Last edited: Dec 9, 2012
    I just tried to manually install the key and certificate (both ASUS) and now w7 is active and genuine.

    So the problem only occurs when I add the $OEM$ folder on the W7 installer DVD.

    One more thing;
    The ASUS certificate that I installed manually I haven't take from the $oem$\$$\Setup\scripts\Certificates directory, but from "OEMCERT_AND_SLICS_2012-11-20" package because the first didn't work, while that in "OEMCERT_AND_SLICS_2012-11-20" work well and active my W7.

    Should not be the same the two certificates?
     
  10. urie

    urie retired mod

    May 21, 2007
    8,996
    3,380
    300
    Those are from the same place one is probably for vista i,e, slic 2.0 other for windows 7 slic2.1 as I said it would be trying to install BEKO and it would not have been accepted.
     
  11. fox85

    fox85 MDL Novice

    Dec 8, 2012
    8
    0
    0
    ok, thank you.
     
  12. searchengine

    searchengine Guest

    #1492 searchengine, Dec 14, 2012
    Last edited by a moderator: Dec 16, 2012
    (OP)
  13. searchengine

    searchengine Guest

    #1494 searchengine, Dec 15, 2012
    Last edited by a moderator: Dec 15, 2012
    (OP)
    @urie...

    Any user who experiences incorrect identification of manufacturer should post 'Results.txt' (as above image).

    Entries that cause incorrect identification such as 'To Be Filled By O.E.M.' can be by-passed to allow correct identification.

    ie. above example by-passes 1st, 2nd, 4th, 5th outputs, and uses 6th output for theme, and 7th for activation.

    Another example of incorrect identification posts #1367 to #1373...

    'System Product Name' and 'System manufacturer' caused identification problems.

    Thus outputs 'To Be Filled By O.E.M.', 'System Product Name' & 'System manufacturer' can be filtered|by-passed via oobe.cmd to
    overcome reported identification conflicts.
     
  14. Tito

    Tito Admin / Adviser
    Staff Member

    Nov 30, 2009
    19,004
    19,680
    340
    Exactly... I think most of the ASUS and ASRock engineers are just lazy to put that info on their desktop mobos.

    ;) :D
     
  15. searchengine

    searchengine Guest

    1st page updated...

    1st December 2012 (project update)
    • project suitable for Win7 • Vista (specified editions)
    • updated|added 'OEM's'
    • updated|added 'certificates'
    • updated 'OOBE.cmd' script (by-pass 'reported' conflict manufacturer id's)
    • updated 'oemscan.ini'
    • updated '$oem$|assessment' tool in project folder (machine assessment tool)
     
  16. ahd_dc

    ahd_dc MDL Novice

    Mar 5, 2012
    7
    0
    0
    Thanks, but where is download link ?:confused:
     
  17. urie

    urie retired mod

    May 21, 2007
    8,996
    3,380
    300
    That would be on the First page with the KYPYk.png Image.
     
  18. Tanith

    Tanith MDL Novice

    Dec 17, 2012
    3
    0
    0
    After the enterprise installation got non genuine I tried this on HP 8530p, worked like charm, thanks.
     
  19. CalvinLim

    CalvinLim MDL Novice

    Sep 16, 2010
    2
    0
    0
    Download link 403 Forbidden???