DSA Theory Test DVD
Posted: 20. Aug 2014, 16:51
Hi,
This is probably relevant to only those living in the UK; and I can't say the problem is specific to VirtualBox either.
I borrowed a DSA theory test DVD from a friend and installed it on a Windows XP VM. It's an application protected by SecuROM, and fails to launch, citing problems loading security modules. I tried giving direct access to the host DVD drive, providing an ISO image created via. dd, and also mounted a virtual drive in Windows using daemon tools, but the problem remained. So I don't think it's a problem with accessing DVD drive, but rather with having the application launched. When I contacted their support, I was told that they don't support VMs. I tried in Windows XP hosted on both VirtualBox and VMPlayer, both with the same behaviour. I've given up eventually.
I've very little information to offer to ask this question, and this isn't a problem only with VirtualBox, but I wonder using what in the guest could the software be testing for a real hardware. My belief was that VirtualBox would be completely mimicking the underlying hardware and so the guest software, however cunning, shouldn't be able to tell the difference. If we know this, is there a chance of having that mechanism (whatever that is) virtualized?
--
Jeenu
This is probably relevant to only those living in the UK; and I can't say the problem is specific to VirtualBox either.
I borrowed a DSA theory test DVD from a friend and installed it on a Windows XP VM. It's an application protected by SecuROM, and fails to launch, citing problems loading security modules. I tried giving direct access to the host DVD drive, providing an ISO image created via. dd, and also mounted a virtual drive in Windows using daemon tools, but the problem remained. So I don't think it's a problem with accessing DVD drive, but rather with having the application launched. When I contacted their support, I was told that they don't support VMs. I tried in Windows XP hosted on both VirtualBox and VMPlayer, both with the same behaviour. I've given up eventually.
I've very little information to offer to ask this question, and this isn't a problem only with VirtualBox, but I wonder using what in the guest could the software be testing for a real hardware. My belief was that VirtualBox would be completely mimicking the underlying hardware and so the guest software, however cunning, shouldn't be able to tell the difference. If we know this, is there a chance of having that mechanism (whatever that is) virtualized?
--
Jeenu