Forum Replies Created
-
Posts
-
No, it is based on a virtual bus driver, that accepts requests from mounter application. When you click on an image, the bus driver reports that a new device was inserted into it (as if you have inserted a USB stick into USB port) and Windows loads the BazisVirtualCD.sys driver that presents the newly found device as a CD/DVD-ROM device. You can see it from Device Manager if you select ‘display devices by connection’.
That could be nice, however, CUE+APE & etc formats require special decoding module, multi-track mode & etc. Basically, to add this single feature, the source code size would be increased 5 times, that is not the way of WinCDEmu.
I cannot say that this feature will never be added, however, unfortunately, it won’t happen in the nearest future.
P.S. You can use various other free software for APE/FLAC decoding, such as Winamp plugins.I guess that the problem is caused by WinDbg using MASM syntax parser by default, and VisualDDK using C++ parser (switching it every time would be very slow). You can try using @@masm(nt!…), however, in the future versions, I’ll add automatic redirection to Disassembly window when the ‘u’ command is typed.
Regarding the automatic command completion by ‘TAB’, is there any textfile, containing a list of all WinDbg commands? Parsing help files and rebuilding it could be quite inaccurate. If not, I’ll maybe add this support to next version, but provide only a sample command list file, encouraging users to update it.What does .symopt show in WinDbg and VisualDDK? If you set symbol options in VisualDDK equal to WinDbg ones, will the bug disappear? If you open Disassembly window in Visual Studio, and type IoCreateFile (should work even without nt! prefix there), does it locate the function correctly?
Well, it’s a Microsoft policy in Vista x64 to prevent loading of unsigned drivers. As signing drivers by Microsoft requires quite a budget, it is not an option for free software, like WinCDEmu. A partial workaround is decsribed here: http://www.elandigitalsystems.com/support/code39faq.php.
VMMON is not needed while using VisualDDK, as VisualDDK takes its role using functions from KDCLIENT.DLL.
You can start VisualDDK debugging session even before the target OS is booted. In that case, VisualDDK will connect to VM and will be waiting for the OS to load. Basically, an open VIsualDDK session is completely equivalent to an open WinDbg session, from KDVMWare’s point of view.
