Well, allright. I will first start with a little introduction. I am a great fan of Portable software, as not everyone has the software I use. I use it mostly for school and everything was fine until about a year ago.
What happened was that they installed a program which blocks all executables except those on a whitelist. Off course we immediately searched for a solution and we found one.
The solution was to change .exe to .cmd and that worked fine. I can change the launcher to .cmd and that part works. However, the launcher then tries to launch the main executable, but cannot find it (it cannot find firefox.exe for example). This is I think because firefox.exe had to be changed to firefox.cmd.
I already changed the configuration file (the .ini), but that didn't work. Does anyone know how I can get this to work? I am quite technical, so don't hesitate to use difficult techniques in your answer.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
should have read more carefully....
"Lorem ipsum dolor sit amet, consectetur adipisici elit, sed eiusmod tempor incidunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis .." Friday Next -
"May The Schwartz be with You!" Yogurt the Yoda
That can happen. Everybody makes mistakes. But I read once, I do not remember the source, that Firefoxportable worked by using the profile switch. If somebody could tell me exactly how it is done, I could perhaps create my own launcher. Ubless omseone knows how to make it work with the normal launcher.
I was curious so I tried this with the latest release, 3.0.5, and it works perfectly just like you described you wanted. Can you post the content of your FirefoxPortable.ini file? Is it in the same directory as the launcher?
It does not seem to work with me. Note that I need to rename the launcher and firefox itself (so FirefoxPortable.exe -> FirefoxPortable.cmd and App\Firefox\firefox.exe -> App\Firefox\firefox.cmd).
This is my FirefoxPortable.ini:
[FirefoxPortable]
FirefoxDirectory=App\firefox
ProfileDirectory=Data\profile
SettingsDirectory=Data\settings
PluginsDirectory=Data\plugins
FirefoxExecutable=firefox.cmd
AdditionalParameters=
LocalHomepage=
DisableSplashScreen=false
AllowMultipleInstances=false
DisableIntelligentStart=false
SkipCompregFix=false
RunLocally=false
# The above options are explained in the included readme.txt
# This INI file is an example only and is not used unless it is placed as described in the included readme.txt
It gives an error saying that I should reinstall it and then '(Error: firefox.exe not found'.
exe files are not made to be called cmd files. cmd files are batch files with a different structure. What you are doing is of course going to produce a lot of errors. you need to rename back to exe.
your friendly neighbourhood moderator Zach Thibeau
Well, renaming them to .cmd does acutally works for most programs. What happens, is that it is openened by cmd.exe. cmd.exe recognizes that it is in fact not a batch file and knows it's an exe and executes it.
The problem with making it .exe again, is that it triggers the exeblocker. So I just want the launcher to run the cmd file.
but I would assume that the launchers are coded in such a way as to call exe files specifically, and that to make the launcher word with a cmd file, you would need to change the code and recompile the launcher.
I made this half-pony, half-monkey monster to please you.
Yeah, I already expected an answer like that. I thought it would probably be an security mechanism from PortableApps. But if that is what it takes, I will recompile it. Where can I find the source code of the launcher?
usually in the other/sources directory/folder
your friendly neighbourhood moderator Zach Thibeau
But I TESTED this, and it worked. I renamed everything to .cmd, launcher and executable, and changed the INI. It worked just like normal. FF Portable 3.0.5.
Where did you put the INI file after editing it? Do other INI options work, like disabling the splash screen?
Strange. I checked it once again, and it just did not work. I will try if editing the INI options works at all.
I've tried asking a couple times...WHERE are you placing the edited INI file? This is a very important piece of information.
Did you put the INI in the same location as the launcher? If not, try it.