New Way Of Handling Hosts File On Windows
Somebody wrote to me saying that my hosts file installer is no longer suitable for Windows Vista, 2008 Server, Windows 7 or if you are crazy enough to use it there - Windows 8.
This is absolutely correct. The UnxUtils way of using my hosts file on a Windows system is only for Windows XP and for use with something like Homer to act as a pseudo HTTP server (phttpd). The reason I don't provide anything else is because I depend on somebody else's program to handle incorporating my hosts file on Windows 7 systems now.
If you use Windows 7, use Alex Kowalski's hosts file maintainance program which I provide download space for. Here is the Hosts file page which shows where the links are:
Hosts File Page
Down at the end you see these two links:
APK's 64/32 Host File Engine Program
APK's 64/32 Host File Engine Instructions
My hosts file is primarily used by Linux people. They use dnsmasq, Marco Peereboom's adsuck program or similar. I am the only one using my phttpd. But all of these people expect the hosts to be remapped to 127.0.0.1. There is no 0.0.0.0 on Linux like there is on Windows. On Windows 0.0.0.0 is normally used as an inter-process server. On Linux and Unix they use a special file construct called pipes for processes to communicate with each other.
Will I remap the entries to something else other than 127.0.0.1? No. I depend on Alex Kowalski's program to do that for me. The reason I mention this is because somebody wrote to me about this 4chan comment on hosts files (which you will note has Alex Kowalski's comment - APK):
4Chan comment on hosts files
What is my statement on using 0 versus 0.0.0.0? I defer to Alex Kowalski on that issue since it is his APK 64/32 Hosts file engine that automatically does the conversion from 127.0.0.1 to what ever he uses. Frankly I am surprised somebody wrote to me about it. You can NOT use my shell file to install a hosts file on anything newer than Windows XP anyway. Even if you give the script a temporary over-ride you have lots of programs like wget, rm, etcetera, the script calls that do not have the over-ride. IOW, attempting to use my script file on Windows 7 will fail. Even if you can seem to get it to work (I couldn't) use APK's Host File Engine Program instead. His program does much more than just install a hosts file. I will say you must use some other AV program on Windows 7 than the one provided by Microsoft with a hosts file. The AV program supplied by Microsoft will remove every entry in a hosts file. You need another AV program that doesn't do that.
New Way Of Handling PAC On Windows
Here the special instructions for putting the PAC filter on Windows 7. You don't put it on there the same way you do it on XP. You should change it to put the all of the files which can be used for Firefox in your account in an etc folder. You also need an extra special folder for Internet Settings and it is mandatory for the Chrome browser. For example for a user named hhhobbit and assuming your system drive is C: you will have these folders (substitute your user name for mine and it should be just alphabetic or alphanumeric characters):
You put all of the files in the etc folder. You need to edit all of the proxy files and change the blackhole from 127.0.0.1 to 0.0.0.0 unless you intend to install Homer in roughly the same area, e.g.:
I don't advise that and didn't even try it due to too many problems. Like I just said, you should change the blackhole to be 0.0.0.0. Use the Error Console in Firefox for debugging. Unlike a hosts file it is done only once on one line in the PAC filter. Then you copy which ever of proxy_en.txt or proxy_fr.txt file that you use to the OneFile folder. WARNING! This is the only file you should have in that folder. You set your Internet Settings browsers to use that file. Why have just one file? The Chrome browser parses evey darn file in the folder. Worse yet, it sucks up those settings and puts them in places I cannot find. It doesn't know how to handle the debug statements. The proxy_en.txt and proxy_fr.txt files have the debug statements removed. The debug even if it is not used causes unexpected "Object Unexpected" pop-up messages. I have even uninstalled Chrome completely, removed all the files Chrome left manually, and then manually cleaned the Registry. Why? Because Chrome parses every file in the folder. The debug causes it to pop up "Objected Unexpected" messages. I then reset Internet Settings to use the OneFile folder and used it that way successfully with Opera and Safari. I have even waited as long as 4 months. But the instant I reinstall Chome, back comes the "Object Unexpected" messages if you did it wrong the first time around. I am beginning to suspect that Google sucks your Chrome settings up into the cloud and puts them right back the way they were when you reinstall. Hasn't Google ever heard of a clean state reinstall to get rid of problems? There are times when a history should not be done! This is one of them.
Actually the only people I know using the PAC filter are all on Linux and the rest just look at the rules and if they like some of them, they stuff them into their company's proxy. expect most of these users to be smart enough that they can handle it all with just what I say here.