No. Not without hacking the registry every time, anyway. ☆PhistucK
On Thu, Dec 24, 2009 at 10:28, demiurg <sasha.sirot...@gmail.com> wrote: > I'm trying to do just that, i.e. I installed Chrome 4, copied "Local > Settings\Application Data\Google\Chrome" to a different directory, > than removed it and reinstalled Chrome 3 to its default location. Now > Chrome 4 won't run from it's new location... unless it is installed in > it's default location. > > So... after all, is it possible to have Chrome 3 and 4 installed on > the same PC (Windows) or not ? > > On Dec 17, 12:17 am, dhw <dhh...@gmail.com> wrote: > > Actually, in Windows, you cannot install official Google Chrome into > > different directories. That is this bug:http://crbug.com/141- Installer > doesn't ask about installation > > destination > > > > However, it is true that after installation, Chrome runs from its > > directory independently of other software. > > > > So of course you can download Snapshots or Continuous builds into > > their own separate directories and run them, or you can run self > > compiled versions. > > > > But if you want to run official Google Chrome Beta and Dev together on > > Windows, you need a workaround: Run the Beta or Dev installation as > > normal, then copy the Application Data\Google\Chrome\Application > > directory somewhere else to save that copy. Then run the other > > installation and save that directory. > > > > Then you need to make program shortcuts using the --user-data-dir > > option as mentioned by Greg Oliver. You will need these 2 shortcuts: > > (1) c:\path\to\beta\chrome.exe --user-data-dir="c:\path\to\beta > > \profile" > > (2) c:\path\to\dev\chrome.exe --user-data-dir="c:\path\to\dev\profile" > > > > On Dec 16, 1:50 pm, Greg Oliver <oliver.g...@gmail.com> wrote:> On Wed, > Dec 16, 2009 at 3:46 PM, karl <k...@interclue.com> wrote: > > > > I'm developing Lazarus:Form Recovery for chrome and find I need to > > > > test it on the beta channel of chrome as well as develop on the dev > > > > channel. At the moment I'm having to resort to running the beta > > > > version in a Virtual Machine and using the dev verion to develop on. > > > > > > In my ideal world I would be able to: > > > > * Have separate chrome executables for dev, beta, and stable builds > of > > > > chrome. > > > > * Have one or more separate profiles for each of the executables > > > > (profiles should not be shared between channels) > > > > * Each channel should update normally via the google update exe, so > > > > that I keep the latest version of each. > > > > > I do it with Linux, just by having them installed in different > > > directories using different home directories for each.. > > > > > Google Beta, PPA for dev Ubuntu and self compiled all operate > > > independently no problem. I assume you can install them all in > > > different directories in windows and start them each with different > > > --user-data-dir= the same way...?? > > -- > > You received this message because you are subscribed to the Google Groups > "Chromium-extensions" group. > To post to this group, send email to chromium-extensi...@googlegroups.com. > To unsubscribe from this group, send email to > chromium-extensions+unsubscr...@googlegroups.com<chromium-extensions%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/chromium-extensions?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
