2012-01-23 05:49
	1. You need to create this folder for Internet Settings proxies now:
	   %SystemDrive%\etc\OneFile\
	   - Usually this is:
	   C:\etc\OneFile\
	2. These scripts have been altered to do this for you:
	   AutoPac_EN.sh
	   AutoPac_FR.sh
	3. They also copy the proxy_en.txt and proxy_fr.txt files
	   respectively that are downloaded with the previous scripts.
	4. You MUST reset your Internet Settings to one of these, which
	   ever one you use:
	   file://%SystemDrive%/etc/OneFile/proxy_en.txt
	   file://%SystemDrive%/etc/OneFile/proxy_fr.txt
	   - Usually this is:
	   file://C:/etc/OneFile/proxy_en.txt
	   file://C:/etc/OneFile/proxy_fr.txt
	5. The reasons for this are two-fold:
	   - Microsoft through a patch in late 2011 has made it so that
	     EVERY file in the folder is parsed, not just the one that
	     is specified.
	   - The Google Chrome browser has something wrong with its
	     JavaScript and can NOT determine to leave things alone
	     when the debug variable is set to debugNone.  This may
	     be only their fault but is more likely a shared
	     responsibility of both Microsoft and Google's Chrome
	     Windows team.  I have NO problems with Chrome on Linux.
	     Accordingly, I stripped out ALL debug affiliated lines
	     out of the proxy_en.txt and proxy_fr.txt
	6. I would love to say this completely fixes the problem.  The
	   sad fact is, it does NOT fix it immediately.  I keep getting
	   a "proxy pac file loaded" message even though it is gone.
	   Evidently, Chrome keeps caching it until its next update.
	   After a while (read, probably after Chrome updates) this
	   message seems to go away.  All I know is that it is NOT
	   in either proxy_en.txt or proxy_fr.txt any more.
	7. Because of these problems I am now also signing the
	   dbgproxy_en.txt and dbgproxy_fr.txt files since they are
	   no longer the same as the proxy_en.txt and proxy_fr.txt
	   files except for just the value of the debug variable.