Forum Replies Created
-
AuthorPosts
-
AnonymousParticipant
@bazis wrote:
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.No faulty CD shows up in my Device Manager. I believe one of the problems is that when I double-click an .iso file to mount it, my computer tells me it is installing device drivers for it (like the original poster to this thread), but it never finishes the install, and it eventually times out with an error (see screenshots above).
AnonymousParticipant@bazis wrote:
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?
Yes, my Windows is in Test Mode.
Tim
AnonymousParticipantSame exact thing happens with my machine. Tried the “fix” instructions with no results too. I am running Windows 7 Ultimate x64 on a 27″ iMac through Boot Camp. Was running Daemon Tools with no issues whatsoever, and uninstalled it to try this program out. Any clues?
Tim
AnonymousParticipantHi,
I have similar problem.
W2K8 Srv (32bit) + VS2008 + WDK 7600.16385.1
Tryin to setup Visual DDK 1.5 -> the setup fails to configure VisualDDK, tellingVisualDDK has not detected either WDK or DDK.
Well, setting the path manually won’t help
What the clue?
Thx in advance
AnonymousParticipantThis update (3.1.1) did not help. During the install, a warning popped up saying that it could modify something in the registry. Re-running the installation with Administrator privilege, the error message still appeared. (I dare not try to run this install again–see rest of message.) I mistakenly assumed it worked, so I gave ISO mounting another try… did not work, again. Hung on shutdown. This time, on reboot, the system detected that it is NOT GENUINE WINDOWS OS (Windows 7 Home Premium). Then, Microsoft Essentials complained about it after login. Unfortunately, I cannot tell what is going on because the system logs don’t seem to have anything apparent.
This software needs work. I might suggest that when installing or uninstalling, please create a log file of every single file, directory, registry change, and a backup if you change anything. That way I can go through and understand why install/uninstall/mount failed and how to undo changes to my system. Also, please use the event logger to log problems when mounting an ISO. Unfortunately, I now need to fix my system because I don’t trust this software at all: scan with multiple AV programs to see if this software injects anything, run diskchk to see if it trashed my FS, look for rootkits, recover any system files changed, manually go through regedit and fix leftovers, etc. A lot of wasted time…
I used to run PowerISO (worked fine), but I uninstalled that before trying this software. Going back to PowerISO and will wait a while before trying this software again…
AnonymousParticipant@danielkza wrote:
I was not able to reproduce the issue in Windows 7 x64 RTM: I copied the exact same file to my hard drive successfully. I can test it in Vista SP2 x86 later if it would help.
danielkza, thanks for trying this. I retested this multiple times on 4 different clean systems, here’s what I found:
WinXP Pro x86 – works
WinXP Pro x64 – fails
Win7 Pro x86 – works
Win7 Pro x64 – worksFigures the OS/architecture I’m running is the one with the problem. 😕
I tried to debug this problem, however despite multiple tries I cannot seem to compile the driver. I have several crash-dump files but they are not very useful without symbol files. Is there a way to get symbol files for 3.1 x64 Release binaries? If someone else would like to analyze the crash dump files shoot me an email. Or, if you have the PDB files for 3.1 x64 either Debug or Release please email me. My email is brian_friesen[_at_]yahoo[_dot_]com
AnonymousParticipant@danielkza wrote:
I think you could probably work around this.
1) Replace the file association with one running a custom script that would save the mounted ISO to the registry, and call the original executable afterwards.
2) Run another script on logon that loads the previously saved ISO list.In fact, it would be better if it was included in WinCDEmu itself: I’ll what I can do about it (isn’t free software great?) soon.
I’m not knowledgeable enough to create a script, but I appreciate your response and I’m glad to hear you’re going to look into it 🙂
AnonymousParticipantGuess not 🙁
AnonymousParticipantAnyone?
AnonymousParticipantIt is my suspicion that VisualDDK can’t work with the Express editions, though the error you got is hardly conclusive: since the Express Editions for the various languages do not integrate with one another, they do not use the shared “devenv.exe” that the more expensive versions use — each Express Edition has a seperate .exe for its development environment, e.g. C:Program FilesMicrosoft Visual Studio 9.0Common7IDEVCSExpress.exe for MSVC# 2008 Express. (I’m on a campus computer and that is the only one I have installed today, okay?)
The reason I came on to the forum was to look for a definitive statement one way or the other, and to suggest that it be mentioned on the webpage whether or not it can work with MSVC Express.
AnonymousParticipanti’m waiting code signed new version.
when do you release ?AnonymousParticipantI have the same issue. (WinCDEmu-3.1-8lang/XP Pro SP3/Dell Latitude D630) New Hardware is found. Tries to install the new hardware, then hangs. The “new hardware icon” stays in the taskbar and no corresponding drive letter shows up.
AnonymousParticipantHi
I cant see none of the VisualDDK debug commands in Visual Studio 2008 or 2005 Debug menu. I’m running W7 64 bits, WDK 6001.18001, Visual Studio 2005 and 2008 Team System with Whole Tomato Visual Assist X.
I could create a VisualDDK project, but cannot debug. Must I install WinDbg?Thank you.
AnonymousParticipantthanks for the reply. I will look forward to future versions. Great tool.
AnonymousParticipantTo make it work correctly. I actually had to do the following:
“Project Properties -> NMake -> Build Command Line” and insert “x64” before “Win7”.
-
AuthorPosts