This shows you the differences between two versions of the page.
Previous revisionNext revision | |||
— | fuss:vmware [2020/09/01 21:46] – office | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Allow Application to Run Under Virtual Machine (Themida) ====== | ||
+ | Navigate to the registry entry: '' | ||
+ | |||
+ | Edit the virtual machine configuration ('' | ||
+ | < | ||
+ | monitor_control.restrict_backdoor = " | ||
+ | isolation. tools.getPtrLocation.disable = " | ||
+ | isolation. tools.setPtrLocation.disable = " | ||
+ | isolation. tools.setVersion.disable = " | ||
+ | isolation. tools.getVersion.disable = " | ||
+ | monitor_control.disable_directexec = " | ||
+ | </ | ||
+ | |||
+ | ====== Change Boot Order ====== | ||
+ | |||
+ | Shockingly, for an enterprise-grade software, there is no easy option to change the boot order via the virtual machine settings. The general recommendation is to boot the virtual machine and " | ||
+ | |||
+ | One way around this issue is to edit the VM " | ||
+ | |||
+ | < | ||
+ | bios.bootOrder = " | ||
+ | </ | ||
+ | |||
+ | and then reload the virtual machine in VMWare workstation for the settings to take effect. |