- Mar 23, 2015
- 555
I like trying combos of security softwares in the virtual OS hosted in VMware Player Free.
But sometimes, some combos would break down the virtual OS. For example, I found that, after installing Comodo Firewall and HitmanPro.Alert BETA on WinXP, there will be nothing on the desktop after reboot
...
It is not a serious problem if you virtual machine has snapshot function. But the free version of vmware player does not.
What was worse, we can hardly enter the safe mode to uninstall the conflicted antivirus programs to save the corrupted virtual OS, especially WinXP and Win7.
This is because, the time period between we start up the virtual machine and the logo of windows appears is too short, which makes us have no time to press "F8".
This is not a big problem of Win 8.1, which will automatically prompts you whether to enter the safe mode or not after you reboot it several times. But WinXP and Win7 will not.
In the past, I would just abandon the corrupted virtual machine and set up a new one. But the installation of updates and patches for the new system will consume much time.
Today, I found that, we can solve this problem by adding:
bios.bootDelay = "XXX"
to the vmx file in the folder which hosts the disk image files of the virtual machine, where "XXX" should be a large enough number.
By the way I am not sure whether it is proper to post this thread in this "how-to" sub-forum, since this approach is somewhat trivial. If there is another sub-forum that can better match the topic of this thread, please move this thread, thanks.
But sometimes, some combos would break down the virtual OS. For example, I found that, after installing Comodo Firewall and HitmanPro.Alert BETA on WinXP, there will be nothing on the desktop after reboot
...It is not a serious problem if you virtual machine has snapshot function. But the free version of vmware player does not.
What was worse, we can hardly enter the safe mode to uninstall the conflicted antivirus programs to save the corrupted virtual OS, especially WinXP and Win7.
This is because, the time period between we start up the virtual machine and the logo of windows appears is too short, which makes us have no time to press "F8".
This is not a big problem of Win 8.1, which will automatically prompts you whether to enter the safe mode or not after you reboot it several times. But WinXP and Win7 will not.
In the past, I would just abandon the corrupted virtual machine and set up a new one. But the installation of updates and patches for the new system will consume much time.
Today, I found that, we can solve this problem by adding:
bios.bootDelay = "XXX"
to the vmx file in the folder which hosts the disk image files of the virtual machine, where "XXX" should be a large enough number.
By the way I am not sure whether it is proper to post this thread in this "how-to" sub-forum, since this approach is somewhat trivial
. If there is another sub-forum that can better match the topic of this thread, please move this thread, thanks.
