what is an easy way (using file operations) to identify ESXi?ģ) If there are executables named vmware-vmx* or similar on the filesystem, in which directory are they and how are they named exactly? Would you like to help me to test it? I probably just need a few answers to extend the unlocker so it can also handle ESXi.ġ) What is the ESXi environment like? Can you get a shell and run Linux executables?Ģ) If yes, how can you distinguish between regular Linux and ESXi? I.e. I have never tested on ESXi because I know very little about ESXi (maybe I should just try running it in a VM). UPDATE: Got it working as I forgot to change the smc paramter to true in my exisiting guests, as you are obviously adding the OSK0/1 fields into the emulation. Would you consider posting in the 'Multiple Boot & Virtualization' forum? One idea, this forum isn't the one most VMware users hang out in. After spending 2 and half years working on this, you have delivered something which means I can hopefully retire my solution. Found that existing VMs using my method cause the CPU to stop when using this method. I guess so long as the code remains in the product and the binary patches are kept up to date then a great solution. I had looked at the code myself, and realised where some of the areas that could be hacked were. I purposedly do not want to give too many details (hence no source code), because I don't want VMware to figure out too easily what to change to make the life of my unlocker harder in future releases. Then I wrote code to do that automatically (split the binary into code sections, then section disassembly, then search for some patterns, then code replacement) on all platforms, in a way that hopefully will adapt when VMware releases new versions. I decompiled the vmware-vmx and vmware processes, and painstakingly determined what to change to remove all the restrictions VMware put in place.

Create ,mac os emulator in vmnware