Some Notes on the Machines

Several fixes, some of them most interesting:

https://www.guidingtech.com/fixes-for-chrome-not-opening-on-windows/

Number 4 on that page, is most surprising, and often functional with new build upgrades.

Recommended by the amazing Yvonne Wynkoop.

Condensed from here: https://support.google.com/a/answer/2589954?hl=en:

• google.com
• googledrive.com
• google-analytics.com
• googleapis.com
• googleusercontent.com
• ytimg.com
• gstatic.com

The above are all on port 443, HTTPS, only. There is a legacy product which uses talk.google.com on port 5222, XMPP.

Here are some tools:

http://support.atmail.com/display/A7DOCS/Outlook+CalDAV+Synchronization+Setup

If Google Chrome fails to load any web page, giving the “aw snap” after a few minutes, try adding this to the shortcut:

–-no-sandbox

Unfortunately this is not a fix, but a way to prove the problem — the problem is malware.

Add the following to all shortcuts, before the %U:

--disk-cache-size=1

and also add the above to this registry key:

HKEY_CLASSES_ROOT\ChromeHTML\shell\open\command

On lower-powered PCs, CPU not necessarily RAM, this can prevent Chrome from locking up the PC to do cache cleanup. And it does speed up Chrome a lot — in fact, as long as one has 2G RAM or so, this seems like a good idea in general.