[support]

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.

[support]

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.

[support]

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.

[support]

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.

[support]

Viel spaß mit WinCDEmu 😉

[support]

Could you post a screenshot of the “Driver launch settings” dialog and the error message box?

[support]

See the radiobuttons in the bottom of the driver wizard dialog:
[attachment=0:152ahi4z]drvwiz.png[/attachment:152ahi4z]

[support]

So, is the SYS file created?
Did you also try “VS build system”?

[support]

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.

[support]

When you build the project, does it show any messages? Is the SYS file created?

[support]

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)?

[support]

Do you have a Visual Studio project for the driver you are trying to debug? If not, use the Debug->Attach menu and deploy the drivers manually. The Driver Launcher will only autodeploy the drivers that are built in Visual Studio.

[support]

Just use the “error list” panel. The errors/warnings should be translated correctly.

[support]

I assume, the problem is related to your German version of Visual Studio.
I would recommend downloading VisualDDK sources (https://sourceforge.net/projects/visualddk/files/visualddk/1.5.2/VisualDDK-1.5.2-src.zip/download), opening the DDKDebugLauncher project, setting breakpoint on OnConnection() method in Connect.cs and stepping through.
The LookupLocalizedName() method should automaticall fetch the German names for “Tools” and “Debug” menus. If this does not happen, or incorrect names are fetched, please tell me the correct ones, so that I can update them in the next release of VisualDDK.

[support]

Unfortunately, AuthentiCode certificates are more than just SSL or usual code signing certificates. I have asked GoDaddy support about compatibility with Authenticode and received an answer that their certificates are not applicable.

[Author]

Posts