First off, I did a search & did not come up with an answer (though I suspect that there was one buried in there some where).
I'd like too be able to start Chrome portable with a 1 of 2 .ini's which have different Additional Parameters. I know I can edit GoogleChromePortable.ini with the appropriate parms. But I'd like to void having to do the edit when I want to start the app with different parms.
One way I got around the problem was to have Chrome installed in 2 seeperate directories with 2 separate GoogleChromePortable.ini. BUt that seems like the sledgehammer approach. Is there another way?
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
However, if you want to use the same data, you can edit one of the INIs to point the the data of your main installation, so that you don't have multiple profiles.
That's what I thought. Thanks for the reply.
If you place a second GoogleChromePortable install in another folder (e.g.
X:\PortableApps\GoogleChromePortable2ndProfile), add aGoogleChromePortable.inifile and edit it as follows:Then You can delete the
…2ndProfile\App\Chrome-bin,…2ndProfile\App\DefaultData,…2ndProfile\Data, and…2ndProfile\Otherfolders, and I think it'll do what you want with minimal overhead (I'm guessing 300-500 KB).Note: and if you want to use a second profile, then you could leave the
ProfileDirectoryline as:Let us know if this works for you.
~3D1T0R
Thanks 3D1T0R. That is exactly what I wanted to do.
Sweet, Glad it worked.
However I don't know how often the GoogleChromePortable Launcher itself actually gets updated, and you're effectively using the launcher from whatever version you copied the GoogleChromePortable.exe from, so I'd recommend copying the GoogleChromePortable.exe over from your standard GoogleChromePortable installation to your 2ndProfile (or whatever you called it) [partial] installation when GoogleChromePortable gets updates.
~3D1T0R
You also need to update App\Appinfo as well, as the launcher needs that directory to run.
It might be a good idea to keep the
App\AppInfodirectory up-to-date as well, butAFAICTthe Google Chrome Portable launcher doesn't use it, so it shouldn't be necessary; in fact it might be a good idea to change theApp\AppInfo\appinfo.inifile to something resembling the following:That way if an official(Never mind, the current Updater exclusively uses the FolderName as the AppID, so changing theGoogleChromePortable2ndProfileever gets released (and added to thePortable App Directory™) it can be updated to it from the PA.c Platform's Updater.appinfo.inifile won't make or break the ability to Update, but you could still change it if you want. [Just 'cause it's cool? maybe?])~3D1T0R