application cannot run under virtual machine

[ragemage83]

hi as the title says i have a error message that i cannot run my game under virtual machine i already got a fix but i need the config file for that where can i find it ?

[mpack]

You need to ask the game developers. There is nothing you can do in VirtualBox.

[ragemage83]

there is i need to add some lines in the config file wich i cannot find as i wrote above

[mpack]

I have no idea which config file you might be referring to.

In any case, there is nothing you can write to any VirtualBox config file which will prevent a guest application from detecting that it is running inside a VM, at least not if the programmer knows his business.

[ragemage83]

I added these strings in vmware config file and it works fine:

monitor_control.virtual_rdtsc = "false"
monitor_control.restrict_backdoor = "true"
isolation.tools.getPtrLocation.disable = "true"
isolation.tools.setPtrLocation.disable = "true"
isolation.tools.setVersion.disable = "true"
isolation.tools.getVersion.disable = "true"
monitor_control.disable_directexec = "true"

But i want use VirtualBox this way, can i fix it?
kabbahan

Posts: 2
Joined: 19. Nov 2010, 21:18
Primary OS: Ubuntu other
VBox Version: PUEL
Guest OSses: XP

thats what i found on this forum ...
viewtopic.php?p=162776

[mpack]

Are you using the same software that was being discussed in that thread from >5 years ago?

1. I am not aware of any direct VirtualBox equivalents to those config strings.
2. I very much doubt that they really worked in 2010. I only have unsubstantiated assertions for that.
3. I very much doubt they would work with any other guest application (if it worked for even that one then that programmer clearly did NOT know his business - in 2010).
4. In 2016 programmers are much more aware of VMs. The tests which detect them will be harder to fool.

Detecting that you're running in a VM is trivially easy, and impossible to fool. For example, a very simple test would be to detect unique virtual hardware directly, e.g. VBOXHARDDISK, VBOXVGA (*), or presence of the VirtualBox Guest Additions. Those are device IDs that control device driver selection, so you can't easily change those strings. Next would be the presence of standard but obsolete hardware, e.g. an apparently ancient network card: you can simply refuse to run on ancient PCs, it probably won't cost you any business even if the hardware was real (those clients clearly don't like to spend money), finally you can do simple latency tests on hardware.

The notion that you can change a couple of config strings and suddenly the software can't detect that it's running in a VM any more is, frankly, quite ludicrous.

(*) These names are from memory, I haven't bothered to look them up.

[ragemage83]

its not only a solution here on the site i found that clue on other sites too its for a older programm so nothing actually but since u say it doesnt work iam not waist my time anymore thx for ur time and help