Am I supposed to use ClamWinPortable.exe or is it nothing but a splash screen shortcut to ClamWin.exe? If not and I must use it, can I pass ClamWin.exe's command line parameters to it?
Thanks!
New: Supermium (Apr 11, 2024), Platform 29.4 (Apr 10, 2024)
1,000+ portable packages, 1.1 billion downloads
Please donate today
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
You are s'posed to use ClamWinPortable.exe, as it does launch ClamWin.exe, but it does various things to prep for it and clean up after it's done, as well as other usuability tweaks. For parameters, go copy Other\Source\ClamWinPortable.ini to the same directory as ClamWinPortable.exe, and in that file there's a line to put any paramaters called AdditionalParameters. The Other\Source\Readme.txt explains it too.
I see I can also use ClamWin.exe's command line parameters directly with ClamWinPortable.exe . Very nice.
But why can't I just set up some of the INI settings and use the defaults for others?
It would make sure I won't ever have to update the INI file if you ever release a new version with more/less/different INI settings.
For example, I just want it to have:
[ClamWinPortable]DisableSplashScreen=true
But what happens is that it ignores the INI file completely unless I give up and hardcode the other settings too.
Most portable/semi-portable programs (e.g. VLC, DOSBox) just use defaults for everything that isn't mentioned specifically.
but it´s said it will be changed within the newer ones, so just copy the whole .ini template from others/source and change the things you like to
"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
There's no need to remove the other lines. As wk said, it's the design of the launcher. All the other lines are the defaults as written in the code, so there's no problem just leaving them in there rather than doing a bunch of extra coding.
If in the future you'd add/remove/change even one line, than my whole INI file would be ignored.
But if you assume I want defaults for missing lines, my single aforementioned line will always work.
this site is work in progress and , of course, you´re right. Using a single file is more convenient. But it´s much easier for non geeks changing the defaults when they know which codes can be changed and how to. So, the template is made for thousands of people who want to change some of the default settings. advanced users like you will know when coding has changed at last when the .ini won´t work any more..;)
"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