Forum Replies Created
-
Posts
-
I hear this for the first time also. Moreover, knowing what does the installer modify, I cannot name a single reason, why should it be like this. You can try the TweakUI tool from MS to rebuild various explorer caches and manage icons, if that helps. Additionally, try uninstalling WinCDEmu and seeing whether it affects the icons.
If that helps, here is the script that modifies the registry during WinCDEmu installation (as you can see, it does not change anything related to “my computer”):
$registry createkeyb HKCRApplicationsvmnt$64_OR_VOID$.exeshellopencommand 3264 setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1"" createkeyb HKCR.iso setstrdef BazisVirtualCD.Iso createkeyb HKCRBazisVirtualCD.Iso setstrdef "ISO CD/DVD image" createsubkey DefaultIcon setstrdef %SystemRoot%System32shell32.dll,11 createkeyb HKCRBazisVirtualCD.Isoshell createsubkey open createsubkey command setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1"" createkeyb HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.iso setstrsubst Application vmnt$64_OR_VOID$.exe createkeyb HKCR.cue setstrdef BazisVirtualCD.Cue createkeyb HKCRBazisVirtualCD.Cue setstrdef "CUE CD/DVD image" createsubkey DefaultIcon setstrdef %SystemRoot%System32shell32.dll,11 createkeyb HKCRBazisVirtualCD.Cueshell createsubkey open createsubkey command setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1"" createkeyb HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.cue setstrsubst Application vmnt$64_OR_VOID$.exe createkeyb HKCR.img setstrdef BazisVirtualCD.Img createkeyb HKCRBazisVirtualCD.Img setstrdef "Binary CD/DVD image" createsubkey DefaultIcon setstrdef %SystemRoot%System32shell32.dll,11 createkeyb HKCRBazisVirtualCD.Imgshell createsubkey open createsubkey command setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1"" createkeyb HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerFileExts.img setstrsubst Application vmnt$64_OR_VOID$.exe createkeyb "HKCRBazisVirtualCD.IsoshellSelect drive letter && mount" createsubkey command setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1" /ltrselect" createkeyb "HKCRBazisVirtualCD.CueshellSelect drive letter && mountcommand" setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1" /ltrselect" createkeyb "HKCRBazisVirtualCD.ImgshellSelect drive letter && mountcommand" setstrdef ""$DESTDIR$vmnt$64_OR_VOID$.exe" "%1" /ltrselect"WinCDEmu installer registers its program folder in “Start” menu and that causes it to reload. I mean, if something messed up the settings before, installing WinCDEmu just caused explorer to re-read all settings & make the problem visible. Ok, can you clearly describe what exactly has changed? Which icons appeared where? It is not completely clear from your previous posts. Maybe, I’ll have some suggestion.
WinCDEmu does not add any icons or shortcuts apart from its own group in the start menu. Maybe, your problems are due to unclean shutdown, or some other software? The only rarely happening problem related to icons is that when you unmount a disk image (e.g. V:) and mount a new one to the same letter, explorer can continue using the old icon for that. However, this has nothing to do with WinCDEmu. If you are not sure, try disabling “Virtual Disk Enumerator” device in the Device Manager and checking whether the problem persists.
Actually, I was recently contacted by a guy planning to port VirtualKD to Linux VM host (redirecting connections to WinDbg via TCP/IP). I have no clue whether he has any success with that, however, I can forward him your e-mail. Maybe, you can join your forces to make it work on Linux 🙂
In such case, VirtualKD won’t work. It requires a Windows host machine, simply, as WinDbg runs only on Windows. Running VirtualKD without having WinDbg on the same machine would make no sense.
Ok, the solution is simple. VBoxDD should be replaced on the HOST machine, not on the GUEST. It allows the host-side part of the VirtualBox to handle the requests from the OS. Guest-side modifications are performed automatically by VMInstall.
Ok, VisualDDK setup checks the validity of WDK path in the following way:
The file %WDKPATH%incddkntddk.h should exist. %WDKPATH% is the path you enter in the setup window. Please check that the file exists on your machine and that you are entering correct path.
Visual Studio Express does not support building ATL applications. So, some user-mode parts of BazisLib and some other stuff will not be functional. Otherwise, should work.
You need BazisLib for that. It comes with automatic installer, so all paths will be set up automatically.
P.S. The only answer to the question ” some header file not reading” could be “you should add something somewhere”. Next time, please specify the exact error message, so I can provide a real answer, not just a guess 😀Sure, use the SourceForge download page here:
http://sourceforge.net/projects/wincdemuProblem is that the .BIN extension is not only used for CD/DVD images and registering it by default is not the best idea. However, in the future versions I’ll most likely add a non-default context menu command for it (present version of installer does not support it).
DVD disks with DVD movies include additional protection stuff, that is not emulated by WinCDEmu. That’s why some programs see the drives as CD.WinCDEmu is not targeted to be a protection emulation software, it is a quick and simple image mounter, not more.
You don’t need to reinstall the OS. Just install another application that will associate itself with ISO files and that’s it.
Testsigning should be always on. Otherwise, only drivers signed by MS partners can be loaded. As for the missing file, could you please see the name of the executable, that reports “cannot find driver”? It can be done in the task manager by selecting the task and clicking “go to process”. It should be 64-bit vmnt64.exe. The BazisVirtualCD.sys driver should be also present in SYSTEM32DRIVERS.
