Forum Replies Created
-
AuthorPosts
-
AnonymousParticipant
Hi,
Thanks for the response. I’m using VisualGDB-4.3-trial and have installed in both 2008 and 2010 VS versions but both only give me ‘Empty Project’ in the dropdown for a Linux project. I have Qt installed as I use Qt Creator for building the project for Windows. I saw something about installing Qt for MinGW. I have MinGW installed but wasn’t sure if I needed to do anything extra.
Bob
AnonymousParticipantfeature request:
– WinCDEmu support to mount ISO with CDAUDIO tracks.AnonymousParticipantbumping this.
Bazis don’t let us down. I really need a UI-Less parameter with CreateISO.
AnonymousParticipantmy request is… if you can improve the installer, in order to no install x64 files versions when you install in a x86 Windows version, because it cause some issues in event logs like:
Activation context generation failed for "c:program filesWinCDEmuvmnt64.exe". Dependent Assembly Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0" could not be found. Please use sxstrace.exe for detailed diagnosis.
AnonymousParticipant@bazis wrote:
* Registry cleanup for portable driver uninstallation. Simply could not reproduce it. If you can share exact repro steps, I’ll look into it more
Is easy to reproduce:
a) Use a software for making a registry compare like Regshot
b) Start WinCDEMU Portable and install the driver
c) Mount an image <-- Important, i have Mount an ISO
d) Unmount-Uninstall the driver
e) Compare previous-after registry key with RegshotAs you can see, the software leave traces, example here:
Other keys was already posted, but just for complete information are:
HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesBazisPortableCDBus HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBazisPortableCDBus HKEY_LOCAL_MACHINESYSTEMControlSet001EnumRootLEGACY_BAZISPORTABLECDBUS HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumRootLEGACY_BAZISPORTABLECDBUS
My test machine is Windows 7 x64 on a clean VM
AnonymousParticipantSo basiz, will the /CreateISO Parameter reach it into the command line 😀 ?
AnonymousParticipantThe portable version can have the /CreateISO in the commandline? Thanks
AnonymousParticipantI missunderstood that, sorry.
Still, this is a feature request thread and that’s what I was expecting from your post.AnonymousParticipantUh? Edit the resorce don’t compromize anything and there is nothing to fix. If basiz what to make the software multilanguage without additional file there are two ways, compile the software by ourself or edit the resource of the executable, that’s all.
AnonymousParticipantI think that the “problem” with the language files isn’t anything that needs to be fixed asap.
You just shouldn’t touch it if you want it to do its work.AnonymousParticipantAbout the traslation, everyone with a resource editor without any programming knowledge can change the label of the button but there are some part missing in the DIALOG resource, like:
or
or Drive – Image of the Listview ( Basiz everyware 😆 )
Maybe other, dunno. If you add all the phrase in the DIALOG resource of the executable you don’t need to add any other saparate file for the language
AnonymousParticipantBasiz the output of the commandline in the portable version is in a wrong position,, check it out:
The line “The driver is already installed” in theory must be:
C:>PortableWinCDEmu-4.0-beta1.exe /install
The driver is already installed
C:>
P.S. Is not only that line, every output is in a wrong position 😉
AnonymousParticipantIt’s great so far!
I tested the vmnt.exe to create an ISO with the command line and also the batchmnt works fine, but I miss something.First of all: Why didn’t you release the Source Project Files?
And you also did’nt modify/recreate the createiso parameter of vmnt.exe.When I type “vmnt.exe /createiso F” it opens up a graphical interface which wants me to chose a destination folder and a file name.
I would like to have it without that interface so you can just generate it like this:/CreateISO F C:NewDirectoryFinalName.iso
F = my physical drive
C:NewDirectoryFinalName.iso = my destination path and filenameAnonymousParticipantas long as he doesn’t forget our requests
AnonymousParticipantGreat! I can’t wait! 😀
-
AuthorPosts