Forum Replies Created
-
Posts
-
It is possible to dump iTunes installation script to see what it does, but if removing the filter caused problems for iTunes, 99% that it is the reason.
I suggest installing the trial of the latest GearDVD or whatever, making a copy of the latest GearASPIWdm that it installs (after ensuring that it has no problems with WinCDEmu), uninstalling it, reinstalling iTunes (so that it will install the old buggy GearASPIWdm again) and then manually replacing the GearASPIWdm.sys installed by iTunes with the one that came with GearDVD trial. Note that you will need to restart after replacing the SYS driver.Let’s say, not without a hack. It is possible to do something like “disable filters -> mount image -> wait for drive letter assignment -> reenable filters” every time, but this can turn your entire system into a buggy mess if some other programs have some other hardcoded expectations. Plus, trying to mount 2 images using 2 different emulators at the same time would be destructive.
I suggest understanding whether you really need this filter. If not, simply delete it with devcon. If yes, install the latest version of the product that uses it (e.g. the version that comes with the trial of GearDVD did not cause any problems on my test machine). Most likely, there is a bug in your version of GearASPIWDM that has been fixed in newer versions.Ok, I guess, I posted a slightly incorrect link. Here is the recipe:
Select “start->run” or press “Windows key + R key”, type “regedit”.
Go to HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Control -> Class
Press “Ctrl+F”, type “cdrom”, press ENTER.
Ensure that the “{4D36E965-E325-11CE-BFC1-08002BE10318}” class was selected on the left.
Carefully examine the values on the right. If anything like “UpperFilters”, “LowerFilters” or anything else containing the word “filter” appears there, please either post the values here, or make a screenshot of your regedit window.If the “UpperFilters” is non-empty, try using devcon to remove it and test whether WinCDEmu works.
As for keeping AnyDVD, I suppose, it uses a filter driver – a special driver, that intercepts the connection between the operating system and the original driver and does some background hacking (e.g. prevents other applications from accessing the drive while recording is in process). The problem is that it has its own internal assumptions about the underlying CDROM driver, that I cannot know. As WinCDEmu emulates only basic features, something confuses the filter driver and it sabotages the virtual device. If you get the exact name of the filter driver and I manage to reproduce the bug on my machine, I might be able to make WinCDEmu satisfy AnyDVD’s expectations. However, I cannot promise any success, as the problem is generally outside WinCDEmu and can be hard to analyze.
Please ensure that the AnyDVD filter was removed from the “UpperFilters” for CDROM class (more details here: viewtopic.php?f=3&t=457&start=10)
Devcon is a Microsoft utility from Windows Driver Kit, that does various maintenance things related to device drivers. You can read more here: http://support.microsoft.com/kb/311272
Yes, you can delete “UpperFilters” manually, but you will most likely need to reboot afterwards and there may be some leftovers in the registry, that devcon would clean up otherwise.
I have no clue, how did GEARAspiWDM get on your machine, but googling it points to Gear Software. Maybe, some other product uses it as well. I have installed InfraRecorder 0.50 on my VM and found out that it did not add GEARAspiWDM.Ok, the GEARAspiWDM, that is the reason of the problem, comes from “GearDVD” and related software. I have checked the latest GearDVD trial on Win7x64 and did not encounter any problems with WinCDEmu. It seems that you have previously installed some older Gear Software products, that left this filter driver. To remove it, please download devcon utility (http://wincdemu.sysprogs.org/devcon.zip) and run the following command line:
devcon classfilter cdrom upper !GEARAspiWDMOk, the “GEARAspiWDM” seems to be the reason of the conflict. I guess, it sends some specific control codes to the virtual drive, gets a “not supported” reply and aborts the device initialization sequence. Generally, a bug in InfraRecorder, BTW.
Anyway, I’ll install InfraRecorder on a VM and see what happens.Ok. As the combination of Mac + Windows 7 is quite rare and impossible for me to test, I won’t be able to fix it without any feedback.
If you or anyone else having the same problem find some more time to do the tests and submit the feedback, you are welcome 🙂Ok, what does the “batchmnt64 /list” command print, when such a “install failed” dialog is still active? BTW, you need to check the device manager while the dialog is still there (or just after; restarting will of course remove the device node for the virtual CDROM).
Ok, please go to the device manager (press Windows key + Pause key on the keyboard and select “Device Manager”), find the faulty CD-ROM drive in the list, right-click on it, select “properties”, look and post here the following information:
1. The text in “device status” box.
2. In “details” page, the “value” for:
a. Hardware IDs
b. Compatible IDs
c. Device Instance Path
d. Matching device ID—
It is important that “hardware IDs” will contain “GenCDRom. If it does contain it, but the driver still cannot be installed, do the following:
Select “start->run” or press “Windows key + R key”, type “regedit”.
Go to HKEY_LOCAL_MACHINE -> SYSTEM -> CurrentControlSet -> Control -> Class
Press “Ctrl+F”, type “cdrom”, press ENTER.
Ensure that the “{4D36E965-E325-11CE-BFC1-08002BE10318}” class was selected on the left.
Carefully examine the values on the right. If anything like “UpperFilters”, “LoweFilters” or anything else containing the word “filter” appears there, please either post the values here, or make a screenshot of your regedit window.Did the installer successfully switch your system to the “testsigning mode”? Maybe, BootCamp somehow prevents it? Do you have the “test mode/windows 7” message in the lower right corner of your desktop?
That is really wierd. I tested the latest version on Windows XP, Server 2003, Vista and Win7 both x86 and 64 and could not reproduce any problem Please check your system for viruses.
