Forum Replies Created
-
Posts
-
Done. Check out the beta here: http://wincdemu.sysprogs.org/portable
If you can find a detailed description for those formats, I will consider supporting them. Otherwise, analyzing an unknown binary format is quite a hassle and is questionable unless the format is really popular. You can also provide your own implementation based on WinCDEmu format driver interface, so I will include it in future versions of WinCDEmu.
I guess, you can use devcon or other Microsoft tools to cleanup drive information as well. Anyway, do such leftovers cause any real inconvenience to anyone? Windows is designed to keep history of all previously connected devices, this information does not occupy any considerable amount of your disk space or RAM and does not slow your system…
These ‘leftovers’ is the way Windows stores the information about devices. Any USB flash drive will leave exactly the same “leftovers” in any system. I would NOT recommend deleting these keys manually, as it can damage some internal dependencies maintained by Windows.
Is the device shown in the Device Manager? And in the “drive management” under “my computer -> manage”?
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.
