103  6881 
Tom wrote:
On Sun, 13 Jul 2008 14:52:18 -0400, Ed Mullen wrote:
>Why are you jumping through all these hoops? The Windows "hosts" file
is a plain text file you can edit in Notepad.
I know, I know.
Microsoft put the c:\windows\syst em32\drivers\et c\hosts file in the most
ridiculous non-intuitive spot it could possibly find, deep in muck, deep
under large directories that take a while to load, and without a decent
extension so you have to grope for your text editor (mine is vim freeware).
So, rather than "jump thru hoops" each time just to edit the hosts file, I
add a one-time-only registry key "hosts" which opens up the TEXT file (so
that I have a backup if I need it).
When I type "Start -Run -hosts", vim opens up that
c:\windows\syst em32\drivers\et c\hosts.txt text file, where I edit and save
to "hosts" which it saves in the current directory (i.e.,
c:\windows\syst em32\drivers\et c\hosts).
That's a LOT easier than navigating deep into the windows hierarchy into
the least logical place MS could have placed the hosts file and then
fumbling around to get notepad to edit the file with no extension.
Nonsense!
You have detailed a process that does not work in my standard install of
WXP-SP3. You have further created a questionable process involving
editing the Windows Registry which is, at best, a questionable process
in and of itself, and hardly something to be posting to a newsgroup.
Further, you have not answered satisfactorily any questions of the links
you posted. And, your bizarre approach to a HOSTS file is ...
mind-blowingly stupid.
I deem this entire thread bogus at best, threatening at worst. I
encourage no one to do anything that "Tom" has recommended until he
demonstrates that he actually knows what he's doing by citing
authoritative references.
That HOSTS file and registry stuff is total nonsense and the product of
(at best) someone who has not a clue and who has been surfing and copied
suspect references.
IGNORE ALL OF THIS.
--
Ed Mullen http://edmullen.net
A budget is just a method of worrying before you spend money, as well as
afterward.
Tom wrote:
On Sun, 13 Jul 2008 13:45:20 -0400, C A Upsdell wrote:
>If Windows, Ctrl Alt Delete to call up the task manager; select the
browser; kill it.
Very inelegant.
Inelegant. But reliable, and safe.
Tom wrote:
On Sun, 13 Jul 2008 13:45:20 -0400, C A Upsdell wrote:
>If Windows, Ctrl Alt Delete to call up the task manager; select the
browser; kill it.
Very inelegant.
Inelegant. But reliable, and safe.
On Sun, 13 Jul 2008 23:43:02 -0400, C A Upsdell wrote:
>>If Windows, Ctrl Alt Delete to call up the task manager; select the
browser; kill it.
Very inelegant.
Inelegant. But reliable, and safe.
I agree. It's what I used to do before I found Hummingbird's more elegant
hosts file solution.
Thanks everyone,
Tom
Tom wrote:
On Sun, 13 Jul 2008 21:36:51 +0100, hummingbird wrote:
>>Rather after-the-fact isn't it?
He can use the hosts file to avoid going to that site
The whole point is to be able to get out of the quicksand without having to
kill the entire browser session (losing all your tabs).
You have not demonstrated that this is an issue. Most of the URLS you
posted died as a 403 or something. This is a non-issue for 99% of users
and I believe you are (at best) spamming, at worst trying to suck people
into your links. Well, ok, you could just be stupid.
>
If you kill the browser, yet you wanted the OTHER tabs (not the quicksand
tab), you can't ever start it again 'cuz you can only recover all the tabs
or none of the tabs.
What? You are clueless.
So, this hosts edit and then doing a shift reload, allows you to blank out
the one quicksand tab and move on with your life.
Elegant, isn't it?
Not!
Idiotic at best when considered in light of his other posts.
--
Ed Mullen http://edmullen.net
A clear conscience is usually the sign of a bad memory.
On Sun, 13 Jul 2008 23:43:02 -0400, C A Upsdell wrote:
>>If Windows, Ctrl Alt Delete to call up the task manager; select the
browser; kill it.
Very inelegant.
Inelegant. But reliable, and safe.
I agree. It's what I used to do before I found Hummingbird's more elegant
hosts file solution.
Thanks everyone,
Tom
Tom wrote:
On Sun, 13 Jul 2008 21:36:51 +0100, hummingbird wrote:
>>Rather after-the-fact isn't it?
He can use the hosts file to avoid going to that site
The whole point is to be able to get out of the quicksand without having to
kill the entire browser session (losing all your tabs).
You have not demonstrated that this is an issue. Most of the URLS you
posted died as a 403 or something. This is a non-issue for 99% of users
and I believe you are (at best) spamming, at worst trying to suck people
into your links. Well, ok, you could just be stupid.
>
If you kill the browser, yet you wanted the OTHER tabs (not the quicksand
tab), you can't ever start it again 'cuz you can only recover all the tabs
or none of the tabs.
What? You are clueless.
So, this hosts edit and then doing a shift reload, allows you to blank out
the one quicksand tab and move on with your life.
Elegant, isn't it?
Not!
Idiotic at best when considered in light of his other posts.
--
Ed Mullen http://edmullen.net
A clear conscience is usually the sign of a bad memory.
Tom wrote:
On Sun, 13 Jul 2008 13:45:20 -0400, C A Upsdell wrote:
>If Windows, Ctrl Alt Delete to call up the task manager; select the
browser; kill it.
Very inelegant.
When you have a dozen tabs open, killing the browser, kills all the tabs.
When you restart Firefox, it asks if you want to open all the old tabs,
but, of course, that will just open the quicksand site all over again.
So, without editing the hosts file and shift reloading, you're forced to
say NO to reloading your old tabs ... and you lose them all.
That's why you don't kill the browser session.
Luckily we found a single-click way to solve the problem (type "start ->
run -hosts, add the offending domain, and shift reload the browser). This
turns the quicksand URL into cement. Voila! Thanks to hummingbird!
If you have other tabs open that you want to keep viewing, then yes,
it's a good immediate, albeit 'temporary' solution to the problem. I
say temporary because using a Hosts file isn't a good solution. Many
malware sites scan and remove their listings from hosts files (and even
locking it via the read-only attribute won't protect you). They do it
by making you log into a benign site first (one that isn't blocked) and
using that to remove their entry from your Hosts file before redirecting
you and trapping your browser. Even running free FireFox addons such as
NoScript won't protect you unless you've been caught before and know not
to allow the site access to Java or JS. You should really be running
an IP blocking program like PeerGuardian or if that is too much hassle,
do what I do and use OpenDNS. I'm sure there are other solutions, those
two just spring to mind. My advice, if you don't want this happening
again and you're the type that's likely to run across sites like these
often, is to do a bit of research into blocking methods and choose the
one that best suits your need.
--
Me Here
I've started referring to the proposed action against Iraq as Desert
Storm 1.1, since it reminds me of a Microsoft upgrade: it's expensive,
most people aren't sure they want it, and it probably won't work. --
Kevin G. Barkes 2002
"Ed Mullen" <ed@edmullen.ne twrote in message
news:oI******** *************** *******@comcast .com...
Tom wrote:
>On Sun, 13 Jul 2008 14:52:18 -0400, Ed Mullen wrote:
>>Why are you jumping through all these hoops? The Windows "hosts" file
is a plain text file you can edit in Notepad.
I know, I know. Microsoft put the c:\windows\syst em32\drivers\et c\hosts
file in the most
ridiculous non-intuitive spot it could possibly find, deep in muck, deep
under large directories that take a while to load, and without a decent
extension so you have to grope for your text editor (mine is vim
freeware).
So, rather than "jump thru hoops" each time just to edit the hosts file,
I
add a one-time-only registry key "hosts" which opens up the TEXT file (so
that I have a backup if I need it). When I type "Start -Run -hosts",
vim opens up that
c:\windows\sys tem32\drivers\e tc\hosts.txt text file, where I edit and
save
to "hosts" which it saves in the current directory (i.e.,
c:\windows\sys tem32\drivers\e tc\hosts).
That's a LOT easier than navigating deep into the windows hierarchy into
the least logical place MS could have placed the hosts file and then
fumbling around to get notepad to edit the file with no extension.
Nonsense!
You have detailed a process that does not work in my standard install of
WXP-SP3. You have further created a questionable process involving
editing the Windows Registry which is, at best, a questionable process in
and of itself, and hardly something to be posting to a newsgroup.
Further, you have not answered satisfactorily any questions of the links
you posted. And, your bizarre approach to a HOSTS file is ...
mind-blowingly stupid.
I deem this entire thread bogus at best, threatening at worst. I
encourage no one to do anything that "Tom" has recommended until he
demonstrates that he actually knows what he's doing by citing
authoritative references.
That HOSTS file and registry stuff is total nonsense and the product of
(at best) someone who has not a clue and who has been surfing and copied
suspect references.
Nonsense. This is a fine solution (though I can think of simpler ones ...
like just creating a shortcut to vim-edit the hosts file).
"Ed Mullen" <ed@edmullen.ne twrote in message
news:X7******** *************** *******@comcast .com...
Tom wrote:
>On Sun, 13 Jul 2008 21:36:51 +0100, hummingbird wrote:
>>>Rather after-the-fact isn't it?
He can use the hosts file to avoid going to that site
The whole point is to be able to get out of the quicksand without having
to
kill the entire browser session (losing all your tabs).
You have not demonstrated that this is an issue. Most of the URLS you
posted died as a 403 or something. This is a non-issue for 99% of users
and I believe you are (at best) spamming, at worst trying to suck people
into your links. Well, ok, you could just be stupid.
>>
If you kill the browser, yet you wanted the OTHER tabs (not the quicksand
tab), you can't ever start it again 'cuz you can only recover all the
tabs
or none of the tabs.
What? You are clueless.
>So, this hosts edit and then doing a shift reload, allows you to blank
out
the one quicksand tab and move on with your life.
Elegant, isn't it?
Not!
Idiotic at best when considered in light of his other posts.
Hey Ed. Are you Bare Bottoms in disguise. Or just a wannabee?. This thread has been closed and replies have been disabled. Please start a new discussion. |
