Forum Replies Created
See the radiobuttons in the bottom of the driver wizard dialog:
So, is the SYS file created?
Did you also try “VS build system”?
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.
When you build the project, does it show any messages? Is the SYS file created?
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)?
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.
Just use the “error list” panel. The errors/warnings should be translated correctly.
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.
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.
Were you able to set breakpoints/use the “forcible break-in” option?
Do you put the complete path including the version number (e.g. E:WinDDK7600.16385.0)?
If yes, could you please post a screenshot?
1) I will add an option for batchmnt to use the portable driver in the next version.
2) I assume, this could be related to some handles that Windows keeps open, so that the new driver cannot register itself in the system before those are released. However, when I tested it, installing/uninstalling/reinstalling the portable driver did not require a restart.
Thank you for the WinPE image. I have downloaded it and tried on a VM.
It seems that WinPE does not support dynamic Plug-n-Play device recognition (e.g. USB disks). WinCDEmu relies on Plug-n-Play manager to create the virtual drives dynamically and will not work unless the OS supports it.
I would recommend using some third-party Windows LiveCD compilations with full Plug-n-Play support.
The workaround for iTunes problem was added in version 3.4.
OK, thanks for the fix. I’ll include it in the next version.