Daemon Tools securom emulation broken in WinXP guest?

[vollmond]

In my native Windows install, I am able to load and play a .nrg (Nero) image of Diablo II: Lord of Destruction with the Daemon Tools app. When I try to do the same thing in my Virtualbox instance of XP, though, I get a typical "can't see the disk" error that LOD gives when it can't verify securom drm.


Any ideas?

I get the same thing if I try to mount a .iso of the disk through the Virtualbox cdrom settings, as well.

[frank]

What is securom drm? Some external device?

[chungy]

SecuROM is a copy protection method on discs, relying on bad subchannel data...

[frank]

So how did you use your .nrg file with VirtualBox? If you use the original CDROM, make sure that the CDROM passthrough mode is enabled. But keep in mind that this mode is less tested than the standard (non-passthrough) mode.

[simulacrum]

This "passthrough" mode don't work in v2 too
And in VirtualBox guest Windows XP don't work any original protected disk.
For explaine, I have original Cambridge Vocabulary in Use disk, bet a can't use it in VirtualBox Windows XP (I have Linux as a host system).

IS any IDEA?

[vkov_tinsky]

In my native Windows install, I am able to load and play a .nrg (Nero) image of Diablo II: Lord of Destruction with the Daemon Tools app.

If you've already installed Diablo II in your VM why don't you use Patch 1.12a which allows you to play without the CD?

Regards,
VT

[simulacrum]

I discovered. The protected disks work fine and without trouble in vmware

GOOD BUY, VIRTUALBOX!

[Harry Tuttle]

You may need to use hardware virtualization.
If your CPU supports it, you can enable this in the settings for that machine (VT-x/AMD-V).

[khooke]

I just tried to install Star Wars Empire at War from original CDs with the registration code on Windowx XP running on VirtualBox 3.2.8 running on Mac OSX 10.6.4.

Even with CD drive passthrough, CPU virtualization settings enabled, SECUROM says at startup:

"Please insert the original disk instead of a backup (1000)"

Before enabling the hardware virtualization settings I think it gave a 3000 error.

Anyway, no good, doesn't work on VirtualBox