Forum Replies Created
-
Posts
-
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.
Sure, however, with relatively small DriverEntry this will not give any noticeable effect. On the other hand, moving some initialization functions to .init section may cause failures, in case such functions are accidentally called after initialization. So, IMHO, freeing up to 10K of RAM (typically less than 1K) on a 1-4GB machine at a cost of making the code potentially unstable (if later one forgets that a certain function is in .init) is not very reasonable. However, this is just my IMHO.
So, if i understand correctly, i can use new/delete/npagednew in KM C++ if i include stlsup.cpp?
Yes. Otherwise you will simply get a linker error stating that “operator new()” is undefined.
Just try DDKWizard, why you not use RTL_CONSTANT_STRING to define DeviceName and Win32Device instead of RtlInitUnicodeString?
Sample files for DDKWizard were copy-pasted from some very old stuff without any refactorring. Anyway, thanks for the advice, I’ll probably update the samples.
It is managed by BazisLib. You can see the stlsup.cpp file for new() and delete() implementation. However, note that if you need to allocate objects from non-paged pool, you should use the npagednew() function instead (or, more preferably, overload the new() operator for your specific class, that always needs to be allocated from non-paged pool; for example, see the irpqueue.h file). The standard C malloc()/free() implementations are provided as well for compatibility reasons.
