pantagruel, Thanks for the explanation and the method to confirm that all is OK. What about all those files in the VM BIOS mega-pack though? For example, in one folder there are files named 361H_dell_e2_21.rom, 361H_dell_inv_21.rom, and 361H_dell_qa09_21.rom, just to name a few. How does one know which hardware platforms these correspond to?
These refer to modded VMware BIOSes which can only be run in VMware. To date, all the Vmware Mega Bios Packs are based on older versions of VMware, and are outdated. The file name refers to the VMware bios version, the SLIC, and the SLIC version. Using the same convention 361H_dell_pesc3_22.rom (VMware bios 361H, dell_pesc3 SLIC, SLIC version 2.2) would become 429_dell_pesc3_23.rom (VMware bios 429, dell_pesc3 SLIC, SLIC version 2.3) for the MULTI ROMs I posted. Slic 2.3 activation refers NT 6.0 (Vista/Server 2008), NT 6.1 (7/Server 2008 R2), NT 6.2 (Server 2012) & NT 6.3 (Server 2012 R2) activation. You can activate any one of these using any 2.3 SLIC as long as you use the corresponding certificate.
Thank you pantagruel Pantagruel thanks for the great job with sharing these SLICs. Very generous of you.
@pantagruel: You had been so kind to provide me an Asus Slic 2.1 version of the 429 rom for my Windows 7 guest. Would'nt I need an Asus 2.3 rom if the above is right? Or could I still use the old Asus 2.1 Slic 6006.rom to patch a recent vmware-vmx.exe?
SLP 2.3 is backward compatible with SLP 2.1, but Asus doesn't have a 2.3 SLIC. You can continue to use the Asus 2.1 SLICed 6006.rom as is in a guest, or use it to to patch a more recent Workstation (BIOS 429) vmware-vmx.exe. You won't be able to activate Server 2012 or Server 2012 R2 with the 2.1 SLIC, though.
VMware Workstation 12.5 Mod From VMware: VMware 12.5 has the same 429 BIOS build as prior VMware Workstation 12 releases, but vmware-vmx.exe has changed. If you are using a prior Version 12 mod (12, 12.01, 12.1, 12.1.1) you will only be affected by this update if you are using the modded vmware-vmx.exe, the modded 6006.rom (BIOS) is the same. Added to the first post.
Recommend sticky this post and un-sticky the outdated ones. I was trying to work with the stickied ones and was frustrated as why it didn't work. This found this post by chance and everything works now.
If anybody know chineese can tell me the answer. I want to register for download too. *楠岃瘉鐮�: 鎹竴涓� 杈撳叆涓嬪浘涓殑瀛楃
Hello I am having a hard time with this method: Method 1 – Use the modded 6006.rom [overrides the default VMware BIOS]. Copy the 6006.rom into the VM folder, located by default at C:\Users\<username>\Documents\Virtual Machines\<guestOSname> In the same folder edit the <guestOSname>.vmx file and add the line bios440.filename = "6006.rom" my guestOSname is this - Windows 7 x64.vmx how will I add this bios440.filename = "6006.rom" on the line? Appreciate your reply.
Open the vmx file in a text editor (like notepad) and add the line bios440.filename = "6006.rom" anywhere in the vmx file. It will look like this: Code: . . . usb:1.parent = "-1" sata0:1.startConnected = "TRUE" tools.syncTime = "FALSE" tools.remindInstall = "FALSE" toolsInstallManager.updateCounter = "5" floppy0.present = "FALSE" bios440.filename = "6006.rom" svga.guestBackedPrimaryAware = "TRUE" checkpoint.vmState.readOnly = "FALSE" checkpoint.vmState = "" workingDir = "." . . .