Guide for VMware Fusion 5.0.1 SLIC 2.1 (MAC OS)

Discussion in 'Virtualization' started by Acid_Scorpion, Sep 2, 2012.

  1. Acid_Scorpion

    Acid_Scorpion MDL Novice

    Apr 11, 2010
    2
    1
    0
    #1 Acid_Scorpion, Sep 2, 2012
    Last edited: Sep 3, 2012
    Short step-by-step manual. It's also suitable, if you have no any Windows machine near. Please note, that this is guide for users, which already has experience in Windows activation:

    - Download and install VMware Fusion
    - Copy /Applications/VMware Fusion.app/Contents/Library/vmware-vmx to somewhere. I recommend to ~/Downloads.
    ("~" means your home directory)

    - Open terminal window and run:
    $ segedit vmware-vmx -extract __VMWARE bios440 bios440.rom
    (Personally, I don't like embedded terminal program and using iTem2)

    This will extract BIOS rom file from vmware-vmx and save it as bios440.rom, on which we will apply a SLIC patch.

    - Now, you need any Windows machine. You can also install virtual Windows machine, using your VMware Fusion

    - Install latest "Andy's Phoenix BIOS tool"
    (sorry, can't post URL, use "Forum search")

    - Install latest "RW-Everything" to get AcpiTbls.rw
    (The same thing, use "Forum search")

    - After You'll get patched bios440.rom from Windows machine, put it somewhere on your Mac. I recommend to ~/Documents
    (If you using virtual Windows machine, then I recommend to use "shared folder" for quick file exchange - Virtual Machine - Sharing - Sharing Settigs)

    - Now, You can create and install virtual Windows machine, if you haven't did it before.

    - After installation, You should shutdown your Windows virtual machine

    - Locate .vmx file of you Windows virtual machine. Usually it's in ~/Documents/...
    - Open .vmx file and put in the end:
    bios440.filename = "/path/to/your/patched/bios440.rom/file"
    (example: bios440.filename = "/Users/acid/Documents/bios440.rom")

    - Now, your virtual machine has correct BIOS for activation

    - Run your virtual machine and make usual procedure for certificate (.xrm-ms) installation and activation.

    Good luck! :)
     
  2. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,792
    1,737
    180
    Can segedit insert the resources back into executable?

    External BIOS is not as "elegant" (still works fine)

    sebus
     
  3. Kouryu

    Kouryu MDL Senior Member

    Jan 19, 2011
    408
    111
    10
    I prefer external bios... it's more elegant to me, the executable remains untouched, therefore all guests stay modular... you can choose to have a patched BIOS or not for each guest, or different SLIC for each guest
     
  4. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,792
    1,737
    180
    Thanks for expressing your opinion & NOT answering the question!
     
  5. Kouryu

    Kouryu MDL Senior Member

    Jan 19, 2011
    408
    111
    10
    just a response to your opinion that external bios isn't elegant :)
     
  6. Sean_93

    Sean_93 MDL Novice

    Nov 19, 2012
    1
    0
    0
    Thanks for the information, i am trying to activate an instance of XP for VMWare on a Dell D830, is there any chance you could give me more information on how to use the tools such as Andy's BIOS tool, and RW Everywhere as googling the subject has left me very confused.

    Thanks in advance.
     
  7. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,792
    1,737
    180
    Just pick up ready BIOS from here
     
  8. IlDavo

    IlDavo MDL Novice

    Jan 5, 2013
    1
    0
    0
    More Info Requested: How to Use Andy's Tool, RW-Everything, etc.?

    Seconding:

     
  9. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,792
    1,737
    180
    #9 sebus, Feb 20, 2013
    Last edited by a moderator: Apr 20, 2017
    @ IlDavo

    SLIC has nothing do do it XP, you need modded BIOS with SLP
    In your case most likely Hewlett-Packard string (you can always check it with oembios tool - available in XP section)

    Code:
    $ segedit vmware-vmx -replace __VMWARE bios440 361H_asus21.rom -output vmware-vmx-slic
    
    segedit: can't replace section (__VMWARE,bios440) in: vmware-vmx because it requires relocation
    segedit: unknown load command 5 (result maybe bad)
    segedit: current limitation, can't process files with LC_DYSYMTAB load command as in: vmware-vmx
    
    So it seems that it is not easy to do the replacement...
     
  10. benhadad

    benhadad MDL Novice

    Mar 6, 2013
    20
    3
    0
    #10 benhadad, Nov 17, 2014
    Last edited by a moderator: Apr 20, 2017
    I just did this with VMware 7.0, I was using the older bios and I was having some driver problems so I figured starting over with a new bios would work better. I followed the process exactly and it worked. Some things for new ones to note.

    1. It is easier in my case to find the actual file vmware-vmx and copy it to a easy to locate drive as the tutorial suggests. I have seen other tutorials that have you do the extraction in place and I had problems with that.

    2. Once you have the extracted bios you copy it to a windows machine. This should be a windows machine running on the Vmware Fusion your BIOS came from. This means you have to install a copy (normally MS gives you 2 days to activate). Then on that windows machine ( I could be incorrect about this) you use RW-Everthing to extract the AcpiTbls.rw. It has the option to extract 1 table or all tables the option for save all gives you I believe this AcpiTbls.rw. I am assuming this is correct as it is the process for other vmware versions (http://forums.mydigitallife.net/thr...staller/page76?p=647522&viewfull=1#post647522)

    3.Downloaded Andys tool. IT ask for the location of the extracted bios, and the Acpitbls.rw and spit out a BIOS_440_SLIC.ROM as a result.

    4. I copied this back to my mac mini and opened the VMX file for the Virtual machine and added the line bios440.filename="BIOS_440_SLIC.ROM". [Actually i had to enter the location of the file as I placed it inside the VM package so it looked more like bios440.filename="/Volumes/Windows/VM/Windows 7x64.vmwarevm/./BIOS_440_SLIC.ROM" ] I tried the straight reference and it didnt work for me.

    The windows 7 machine bios works fine.

    On a side note I still have an issue with a unknown "Base System Device" showing up in windows Device manager. I figured out that due to lack of USB 3.0 support in windows 7, I was getting an unknown usb device before. I had to change usb compatibility for the VM to USB 2.0 and that issue went away. I also change hardware compatibility to version 10 since I might want to transfere this machine to an ESXi 5.5 system.

    Hope this is of some help...