Forum Replies Created
-
Posts
-
OK, the security considerations are regarding the VisualDDK monitor (the program that runs on VM and starts your driver on demand). As for the VM monitor, you can simply close it when you don’t need it any more. VisualDDK can detect and patch the required VMs automatically when you start debugging in Visual Studio and does not need the VM monitor.
I assume, the game uses some kind of a copy protection mechanism. WinCDEmu is a simple image mounting program and is not designed to counteract the copy protection systems.
The problem is that creating a “Virtual CD/DVD burner” is somewhat around 5x complexity of WinCDEmu. So, unless there are volunteers to implement it, I would recommend other ways of “burn-testing”.
BTW, as far as I remember, some CD burning programs can actually create ISO images. Should be the same effect, more or less.Try the quickstart manual: http://visualddk.sysprogs.org/quickstart
You don’t *need* a virtual machine, but using it together with VirtualKD would make debugging lots faster than COM port. If you want to debug drivers for real hardware, I recommend using FireWire connection.Hi,
I’ve checked BazisLib sources. It seems that the problem was caused due to the FILE_RANDOM_ACCESS flag present in kDefaultAdditionalFlags inside bzsddkfile.h
Please download BazisLib 2.5.2 to fix the problem.Please examine the build log to ensure that you build the 64-bit version of the driver.
You might also need to enable testsigning mode on the VM.Fixed. Please download latest VisualDDK, use the driver project wizard and select “get additional templates”. It will download BazisLib and use the fixed RAMDISK temlpate.
Hi, all.
Starting from VisualDDK 1.5.2/BazisLib 2.5.2 the BazisLib project templates have been integrated into VisualDDK project Wizard and will work for Visual Studio 2005, 2008 and 2010.Fixed. Please use the following link:
http://sourceforge.net/projects/wincdemu/files/wincdemu/3.4/PortableWinCDEmu-3.4.exe/downloadHi, please don’t create multiple topics regarding the same problem. Check the default BazisLib::DDK::File flags.
