[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.

[support]

devenv.exe (enable native debugging!)

[support]

Which BD player are you using? Could it be that the player keeps on running, accessing the drive letter and preventing the disc from being ejected (just like on a physical drive)?

[support]

Try rebooting just to get sure.

[support]

The module is DDKDebugger-dbg.dll. Normally, you simply attach and press the OK button in the “please attach debugger” dialog. This will cause a forced breakpoint, so that the debugger will stop and show the error location.

[support]

Only by downloading VisualDDK sources and modifying DDKDebugConsole project manually.

[support]

Yes, but I’ve got very strange results. Visual Studio shows the wow64 functions in the call stack and pretty much nothing more. I am not sure I can extract any info from that file. Could you try to attach to the process in VIsual Studio (debug->attach), press “OK”, let Visual Studio stop on a breakpoint and:
1) Create a dump using Visual Studio (debug->create dump)
2) Look at the call stack and make a screenshot of it.

You can alternatively download the VisualDDK sources from SourceForge and have a look which code line causes the exception.

[support]

Hi. Could you please send me a sample ISO that does not mount with WinCDEmu 3.6?
Please send an e-mail to ivan {at} sysprogs org. I will provide you with a temporary FTP login/password so that you could upload your files to me.

[support]

OK, which VM are you using? VirtualBox or VMWare?

[support]

The general problem with mounting compressed files is that you normally cannot peek a chunk of data from the middle of a file (or even the entire archive if it’s a solid archive) without decompressing the preceeding data.
I.e. mounting a 4GB iso is instantaneous and does not consume any additional space, but mounting a 4 GB 7z archive would take ~10 minutes to decompress is completely.
I am thinking of adding support for compressed ISO images, but I would need to modify one of the common compression algorithms to accomplish that. As for automatic decompressing of the archives into a temporary directory, you could write a simple script to do that (and clean up the directory after reboot), you don’t need any special tools for that.

[Author]

Posts