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

    iqbalpnr MDL Novice

    Jan 21, 2012
    26
    15
    0

    run this "bat file" on same Compaq lap and four resultant "txt files" send to me
     

    Attached Files:

  2. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    #1222 The_Guardian, Jul 2, 2012
    Last edited: Jul 3, 2012
    @ iqbalpnr

    Here ya go.....I see one shows compaq but looks like others show hpqoem type....i know hp owns compaq now and that is the reason for confusion I think....seems like it uses a hp cert also instead of compaq...not sure but looks that way. Anyways here ya go and thank you for quick response.
    Thanks to Tito and the creator of modded bios, I now am running slic 2.1. ;)

    What if I did this....WMIC COMPUTERSYSTEM GET MODEL at begining of :BIOS section or just in :branding part of script?
    This pulls up "Compaq Presario C700 Notebook PC"
    If I do that at the begining will it mess up the others listed there for other oem machines to activate?
    I know you have it in a certain order.
    Also concerned about which cert it would use then....hp or compaq for activation (if it chooses the correct one....).
    This is a lil confusing. lol
     

    Attached Files:

  3. urie

    urie retired mod

    May 21, 2007
    8,996
    3,380
    300
    Whole point has anyone asked Searchengine, I know few members were working with him but now are releasing their version based on his original code with alterations o_O
     
  4. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    #1224 The_Guardian, Jul 2, 2012
    Last edited: Jul 2, 2012
    I have tried to contact him but cannot message on here....maybe he has setting turned off I dont know. I was tring to ask him about the Display.exe but hoping he will look at this thread and post a reply. I did modify mine to suite my needs but give credit to orig poster (searchengine) and to iqbalpnr for his rewrite for faster install. I think it is always right to give credit to those involved. Just my opinion.

    as far as the alt......I would hope he would be happy seeing ppl involved in working any bugs out. That is all we are tring to do.....no disrepect intended by anyone I dont think at least not by me.
     
  5. 589661

    589661 MDL Novice

    Feb 6, 2011
    18
    4
    0
    download link no longer working.
     
  6. iqbalpnr

    iqbalpnr MDL Novice

    Jan 21, 2012
    26
    15
    0
  7. iqbalpnr

    iqbalpnr MDL Novice

    Jan 21, 2012
    26
    15
    0
  8. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    @ iqbalpnr
    my wife says thank you.....she will have her lappy back today. lol Thanks for solution. Will report if any issue's. Have a good day.
     
  9. iqbalpnr

    iqbalpnr MDL Novice

    Jan 21, 2012
    26
    15
    0
    download again , small simplification is there
     
  10. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    #1232 The_Guardian, Jul 4, 2012
    Last edited: Jul 5, 2012
    @ iqbalpnr

    update: I have came to the conclusion that I cannot oem activate a compaq lappy for everything I have tried has failed. If a manufacture has two names like HP that owns Compaq will have issues....I dont know if other are the same as this situation (levano/ibm) or not. I will just use loader for my wifes lappy. Thanks for trying anyways.
    For testing purposes...I have been testing in vmware with bios patched for Compaq and I have changed names of all hp and hppro certs to Compact3 one at a time testing and none work for activation. I even removed the loader portion of script to check oem activation only.

    I even downloaded all updated certs and bins that I found here and none will work with the oobe.cmd on any Compaq or Compaq bios patch for vmware. Not good. :(
    Going to try orig by searchengine and see if his works....and it activated and choose the correct background theme and info. iqbalpnr you might want to look at your script real closely to see where the failure happened. Just passing on the info from my personal testing.
     
  11. iqbalpnr

    iqbalpnr MDL Novice

    Jan 21, 2012
    26
    15
    0
    #1233 iqbalpnr, Jul 5, 2012
    Last edited: Jul 5, 2012
    as per you given results

    WMIC CSPRODUCT GET VENDOR = Hewlett-Packard
    WMIC COMPUTERSYSTEM GET MANUFACTURER = Hewlett-Packard
    WMIC BASEBOARD GET MANUFACTURER = Hewlett-Packard
    WMIC BIOS GET VERSION = HPQOEM - 1



    i think your bios modded with hp . install latest original bios from Compaq site & use my oobe.cmd

    i have got many successful results from Compaq & hp users, so check yourself
     
  12. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    #1234 The_Guardian, Jul 5, 2012
    Last edited: Jul 6, 2012
    Had some time and found the answer...I have a compaq presario c700 notebook pc and if you just use these..
    WMIC CSPRODUCT GET VENDOR = Hewlett-Packard
    WMIC COMPUTERSYSTEM GET MANUFACTURER = Hewlett-Packard
    WMIC BASEBOARD GET MANUFACTURER = Hewlett-Packard
    WMIC BIOS GET VERSION = HPQOEM - 1

    Bios get version I put first to goto sharecheck where you will see below. This is for my case only....I feel other c700 series may have some issues too. Not all have same bios.....for c7** F.35 mod will work but on others like myself it didnt (F.34 worked for me). c700 series has alot of variety in them so some differ from others. You have to use something like this to get correct cert and branding because of HP/Compaq machines....
    2>NUL WMIC BIOS GET VERSION | findstr /I "%%j" >nul
    %INL% SET MAN=%%i&goto :SHARECHECK
    has to be first or will fail....also...
    2>NUL WMIC CSPRODUCT GET VENDOR | findstr /I "Hewlett-Packard" >nul
    %INL% SET MAN=COMPAQ&goto :FOUNDMAN
    2>NUL WMIC COMPUTERSYSTEM GET MANUFACTURER | findstr /I "Hewlett-Packard" >nul
    %INL% SET MAN=COMPAQ&goto :FOUNDMAN
    added and edited these lines to correctly pick Compaq for HPQOEM only. This has been tricky! lol All is well now in my world. lol Tested on wifes lappy. Ya really cant test the shared oems in vmware.....too much variety.
     
  13. iqbalpnr

    iqbalpnr MDL Novice

    Jan 21, 2012
    26
    15
    0
  14. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    #1236 The_Guardian, Jul 6, 2012
    Last edited: Jul 6, 2012
    I am using F.34 modded bios which has and checked for slic 2.1. Do I delete the "HP=HEWLETT Hewlett-P Hewlett-Packard" and replace it with "COMPAQ=HEWLETT Hewlett-P Hewlett-Packard" and it should work...correct? Will test this evening when I get home. Take care.

    ok doesnt pick compaq.....it picks hp and installs hp cert and theme info.....not activated of course....I am done testing this in my wifes lappy....I have it working from orig poster so that is all that counts. This can only be tested in real life not in vmware or anything like it. My bios is a mixture of hp and only model says compaq and this is the reason for the error. It needs to pick compaq cert to match the bios.
    If...COMPAQ=HEWLETT Hewlett-P Hewlett-Packard....would work if it picked up compaq which it does not. Maybe...HP=Compaq but that would error on hp machine then. Like I said....this is tricky.
    If bios = hpqoem then hpqoem = compaq would work but need to add that back to oobe.cmd which you have no reference to in your oobe.cmd or bios.ini file which is probably the issue from what I see. hpqoem needs to be included for hp/compaq oem activation if not it will always pick hp cert and theme info then fail activation of course for we need compaq cert and theme info.
     
  15. Klomar

    Klomar MDL Junior Member

    Jun 10, 2012
    62
    12
    0
    try changing this line:
    IF EXIST "%windir%\Setup\scripts\keys.ini" FOR /F "TOKENS=1,2,3,4 DELIMS=|" %%a in ('TYPE "%windir%\Setup\scripts\keys.ini" ^| FINDSTR /I "%%WINVER%%" ^| FINDSTR /I "%%EDITION%%" ^| FINDSTR /I "%%MAN%%"') DO %INL% SET PIDKEY=%%d

    in iqbalpnr's last oobe.cmd with these lines:

    IF EXIST "%windir%\Setup\scripts\keys.ini" (
    cd /d "%windir%\Setup\scripts\" >nul
    for /f "tokens=1,2,3,4 delims=|" %%a in ('type keys.ini ^| findstr /I "%%EDITION%%" ^| findstr /I "%%MAN%%"') do (
    echo %%a | findstr /I "%WINVER%" >nul
    %INL% SET PIDKEY=%%d
    )
    )

    i had the same problem with a compaq mini but with this solution it seems to work good.
     
  16. Klomar

    Klomar MDL Junior Member

    Jun 10, 2012
    62
    12
    0
  17. searchengine

    searchengine Guest

    #1239 searchengine, Jul 11, 2012
    Last edited by a moderator: Jul 18, 2012
    (OP)
    Re. recent $oem$|OOBE.cmd Edit Posts

    OOBE.cmd
    move scanning order under ':BIOS' section, remove ':SHARECHECK' and wonder why system installs with wrong brand theme etc... maybe scanned WMIC CSPRODUCT and didn't find 'Compaq', but found 'HP', so set MAN=HP and no ':SHARECHECK' but if it had bothered with ':SHARECHECK', it might have found 'Compaq' under WMIC COMPUTERSYSTEM etc... and then if 'ACRYSYS' found, just set MAN=ACER without sharecheck, too bad if it should really be eMachines, Gateway, or PBell... the good part is you save maybe 50 lines on the OOBE.cmd.

    MENU
    The main purpose of the project was to 'automatically and silently' determine and apply appropriate OEM branding etc (without user input). I see no benefit to having a pop-up menu during install that asks the user to choose the same options that can be applied using the included 'Custom_Theme_[readme].txt'. A menu that had a 'GUI' look that offered user fuller options, and reported system details, and slic version if detected (2.1 or 2.0) etc... may be of some interest.

    I have no plans to update this project.
     
  18. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,803
    90
    I used yours (searchengine) because of my wifes lappy which is a compaq which is hp owned activated correctly but with other custom versions it failed. I thank you for all the work put into this project and wonder if you know why display.exe fails on vista? Been hoping to ask you that if I seen you online. lol Thanks again!