VMware BIOS and try to apply to my Vmware Fusion 5

Discussion in 'Virtualization' started by jiemin, Jul 3, 2013.

  1. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
  2. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,681
    18,589
    340
    #44 Tito, Jul 7, 2013
    Last edited by a moderator: Apr 20, 2017
    @bigfoot15

    From his MGADIAG report:
    Code:
    OEM Activation 1.0 Data-->
    BIOS string matches: N/A
    Marker string from BIOS: N/A, hr = 0x8007007a
    Marker string from OEMBIOS.DAT: TOSHIBA
    
    OEMBIOS files are intact & functional but bios has no SLP string. It seems that he confuses something and edited wrong VM.

    :eek:
     
  3. bigfoot15

    bigfoot15 MDL Member

    Jul 22, 2009
    102
    222
    10
    I just tried MGADIAG on my VMware WK9 and it shows the same thing as his. I know mine is working correctly. Must be a bug in the MGAdiag.
     
  4. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
    #46 urie, Jul 7, 2013
    Last edited by a moderator: Apr 20, 2017
    yes same here.
    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-MC4VM-QY6XY-R38TB
    Windows Product Key Hash: NejBPSIaVI2Pvbhwzbcr7VceLkU=
    Windows Product ID: 76487-OEM-2211906-02960
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.2.0.pro
    ID: {C6A7635D-7387-4B80-80AB-2A06B298E2B5}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.40.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A
    
    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A
    
    Windows XP Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    Version: 1.9.40.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft
    
    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002
    
    OGA Data-->
    Office Status: 109 N/A
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-543-80070002_025D1FF3-230-1
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed
    
    File Scan Data-->
    
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{C6A7635D-7387-4B80-80AB-2A06B298E2B5}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.2.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-R38TB</PKey><PID>76487-OEM-2211906-02960</PID><PIDType>2</PIDType><SID>S-1-5-21-117609710-152049171-839522115</SID><SYSTEM><Manufacturer>VMware, Inc.</Manufacturer><Model>VMware Virtual Platform</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>6.00</Version><SMBIOSVersion major="2" minor="4"/><Date>20120702000000.000000+000</Date><SLPBIOS>Dell System,Dell Computer,Dell System,Dell System</SLPBIOS></BIOS><HWID>39FD3C870184167F</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/></GANotification></MachineData>  <Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  
    
    Licensing Data-->
    N/A
    
    Windows Activation Technologies-->
    N/A
    
    HWID Data-->
    N/A
    
    OEM Activation 1.0 Data-->
    BIOS string matches: N/A
    Marker string from BIOS: N/A, hr = 0x8007007a
    Marker string from OEMBIOS.DAT: Dell System,Dell Computer,Dell System,Dell System
    
    OEM Activation 2.0 Data-->
    N/A
     
  5. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
    #47 urie, Jul 7, 2013
    Last edited by a moderator: Apr 20, 2017
    Looks like he does have SLP
    Code:
    <SLPBIOS>TOSHIBA</SLPBIOS></BIOS>
    whereas I have
    Code:
    <SLPBIOS>Dell System,Dell Computer,Dell System,Dell System</SLPBIOS></BIOS>
     
  6. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
  7. user_hidden

    user_hidden MDL Expert

    Dec 18, 2007
    1,034
    1,061
    60
    ridiculous that jieman's issue has taken up 5 pages of this thread !
     
  8. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
    Yes so what at least other users are trying to help if you have any useful input on how to solve the problem then lets hear it.
     
  9. jiemin

    jiemin MDL Novice

    Jul 3, 2013
    33
    3
    0
    No matter whether the issue solved or not eventually, it is the most warmhearted forum I've ever been, really appreciate your guys giving the assistance :) /jiemin
     
  10. user_hidden

    user_hidden MDL Expert

    Dec 18, 2007
    1,034
    1,061
    60
    Urie don't get me wrong, it is that the issue at this point should have it's own thread as it has taken over the topic.
    Jieman is running on Fusion(OSX) not Workstation(Win), and therefore has nothing to do with the VmwareMegaBiosPack tool.

    never-the-less SLP activation should be simple and straight forward.
    1- his bios seems to have slp
    2- install correct bios files under an OEM XP
    3- use proper OEM-SLP key
    4- activated
     
  11. user_hidden

    user_hidden MDL Expert

    Dec 18, 2007
    1,034
    1,061
    60
    hopefully your issue is just a simple oversight, i'm sure it'll get fixed
     
  12. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
    Thread Moved.
     
  13. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
    You said you downloaded OEMBIOS changer but could not download OEMBIOS files so copy the files from OEMBIOS backup Uncompressed Folder to your OEMBIOS changer Uncompressed Oembios Folder and run OEMBIOS changer i,e on xp in Fusion.
     
  14. jiemin

    jiemin MDL Novice

    Jul 3, 2013
    33
    3
    0
    Hi Gentlemen, I have run "oembios-back.cmd" and imported 4 files to the VM c:\oembioschanger\compressed oembios folder. After issue "oem.cmd", the attached screenshot pop up? Please advise which one I should choose. I believe we are close to the trophy :worthy: Screen Shot 2013-07-08 at 10.44.03 PM.png
     
  15. urie

    urie Moderator
    Staff Member

    May 21, 2007
    9,039
    3,388
    300
    Either select 1 to check for SLP string then select 5 oem bios changer is what you want to do.
     
  16. bigfoot15

    bigfoot15 MDL Member

    Jul 22, 2009
    102
    222
    10