This is a bit like the problem I had with netbeans; chrome default installer puts a lot of stuff - including the executable - in your user directory. On my work laptop, that's profile space. And some genius decided to put a quota on profile space... therefore, merely installing chrome will fill the quote, and result in a million and one pop-ups and errors.
Google provide a nice alternate installer - and there they describe how you use this to install it for multiple users. If you're not a machine with multiple user accounts, you may not consider the need... In fact, the alternate installs to Program Files (sensibly), so every account can use it, but as a side affect, it stops filling up your individual profile.
A loose collection of helpful stuff that i've found while solving day to day problems. [March 2016] You may have noticed I haven't posted updates for a long, long time. Curiously, I still get the odd comment on a post that's 7 years old, so i'll leave this little lot here and not delete it.
Showing posts with label chrome. Show all posts
Showing posts with label chrome. Show all posts
Friday, June 22, 2012
Tuesday, August 25, 2009
Google Chrome, Google Desktop & corporate proxies
So, my work internet proxy configuration (c/o Windows control panel..) doesn't allow localhost access. Which means Google Desktop doesn't work with Chrome, since Chrome uses the Windows internet configuration.
Solution#1 - simply update the Windows proxy configuration to ignore the automatic config (via PAC file) that work gives me, and manually configure the same proxy but add an exception for localhost. That works.
Then some BOFH decides to push out the proxy configuration (somehow - XP profile?) much more frequently than they were. Such that every hour or so, my lovely manual configuration of Chrome (ie the Windows one) is reset to use the automatic (no localhost!) proxy configuration.
Solution #2 - use Firefox as default browser, since this (in a sensible fashion) lets me manually set the proxy configuration just the way I like it.
Oh, and the Chrome command line switch (--proxy-server=proxy:port) doesn't work either - can't manage the exception for localhost, and thus Google Desktop.
Solution#1 - simply update the Windows proxy configuration to ignore the automatic config (via PAC file) that work gives me, and manually configure the same proxy but add an exception for localhost. That works.
Then some BOFH decides to push out the proxy configuration (somehow - XP profile?) much more frequently than they were. Such that every hour or so, my lovely manual configuration of Chrome (ie the Windows one) is reset to use the automatic (no localhost!) proxy configuration.
Solution #2 - use Firefox as default browser, since this (in a sensible fashion) lets me manually set the proxy configuration just the way I like it.
Oh, and the Chrome command line switch (--proxy-server=proxy:port) doesn't work either - can't manage the exception for localhost, and thus Google Desktop.
Subscribe to:
Posts (Atom)