Forum Replies Created
-
Posts
-
There is no blank areas such as you describe. As I have already mentioned there is even no “DDK Console” menu item in Debug|Windows menu. Maybe somehow it failes to load? Is there any log file I could review?
Hi there,
We need to be able to mount ISO fies from a DFS (Distributed Files System) UNC path.
At the moment WinCDEmu copes well with regular UNC shares such as \servershare…, but seems to be unable to handle DFS pathes – niether using domain FQDN (e.g., \my.domain\namespacedfsroot…) nor NetBios (\DOMAINNAMEnamespacedfsroot…) – both fail with an error. Note that both DFS path formats (doman and netbios) work perfectly well for all other needs such as windows explorer, vbscripts, etc. We’re using Win2008 DFS with WinXP/SP3 clients.
For the time being I’ve bypassed the problem by first mounting the DFS share on a logical network drive (“net use”) and then mounting WinCDEmu from the logical drive (which works okay), but it seems preferable that WinCDEmu cope with DFS pathes by itself.
Thanks,
Uri.Thanks for the quick reply!
When do you expect this newer version to become available?Much obliged,
UriSame problem exactly. ISO does not mount after drive name prompt. Cannot uninstall – uninstaller stops after asking confirmation. Cleanup program runs, says cleanup completed, but full installation remains. Running Windows XP SP3. Help!
Same for me, running Window 7 Prof 64. It actually does someting, windows recognizes a driver install for some cdrom, but this fails. Now I do not get it uninstalled, the uninstall procedure runs but the context menu has still the entry “mount …”. Yes, I did run the cleaning tool as well, rebooted, no effect.
Well, I don’t have a COM cable and also I don’t have any virtual machine on my PC installed. I have UAC turned off and I am running as a member of local administrators group, so I think that there should not be problem with the privileges.
From the windbg I can connect to the target using both the command line (windbg -k 1394:channel=10) and the GUI.
I’ve checked that, but I have correct path to the debugging tools – it’s the same path where the windbg resides (C:Program FilesDebugging Tools for Windows)Martin
Hi!
I have done what the “bcecedit -set …” and the text on the right bottom has gone, but the desktop icons still aren’t visible. I got that bug on Win7 RC, but never knew how to solve it. Now I know what was the cause o the problem but still need help to solve it.
Any more ideas?
Thanks for your help, I appreciate it a lot.
Sorry if I’ve somewhat high-jacked the thread from Windows 7. But all the symptoms described by chrysalisx were the same on my Vista (Home Premium, SP2), plus the blue screen at shutdown.
I was able to get v2.3 to work though.
Then I saw this thread:
http://forum.sysprogs.org/viewtopic.php?f=3&t=115although it is a bit different in that the blue screen only comes up when Windows is shutting down.
That’s when I remember that my system came preloaded with a bunch of Roxio apps. After removing those programs, v3.1 is now working on my Vista.
I’ve installed on the target host vminstall.exe, and I was booting with the way the above…
but still problem…. 😥
Answer is to go into the registry under:
HKLMSOFTWAREBazisSoftVisualDDKDDKDebuggerParameters (add Wow6432Node before BazisSoft if you are 64 bit)Find the “DebugToolsPath” and make sure its set to the correct folder.
C:Program Files (x86)Debugging Tools for Windows (x86)It would be good to have it not allow the selection of the 64 bit debug dll (just try to load it under 32 bit context at selection and if it fails, dont allow)
Or remove that key when you uninstall (as it was being left behind as residue after uninstall).Tanks for suggestion bazis,,,
I’ve rename vboxdd.dll to vboxdd0.dll in virtual box directory and I’ve copied the vboxdd.dll from visualddk to virtualbox directory, but still problem…
