[DISCUSSION] VirtualBox - Update, SLP & SLIC

Discussion in 'Virtualization' started by cigolo_, Dec 30, 2008.

  1. kelorgo

    kelorgo MDL Addicted

    Oct 29, 2012
    839
    1,506
    30
  2. nerd.brazil

    nerd.brazil MDL Novice

    Feb 5, 2014
    11
    0
    0
    Shhh... It's for a good cause... yes, I am checking out Phoenix in VMware because it's a full-fledge BIOS and much can be learned from there... but I'll keep any discussions here strictly VirtualBox.

     
  3. nerd.brazil

    nerd.brazil MDL Novice

    Feb 5, 2014
    11
    0
    0
    It just dawned on me... is it possible to use Windows 7 - XP Mode .vhd file with HP SLP string and OEMBIOS file?? Along the same lines, is it possible to use the Retail version of Windows 7 (as found for download at Digital River) and install HP SLIC / OEM Cert / SLP Key?

    I was under the assumption that if I had HP OEM OS disks, I had to use HP SLIC/CERT and SLP KEY. In this case, Windows 7 XP Mode had to use the Windows_Virtual_XP_F9161D8E7FCC11DDBFAA369856D89593 at offset 0x908A...

     
  4. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    18,682
    18,582
    340
  5. kelorgo

    kelorgo MDL Addicted

    Oct 29, 2012
    839
    1,506
    30
    #525 kelorgo, Apr 2, 2014
    Last edited by a moderator: Apr 20, 2017
    Yes, and you don't even need to mod the VirtualBox BIOS. For HP, you can just add the SLP string to the DMI area. See section 9.12 in the VirtualBox manual. Example:
    Code:
    VBoxManage setextradata "VM name" "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor" "System Vendor"
    Yes, and again, you don't need to mod the VirtualBox BIOS. You can add the SLIC as a custom ACPI table. See section 9.13 in the VirtualBox manual. Example:
    Code:
    VBoxManage setextradata "VM name" "VBoxInternal/Devices/acpi/0/Config/CustomTable" "/path/to/table.bin"
    Now you know better ;)

    VirtualBox is much easier than VMware when it comes to doing SLP 1.x - 2.x, as usually no BIOS modding is needed.
     
  6. nerd.brazil

    nerd.brazil MDL Novice

    Feb 5, 2014
    11
    0
    0
    #526 nerd.brazil, Apr 5, 2014
    Last edited by a moderator: Apr 20, 2017
    In order to use the VBoxManage command below, do I have to pick an OEMBIOS set which includes segment 0xE000 for the SLP string? That is, use set #2 below instead of set #1? From disassembling the BIOS, I believe that VirtualBox's DMI area is located at segment 0xE000. Is that correct?

    #1
    HP (OEMBIOS.CAT CRC32=06D652A4)
    f000,0000,ffff,HP PAVILION

    #2
    HP (OEMBIOS.CAT CRC32=3BA155E1)
    f000,0000,ffff,Hewlett-Packard
    e000,0000,ffff,Hewlett-Packard

    Thanks!

     
  7. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    6,316
    7,023
    210
  8. Jeff_59

    Jeff_59 MDL Novice

    Apr 29, 2014
    5
    0
    0
    Hello:)

    I'm unsure if i'm posting in the right section.

    [So please feel free to move my post if necessary]

    Although i managed to activate an existing windows xp in virtualbox (virtual hard drive obtained by migration using a P2V tool, with the
    modify virtualbox bios containing the manufacturer string, thanks to this method: archive.today/JP5ku and dmidecode settings thanks to commands like "vboxmanage setextradata"), i'm unable to preactivate in the same way and with the same parameters a fresh xp install from a multi OEM windows XP DVD.

    Does anyone know why?

    Regards,

    Jeff.

    P.S.:The dvd seems to work great since i'm able a activate the physical OEM PC.
     
  9. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    6,316
    7,023
    210
    #530 Carlos Detweiller, Jul 16, 2014
    Last edited: Feb 13, 2020
    Unfortunately I cannot use the 4.3.14 build at all (100% reproducibility).
    View attachment 29871

    That's the error I get every time I want to start 4.3.14. Please note that 4.3.12 installs and starts without the slightest problem, it must be something build-specific.

    Please don't suggest posting in the VB forum, I won't feed Oracle my data required for their SSO.
     
  10. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    6,316
    7,023
    210
    Deleting registry key doesn't work for me. Back to 4.3.12, currently.
     
  11. user_hidden

    user_hidden MDL Expert

    Dec 18, 2007
    1,034
    1,061
    60
    I have absolutely no issues with 4.3.14 running on Win8.1/x64
     
  12. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    6,316
    7,023
    210
    Has to do with certain antivirus- and other security products. Personally, Comodo and avast!
     
  13. ailin

    ailin MDL Novice

    Nov 9, 2012
    9
    14
    0
    XP Mode VirtualBox 4.3.16 patch

    Hi ALL!

    There are patched versions of VirtualBox 4.3.16 BIOS for Windows XP Mode (SLP activation) available.
    The BIOS code was recompiled as for version 4.3.8.
    As usual two modules available: pcbios.bin and VBoxDD2.dll.

    Link: sendspace [dot] com/file/ok3j4p
     
  14. LostED

    LostED SVF Patch Lover

    Jul 30, 2009
    7,145
    21,024
    240
    #537 LostED, Sep 27, 2014
    Last edited by a moderator: Apr 20, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. ericgl

    ericgl MDL Senior Member

    Mar 10, 2011
    250
    189
    10
    ailin / LostED,

    Could you guys give me a small reminder on how to use the patch?
    It's been a long time since I've used it, and I seem to have misplaced my "install notes".

    Thanks!
     
  16. ailin

    ailin MDL Novice

    Nov 9, 2012
    9
    14
    0
    #539 ailin, Sep 28, 2014
    Last edited by a moderator: Apr 20, 2017
    ericgl

    There are two ways of using this patch: simple and complex.
    1. Simple way. Replace VBoxDD2.dll in VirtualBox installation directory and all VM's with Windows XP Mode should be activated after reboot.

    2. Complex way. Makes possible to enable SLP BIOS only for certain VM.
    Run next commands (CMD) replacing values:
    <virtualbox_install_dir>: directory where VirtualBox in installed
    VM name: name of virtual machine which settings should be adjusted (note that name should be quoted)
    path_to_pcbios: path to pcbios.bin file (should be quoted)

    Code:
    CD <virtualbox_install_dir>
    VBoxManage setextradata "VM name" "VBoxInternal/Devices/pcbios/0/Config/BiosRom" "path_to_pcbios"
     
  17. RickT

    RickT MDL Novice

    Oct 2, 2014
    2
    0
    0
    Hi,

    I've just upgraded to 4.3.16 (I was running a very old version 4.2.0 before) and replaced VBoxDD2.dll, but it doesn't work for me, in fact the VM doesn't even start. It creates the initial window, and then aborts almost immediately with the following error:
    I've tried it with 2 different XPMode VMs I have and they both do the same. :sad:

    Replacing VBoxDD2.DLL with the original allows the VMs to boot but when I log in it then tells me I must activate them to continue (as expected).

    I tried uninstalling 4.3.16 then re-installing and it does the same thing. I've now uninstalled and re-installed 4.2.0 and installed the patched version of VBoxDD2.dll I was using before and I'm back in business again.

    Have I missed out something?

    EDIT: Host OS is Windows 7 Ultimate 64bit