Forum Replies Created
-
Posts
-
BTW, the forgotten context menu on uninstall was fixed in version 3.5. Now the menu entry will disappear in a short time after uninstallation (when Explorer unloads unused modules) or after a restart.
Currently, BluRay discs are not supported, but it’s planned in the next release.
Update: try WinCDEmu 3.6 beta 1. It has an experimental support for Blu-Ray disc imaegs.OK. The portable WinCDEmu always uses its own driver and does not know anything about the “normal WinCDEmu driver”. I don’t see any reason to use portable WinCDEmu GUI while having the normal WinCDEmu installed.
As for the driver, the ‘uninstall’ button just removed the portable driver, making the PortableWinCDEmu GUI useless. Normally, it should reinstall the driver next time it is started. If this does not happen, remove the BazisPortableCDBus service manually and re-run the portable GUI. The normal WinCDEmu GUI should not interfere with the portable driver as well.Currently not going. I am planning to merge the portable and normal WinCDEmu GUI in the next version, so that the portable version will automatically support the same features, but will use a different driver.
The IP address is needed to control the driver and update its binary automatically. Otherwise, you would have to copy the file and start the service manually.
In order to debug a driver on a second machine, you either need either a direct COM, or FireWire connection. This is a general limitation related to driver debugging and is not VisualDDK-specific.
OK. That explains. To debug your driver you need either another physical PC, or a virtual machine.
The easiest way is to install VirtualBox (it is free), install Windows into it, setup the VirtualKD back-end (go to http://visualddk.sysprogs.org/, look for vminstall), reboot your VM in debug mode and select it in the “Virtual Machine” combo box.See the radiobuttons in the bottom of the driver wizard dialog:
[attachment=0:152ahi4z]drvwiz.png[/attachment:152ahi4z]I am assuming, the “0 files compiled” message is the key one.
Have you updated the “sources” file?
BTW, you can simplify it by selecting “Use VIsual Studio build system” in the Driver Wizard, so that the created project won’t need the external build utility and the sources file.Does the driver building succeed? Or are there any error messages? Does the problem persist if you create a driver using Visual Studio build system (specified in the wizard)?
