Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
Is there such a thing as a standalone portable version without the MSI
Portableapps dot com or something similar would be excellent in environments
where administrative setups is impossible or if you want a lower profile
system deployment without big DLL registration or registry changes. It has
many uses. There should be a zip/7z binary version along the MSI under files
We're not providing a portable version, but it's not so hard to create one.
Extract the MSI, rename the MSVCRT DLLs to their correct names and add an
empty file called mumble.ini to prevent it from writing to the registry.
Extracted the MSI and got this error: missing DLL "libsndfile-1.dll"
What do you mean "rename MSVCRT" DLLs? Where are they and what is their
These are the contents of the MSI once extracted to a directory...
I've installed mumble in sandboxie. Extracted the files. Made Mumble.ini. It
seems to be working.
The installer tries to install files...
What are these files? What should I do with them?
msvcp100.dll and msvcr100.dll are the MS Visual C++ runtime libraries. They
should go in the Mumble directory in a portable version. The other files are
some Windows internal things and should be ignored.
Here is Mumble portable. Just extract and run...
I forgot about the Murmur server. Here is is if anyone wants it...
Extract the contents to your Mumble directory (overwrite files) and it will
take less disk space. But you can extract to another folder if you prefer.
For anyone using a portable Mumble, there is a small security issue you should
know about... http://sourceforge.net/projects/mumble/forums/forum/492607/topi
An official portable version (without security issues;)) would be great.
The "security issue" is intended behavior and won't change unless someone has
a better solution which doesn't require user interaction.
I tried to make a portable Mumble (I created a mumble.ini and renamed two
files to the required .dll names).
It generally works fine, but there seem to be some missing button icons in the
Any ideas? (If I install Mumble regularly the icons are not missing.)
Also, regarding the certificate backup file: is that the only thing that
"portable" Mumble leaves outside of its folder or is there perhaps something
The icon problem most likely happens because of incorrect file/directory structure. If you try to make mumble portable just by decompressing the contents of the .msi-archive all files will be in the root directory. Which is incorrect.
I suspect that Mumble won't be able to find plugins either.
The simplest way to figure out where the files actually go would probably be to install mumble and have a look.
But, to fix the icon issue simply put qsvgicon4.dll in .\QtPlugins\iconengines\
(Edit: Sorry about the bump, but this thread is the #1 search result for mumble portable).
I've created a portable version of mumble 1.2.5 by extracting the mumble.msi, moving the dll file into the mumble folder, and created a mumble.ini file.
Then I opened mumble.exe, added my server info and made a new username (e.g. musicbot), then I tried to login to my mumble server. Unfortunately, it said:
"Sever [sic] presented a certificate which failed verification.. The Specific errors with this certificate are:
1. The host name did not match any of the valid hosts for this certificate
2. The certificate is self-signed, and untrusted
Do you wish to accept this certificate anyway?
(It will also be stored so you won't be asked this again.)
[Yes] [No] [View Certificate]"
Clicking No prevents me from signing on. Clicking Yes unfortunately uses my main username/password/etc. from my installed mumble.exe instance and kicks me off if I am already logged in (since it's using the same certificate). (Just to mention, I own the mumble server and am completely okay with people logging in under two names with one computer).
The point of the portable mumble is to have two mumble instances running with two different names (one for me, one for a bot). I thought creating a mumble.ini in the portable will force it to create a certificate folder for itself.
How can I use the portable mumble and make it unique so it has its own certificate?
Assistance would be greatly appreciated!
Are you sure the file is called mumble.ini and NOT mumble.ini.txt (Type Textfile)?
Yes, I'm sure - Type of file: Configuration settings (.ini)