Forum Replies Created
-
Posts
-
Ok, VisualDDK setup checks the validity of WDK path in the following way:
The file %WDKPATH%incddkntddk.h should exist. %WDKPATH% is the path you enter in the setup window. Please check that the file exists on your machine and that you are entering correct path.
Visual Studio Express does not support building ATL applications. So, some user-mode parts of BazisLib and some other stuff will not be functional. Otherwise, should work.
You need BazisLib for that. It comes with automatic installer, so all paths will be set up automatically.
P.S. The only answer to the question ” some header file not reading” could be “you should add something somewhere”. Next time, please specify the exact error message, so I can provide a real answer, not just a guess 😀Sure, use the SourceForge download page here:
http://sourceforge.net/projects/wincdemuProblem is that the .BIN extension is not only used for CD/DVD images and registering it by default is not the best idea. However, in the future versions I’ll most likely add a non-default context menu command for it (present version of installer does not support it).
DVD disks with DVD movies include additional protection stuff, that is not emulated by WinCDEmu. That’s why some programs see the drives as CD.WinCDEmu is not targeted to be a protection emulation software, it is a quick and simple image mounter, not more.
You don’t need to reinstall the OS. Just install another application that will associate itself with ISO files and that’s it.
Testsigning should be always on. Otherwise, only drivers signed by MS partners can be loaded. As for the missing file, could you please see the name of the executable, that reports “cannot find driver”? It can be done in the task manager by selecting the task and clicking “go to process”. It should be 64-bit vmnt64.exe. The BazisVirtualCD.sys driver should be also present in SYSTEM32DRIVERS.
OK. I don’t have Win2K machine to test the new installer. However, In 1-2 weeks I’ll publish a version with extended error reporting, so you can run it on Win2K and tell me the reason of the problem.
Looks like your CUE file contains audio tracks. Presently, WinCDEmu does not support multi-track CDs. However, this feature will probably be added in future versions.
Obviously, you need a WinDbg (http://www.microsoft.com/whdc/devtools/debugging/) to do that. I recommend reading some tutorials about ‘kernel debugging for beginners’ before starting. Note that VirtualKD is not itself a kernel debugger. Instead, it is a tool, that speeds up interaction between a virtual machine and WinDbg.
Ok, if you mount an image, ensure that an “error code 10” appears in Device Manager, open command prompt and type “net start BazisVirtualCD”, which error message will you get?
Well, if you are already debugging your machine with WinDbg, how can VisualDDK attach to it? The pipe is obviously occupied by WinDbg instance. However, if you close the WinDbg (and uncheck ‘automatically start the debugger’ in VMMON, or just close VMMON, as it is no needed for VisualDDK), debugging from VisualDDK should work.
Bridging is required for automatic driver binary updating, however, is not mandatory for debugging with VisualDDK. If WinDbg/VirtualKD works, and VisualStudio with VisualDDK fails, you can try using Debug->Attach command, selecting “Kernel-mode connections” and picking your OS manually. You will get either a working debug session, or a more detailed error message.
