[support]

It seems that some program keeps open handles to the drive. You can see which exact program it is by downloading Process Explorer from Microsoft and searching for handles to the drive letter.

[support]

It seems to be a bug of KMPlayer. Please install the latest KMPlayer version.

[support]

Hi. FIrst of all, please use the latest version (3.6). If the problem persists, you’re welcome to post here.

[support]

Please re-run VisualDDK configuration tool from start menu to reset plugin settings.
As for “-ceZ”, you can easily modify the build command line from the project settings.

[support]

Maybe, it’s a bug in KMPlayer? WinCDEmu does not lock the system. Anyway, I’ll check for compatibility with KMPlayer and see what I can do.

[support]

Does it happen always? Or did it happen only one time?

[support]

Was there an error message when you clicked “unmount”?
What happens when if you double-click at the drive icon in Explorer? Does the drive open, or is there an error?
Is the CDROM still visible in Device Manager?

[support]

Stop. Did you perform the installation correctly?
1. Rename “normal” VBoxDD.dll to VBoxDD0.dll
2. Copy VirtualKD’s VBoxDD.dll to VirtualBox directory (in place of the original VBoxDD.dll).
Both steps are vital. VirtualKD’s version of VBoxDD.dll should be used by VirtualBox instead of the original. However, it will redirect normal requests to the original DLL (it expects it to be called VBoxDD0.dll).

[support]

Please uninstall VirtualBox, remove all contents of OracleVirtualBox folder in Program Files, reinstall it and use the VBoxDD.dll from VirtualKD 2.5.4. It supports VirtualBox 4.1

[support]

Then you don’t have a network connection between the VM and the host machine. Try adding another network card in the VM settings and selecting “host-only” as the connection type.

[support]

What does the launch window in Visual Studio show? What happens if you press “refresh”?

[support]

Is your firewall blocking the connections to the target machine?

[support]

Does it happen to BD discs only, or data discs as well?

[support]

That looks like a strange bug in VS2010. Do you have the latest service pack installed? If yes, please create a dump file using Visual Studio (Debug->Save dump as) and submit a link to it here.
As another workaround I can suggest getting msdia.dll from VS2008 and registering it in your system. VisualDDK will automatically use it instead.

[support]

This helps partially. Please get symbols for both MSDIA100 and DDKDebugger-dbg:
1. Download http://visualddk.sysprogs.org/DDKDebuggerPDB.zip
2. In Visual Studio right-click on a line containing msdia100.dll, select Load Symbols -> From microsoft servers
3. Right-click on a line containing DDKDebugger-dbg, select Load Symbols -> From file, specify the PDB file from the archive
This should update the call stack and make it more informative. Please submit a new screenshot.

[Author]

Posts