Windows 8 7989 OEM Information

Discussion in 'Windows 8' started by Skylined, Jul 19, 2011.

  1. Skylined

    Skylined MDL Member

    Nov 10, 2008
    150
    18
    10
    I installed 7989 on my Sony Vaio and I noticed in the Computer properties page that the oem information was in fact set to a Hewlett Packard Business Notebook.

    I changed it to my liking in the registry
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation

    Did anyone else notice this?

    PS: There was also a file in my C:\ directory called "OSBOM.txt"
    This was some of the text inside of this file...

    System Information report written at: 05/17/11 23:08:54
    System Name: WIN-KH0OJCNHJ3H
    [System Summary]

    ItemValue
    OS NameMicrosoft Windows 7 Ultimate
    Version6.2.7989 Build 7989
    Other OS Description Not Available
    OS ManufacturerMicrosoft Corporation
    System NameWIN-KH0OJCNHJ3H
    System ManufacturerHewlett-Packard
    System ModelHP ProBook 6555b
    System Typex64-based PC
    ProcessorAMD Phenom(tm) II N830 Triple-Core Processor, 2100 Mhz, 3 Core(s), 3 Logical Processor(s)
    BIOS Version/DateHewlett-Packard 68DTM Ver. B.41, 7/9/2010
    SMBIOS Version2.6
    Windows DirectoryC:\Windows
    System DirectoryC:\Windows\system32
    Boot Device\Device\HarddiskVolume1
    LocaleUnited States
    Hardware Abstraction LayerVersion = "6.2.7989.0"
    User NameWIN-KH0OJCNHJ3H\Administrator
    Time ZonePacific Daylight Time
    Installed Physical Memory (RAM)2.00 GB
    Total Physical Memory1.74 GB
    Available Physical Memory1.33 GB
    Total Virtual Memory3.48 GB
    Available Virtual Memory3.02 GB
    Page File Space1.74 GB
    Page FileC:\pagefile.sys
    Hyper-V - VM Monitor Mode ExtensionsYes
    Hyper-V - Second Level Address Translation ExtensionsYes
    Hyper-V - Virtualization Enabled in FirmwareNo
    Hyper-V - Data Execution ProtectionYes
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. ODY123

    ODY123 MDL Expert

    Apr 20, 2011
    1,164
    181
    60
  3. Skylined

    Skylined MDL Member

    Nov 10, 2008
    150
    18
    10
    this is no problem, i already got rid of the unnecessary stuff
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Nawzil

    Nawzil MDL Guru

    Jun 18, 2011
    2,206
    787
    90
    So this build was leaked by HP???
     
  5. ODY123

    ODY123 MDL Expert

    Apr 20, 2011
    1,164
    181
    60
    You didn't even know that?
     
  6. Nawzil

    Nawzil MDL Guru

    Jun 18, 2011
    2,206
    787
    90
    No, because I am using 7955.
     
  7. Skylined

    Skylined MDL Member

    Nov 10, 2008
    150
    18
    10
    So here is a quick question, how are they able to make an installation image using the file from their drive...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. ODY123

    ODY123 MDL Expert

    Apr 20, 2011
    1,164
    181
    60
    How is 7955 running now? Did you get rid of the timebomb?
     
  9. Nawzil

    Nawzil MDL Guru

    Jun 18, 2011
    2,206
    787
    90
    No, it restarts every 2 hours. But its ok until next x86 leak.
     
  10. ODY123

    ODY123 MDL Expert

    Apr 20, 2011
    1,164
    181
    60
    You can mount it using the ISO(ultraISO or others) utility, or write it to DVD then install...
     
  11. Shenj

    Shenj MDL Expert

    Aug 12, 2010
    1,557
    652
    60
    Or you could use EasyBCD to add a ISO entry in bios ^^, allows you to install your windows from your own hard disk

    (i do not recommend installing this sh*t leak on a hdd)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. Skylined

    Skylined MDL Member

    Nov 10, 2008
    150
    18
    10
    no i mean how to they (HP/Microsoft) make a Windows 8 installation image or a .wim file from their hard disk...?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Skylined

    Skylined MDL Member

    Nov 10, 2008
    150
    18
    10
    Been running 7989 for a few weeks now as primary OS and no problems...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. ODY123

    ODY123 MDL Expert

    Apr 20, 2011
    1,164
    181
    60
    #14 ODY123, Jul 19, 2011
    Last edited: Jul 19, 2011
    Ok, there was a misunderstanding. I think some experts like Stannieman can answer your questions.
     
  15. Skylined

    Skylined MDL Member

    Nov 10, 2008
    150
    18
    10
    no problem
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. mdtauk

    mdtauk MDL Junior Member

    Mar 17, 2011
    51
    5
    0
    OEM "images" are made by OEMs by installing Windows 7, 8 etc, customising it on a copy of the machine they are distributing it with, and then imaging it from the HDDs for the repair/restore disc
     
  17. fafhrd

    fafhrd MDL Junior Member

    Mar 2, 2010
    66
    59
    0
    #17 fafhrd, Jul 20, 2011
    Last edited by a moderator: Apr 20, 2017
    Using Imagex.exe.

    If the PC containing the Win8 installation is booted from a WINPE CD or from a different windows installation on the same machine but not on drive C: in the example given, the install.wim is created using the following command or similar.

    Code:
    imagex /capture c: n:\wim\install.wim "win8" /verify
    This captures and verifies an image of drive c: to drive n:\wim\install.wim (This could be a network share for instance). Takes about 30 min for me.

    You can also dispense with the installation dvd.iso file and use imagex to directly apply the image to either a formatted vhd or a fresh formatted partition.

    The syntax is:

    Code:
    imagex /apply n:\wim\install.wim 1 c:

    The command applies the image number 1 in the install.wim in that location to the c: drive of the target machine.

    If you have an installation DVD already in the D: drive, you can use:

    Code:
    imagex /apply d:\sources\install.wim 1 c:
    It takes less than 10 minutes and then following a couple of reboots, you get to the localization, OOBE login and PKID screens - up and running in about 30 minutes from issuing the imagex /apply command

    (Acer Aspire 7520 AMD 64 Athlon X2 TK57 1.90GHz 2.25GB RAM )
     
  18. spion

    spion MDL Member

    Mar 27, 2010
    136
    92
    10