Forum Replies Created
-
Posts
-
This is related to poorly designed CDROM filters provided by 3rd-party software. Please search for GearASPIWdm on this forum.
OK. You might be having the problem related to the CDROM filters. Please do a search for GearASPIWdm in this forum and read the problems others had and the solutions they used. If you still have problems, you’re welcome to post here (please create a separate topic, though).
Please use the download link for the signed version instead (http://sourceforge.net/projects/wincdemu/files/wincdemu/3.3/WinCDEmu-3.3-signed.exe/download)
ASPI32 is not related to WinCDEmu. It is most likely a leftover from some other CD burning software (e.g. iTunes)
Cleanup program removes registry entries with history of previously mounted images. After running it you should be able to uninstall WinCDEmu using the normal uninstaller (you might need to reboot after running cleanup). The problem with registry paths is a known compatibility issue and will be resolved in the next release of WinCDEmu.
Not yet. I have contacted GlobalSign in April and was informed that they need “just a bit of time”, as I am an individual, rather than a company. Since April, they kept pushing the deadline forward several times, so I am currently searching for alternative ways to get the certificate.
As far as I remember, there were some minor bugfixes. Plus, some features used by VisualDDK.
Regarding the PDB files, installing BazisLib and building VirtualKD from sources is no longer a problem (with automated BazisLib installer). So, supplying large pre-built PDB files with the product is no longer an advantage.The menu items will be enabled only when you have a driver project open. To create a driver project, use the normal “Create Project” dialog and select “VisualDDK” there.
The Express edition does not have support for extensions, thus, VisualDDK won’t work with it. AFAIK, free copies of Visual Studio Professional are distributed via BizSpark and DreamSpark programmes. See Microsoft website for details.
That’s just brilliant. Apparently, the Gear installer (file was called Download GEARDVD703rc19 now.exe) installed the 32-bit filter driver (that was of course ignored on 64-bit Windows), but updated the “UpperFilters” key, making me believe that the driver was there. So, no “GearDVD over iTunes” recipe” will work, unfortunately 🙁
I’ll try to investigate the GEAR-related problems later and maybe add some workaround, but I cannot promise anything, as gear stuff seems to be a big buggy mess, and I don’t want to support CD/DVD burning/identification commands in WinCDEmu, as this may come out twice more complex than the current WinCDEmu code.
