Ok, tried the "copy installed version files, and run from separate directory" option and failed.
I installed the stable version of chrome (into %user%\AppData\Local \Google\Chrome) and then moved the files to a separate folder (c: \chrome\Stable) Added a batch file: start C:\chrome\Stable\Application\chrome.exe --user-data-dir="C: \chrome\Stable\Application\User Data" and it ran fine with the exception of the update mechanism failing (as expected). I then did the same with the beta channel, and it too worked fine. However when I tried to run the Stable version it failed completely. I can only assume there's a registry entry that chrome.exe looks for to make sure it's running the correct executable. But all the paths have changed so the registry entry must contain a unique id, or hash, of the executable to run :( I don't really want to go down the separate windows users accounts path (logging in and out just to test a feature is a hassle (yes, I'm lazy)). So it looks like the only solution is the build (chromium) from source suggested by Meok. I found the pre-compiled chromium builds at http://build.chromium.org/buildbot/snapshots/chromium-rel-xp/, but alas they don't appear to have the builds I need (chrome-dev 4.0.266.0 == chromium build 34023, but build-bot only has 34018 and 34025, both of which are marked as 4.0.267 in the about dialog). Does anyone know where I can get precompiled builds of chromium that match the released version of chrome? - karl -- 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.
