Forum Replies Created
-
Posts
-
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.
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.
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.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.It is generally possible, but you would need to hack VirtualKD code for that. I could give you more details if you’re interested.
You can create the dump file by opening Task Manager, finding the error message, selecting “switch to process” from the context menu and finally right-clicking on the process (should be devenv.exe) and selecting “create dump file”.
Seems to be a WinCDEmu bug. Can also be some weird incompatibility issue. Could you please create a dump file and send it to me?
Oops. Copying both to system32 was a bad idea. WinDBG uses some very special version of dbghelp.dll that is incompatible with most other clients.
Please restore the original versions and specify the debugging tools location in VisualDDK properties. VIsualDDK will automatically use the correct versions.In fact, I’m travelling around till August and only checking my messages once or twice per day. I assume, somewhat in the August I will probably have some time. But definitely not before. If you have good C++ background, I could show you what to hack in WinCDEmu sources to add this feature.
