Forum Replies Created
-
Posts
-
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.
Which OS version did you select in the wizard? Maybe, the selected OS does not have support for x64 target? Try selecting the latest one (Windows 7).
Do you have any cd burning software installed? Something that can interfere with CD drives?
As for the uninstall, I have fixed it in WinCDEmu 3.3-1. Just download the updated file and install it over the old one. Then the uninstall will work.
http://sourceforge.net/projects/wincdemu/files/wincdemu/3.3/WinCDEmu-3.3-1.exe/downloadNot yet. The explanation is on the main page. Basically, issuing code signing certificates to individuals rather than companies is not a “usual practice”, so it takes time to negotiate things.
Please close WinDbg before you start debugging with VisualDDK. You cannot debug the same kernel using 2 debuggers in parallel!
Obtaining a certificate takes time when you are not a company. Unfortunately, this process is quite buerocratic. My best hopes are for the mid-April.
Yes, boot your VM in debug mode and create a snapshot. Then, every time you need to debug anything, just revert to that snapshot et voila!
You can always change the DLL path by selecting Tools->VisualDDK Options in Visual Studio.
BTW, does the 1394:// prefix work correctly?No, but you can try redirecting the host-side named pipe to the other VM using the GuestRPC protocol (http://articles.sysprogs.org/kdvmware/guestrpc.html). (You’ll need to modify the sources)
