Forum Replies Created
-
AuthorPosts
-
support
KeymasterThe incompatibility caused by GearASPIWdm is a known issue. If you prefer calling WinCDEmu buggy rather than searching the forum for a solution, it is your choice.
To remove the “Select drive letter & mount” prompt, please go to the HKCR.iso key, look up the default value there (e.g. BazisVirtualCD.Iso), then go to HKCR{value from .iso}shell and remove the “Select drive letter && mount” subkey.support
KeymasterYou can remove any unusable program, as well as any usable program by using “add/remove programs” applet in the Control Panel.
Additionally, I would recommend checking for buggy 3rd-party CDROM filter drivers (search this forum for GearASPIWdm). They might be the reason of WinCDEmu being unusable on your machine.support
KeymasterDid you select “never install non-WHQL-signed drivers” in your system settings?
WinCDEmu now has a signed kernel-mode driver, but it was obviously not WHQL-certified.support
KeymasterDone. Check out the beta here: http://wincdemu.sysprogs.org/portable
support
KeymasterIf 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.
support
KeymasterI 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…
support
KeymasterThese ‘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.
support
KeymasterIs the device shown in the Device Manager? And in the “drive management” under “my computer -> manage”?
support
KeymasterThis is related to poorly designed CDROM filters provided by 3rd-party software. Please search for GearASPIWdm on this forum.
support
KeymasterOK. 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).
support
KeymasterPlease use the download link for the signed version instead (http://sourceforge.net/projects/wincdemu/files/wincdemu/3.3/WinCDEmu-3.3-signed.exe/download)
support
KeymasterFinally released a signed version.
support
KeymasterASPI32 is not related to WinCDEmu. It is most likely a leftover from some other CD burning software (e.g. iTunes)
support
KeymasterAFAIK, you can use normal Visual Studio with UMDF. VisualDDK is needed for kernel mode only.
support
KeymasterThis is a well-known bug in version 3.1. Please install WinCDEmu 3.3
-
AuthorPosts