@ Searchengine, Test1-x32&64bit working fine with vmware 8 on windows 7 x86 patched to dell slic2.1 and slp1.0
I also read VMware 8 now allows a "passthrough SLIC" that it will basically use the SLIC table of the hostmachine to replicate into the virtual images running on this. Is this a rumor or truth? Is limited to something Cisco related but "easily hacked" (?) Read this on a Chinese site so not sure wtf they were talking about!
Thanks Searchengine, Worked great on HP slic 2.1 and slp 1.0 x86 Win 7 Vmware 8. Thanks for the timely update.
hi that is a wonderful work. I have Win 7 x64 and patched my VMWare8 with a Asus BIOS. That was no Problem and it works wonderful.
thanks for all the feedback re latest "test patchers"... Updated 1st Page Descriptions and download links when I get the time, I will update all bios's to bld 339, and re-update download links
I had used "VMBIOS_Selector_v315-339a.exe" on Windows XP PRO x64. As the result, it was not able to patch any "vmware-vmx.exe" file. An error was generated when I run "VMBIOS_Selector_v315-339a.exe" because ".cmd" is not related to any application. Therefore "VMBIOS.cmd" was not able to run. I executed "VMBIOS.cmd" directly, then a user account selection dialog was displayed. I selected Administrator and entered its password but the access of "HP_339.exe" to "vmware-vmx.exe" file was denied. I copied "HP_339.exe" file to the directory of "vmware-vmx.exe" file and I executed "HP_339 -force". Then I confirmed that the "vmware-vmx.exe" file was patched. The patched "vmware-vmx.exe" file provided both function of SLP 1.0 and 2.1 to my HP PC. Anyway, I succeeded in using VMware 8 and using guest PCs of XP and W7 on my HP PC.
There is a problem with your system especially when it cannot run or does not know what a .cmd file is. Code: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\cmdfile] @="Windows Command Script" "EditFlags"=hex:30,04,00,00 "FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\ 00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\ 32,00,5c,00,61,00,63,00,70,00,70,00,61,00,67,00,65,00,2e,00,64,00,6c,00,6c,\ 00,2c,00,2d,00,36,00,30,00,30,00,33,00,00,00 [HKEY_CLASSES_ROOT\cmdfile\DefaultIcon] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,6d,00,\ 61,00,67,00,65,00,72,00,65,00,73,00,2e,00,64,00,6c,00,6c,00,2c,00,2d,00,36,\ 00,38,00,00,00 [HKEY_CLASSES_ROOT\cmdfile\shell] [HKEY_CLASSES_ROOT\cmdfile\shell\edit] [HKEY_CLASSES_ROOT\cmdfile\shell\edit\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4e,00,4f,00,\ 54,00,45,00,50,00,41,00,44,00,2e,00,45,00,58,00,45,00,20,00,25,00,31,00,00,\ 00 [HKEY_CLASSES_ROOT\cmdfile\shell\open] "EditFlags"=hex:00,00,00,00 [HKEY_CLASSES_ROOT\cmdfile\shell\open\command] @="\"%1\" %*" [HKEY_CLASSES_ROOT\cmdfile\shell\print] [HKEY_CLASSES_ROOT\cmdfile\shell\print\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4e,00,4f,00,\ 54,00,45,00,50,00,41,00,44,00,2e,00,45,00,58,00,45,00,20,00,2f,00,70,00,20,\ 00,25,00,31,00,00,00 [HKEY_CLASSES_ROOT\cmdfile\shell\runas] "HasLUAShield"="" [HKEY_CLASSES_ROOT\cmdfile\shell\runas\command] @=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\ 00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,63,00,6d,00,\ 64,00,2e,00,65,00,78,00,65,00,20,00,2f,00,43,00,20,00,22,00,25,00,31,00,22,\ 00,20,00,25,00,2a,00,00,00 [HKEY_CLASSES_ROOT\cmdfile\shell\runasuser] @="@shell32.dll,-50944" "Extended"="" "SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}" [HKEY_CLASSES_ROOT\cmdfile\shell\runasuser\command] "DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}" [HKEY_CLASSES_ROOT\cmdfile\ShellEx] [HKEY_CLASSES_ROOT\cmdfile\ShellEx\ContextMenuHandlers] @="Compatibility" [HKEY_CLASSES_ROOT\cmdfile\ShellEx\ContextMenuHandlers\Compatibility] @="{1d27f844-3a1f-4410-85ac-14651078412d}" [HKEY_CLASSES_ROOT\cmdfile\ShellEx\DropHandler] @="{86C86720-42A0-1069-A2E8-08002B30309D}" [HKEY_CLASSES_ROOT\cmdfile\ShellEx\PropertySheetHandlers] [HKEY_CLASSES_ROOT\cmdfile\ShellEx\PropertySheetHandlers\PifProps] @="{86F19A00-42A0-1069-A2E9-08002B30309D}" [HKEY_CLASSES_ROOT\cmdfile\ShellEx\PropertySheetHandlers\ShimLayer Property Page] @="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}" [HKEY_CLASSES_ROOT\cmdfile\ShellEx\{8895b1c6-b41f-4c1c-a562-0d564250836f}] @="{1531d583-8375-4d3f-b5fb-d23bbd169f22}" Copy text above and save it as CMD.reg then double click to merge it into registry hope this helps.
@urie Thank you so much for your advice. The ".cmd" was related by your reg file so It was not needed to execute "VMBIOS.cmd", but a dialog of user account selection to run the program was displayed. On the dialog, I selected Administrator and entered its password, but the process was finished at the same time, and the patch was not executed.
re: vmw workstation v8... x64bit - manual extraction|execution of files from patcher not recommended in x64bit OS, auto-patching has to be achieved from Elevated Command, "run as Administator" is not enough, VMBIOS.cmd is ran as an "elevated command", and the patch files (ie.HP_339..exe) are ran in "elevated" status. the installer directly initiates and executes this process in win7|Vista... Xp under investigation.
hmm, so "Test3-patcher" worked, but "VMBIOS_Selector_v315-339a.exe" failed on Xp Pro x64 with vmw workstation v8?
@searchengine Sorry for my mistake. My Acer PC is Win 7 Pro x64, and my HP PC is in XP Pro X64. Your patch worked fine on the Win 7 x64 with elevated command, but it can run as Administator without an elevated command on Win XP x64 so the patch didn't work. Finally, I was able to patch a "vmware-vmx.exe" file with "HP_339 -force" command. It was perfect implementation of SLP1.0 and SLIC2.1.
Come one, it is not magic, all the patcher does is replace Binary 6006 resources (BIOS) with an adjusted version (SLP & SLIC 2.1) sebus
@nori2nori... can you please download this file Deleted Test Link and extract folder to your desktop on XP Pro x64bit. keep all files together in one folder (4 files), and double-click the xptest.cmd file, and tell me if the vmware-vmx.exe (in same folder) gets patched, and a backup copy left in the same folder...thanks.
@sebus I confirmed that the patched bios data set was added to a 6006 resource (not be replaced). I succeeded in extracting a bios file from there (two data sets in a 6006 resource). The bios file was recognized as a perfect HP's rom when I specified it onto a vmx file as an external bios file. Thank you so much for your advice as always. @searchengine Unfortunatelly, an error as "HP_339.exe can not be found" was generated when I double-clicked the xptest.cmd file in the folder which I made on my desktop. I moved their 4 files to the "c:\test" folder, but the same error took place. Therefore the patch was not performed. Thank you so much for your efforts.
ok, I don't have XP x64bit installed, so just need to wait and see if any negative feedback from other XP x64bit users.