Bear wrote:
> Dustin<(E-Mail Removed)> wrote in
> news:XnsA02FB25AF5894HHI2948AJD832@no:
>
>> Bear<(E-Mail Removed)> wrote in
>> news:XnsA02F89DA34FB2bearbottoms1gmail.AC@130.225.254.104:
>>
>>> Dustin<(E-Mail Removed)> wrote in
>>> news:XnsA02F8311ADAA0HHI2948AJD832@no:
>>>
>>>> Bear<(E-Mail Removed)> wrote in
>>>> news:XnsA02F63254151Dbearbottoms1gmail.AC@130.225.254.104:
>>>>
>>>>> Bear<(E-Mail Removed)> wrote in
>>>>> news:XnsA02C4560CC195bearbottoms1gmail.AC@130.225.254.104:
>>>>>
>>>>>> Norton ConnectSafe
>>>>>
>>>>> Damn, Cox's servers are closer than Symantec's to my location yet
>>>>> the DNSBenchmark shows Symantec's DNS servers to be faster. In
>>>>> fact, it is fastest of the performance of 4,849 resolvers.
>>>>>
>>>>> http://bearware.info/screenshots/DNSBenchmark000.png
>>>>
>>>> http://bughunter.it-mate.co.uk/dnsbenchmark.jpg
>>>>
>>>>
>>>>
>>>>> Must be something going on other than the speed of electricity.
>>>>
>>>> As already explained.
>>>
>>> You did not ... I did. You were hung up on how close a server was,
>>> and I explained to you that other factors were at play. You only
>>> spouted that out after I proved you wrong and only since today.
>>> Yesterday was a different story Mr. Crawfish.
>>
>> Nice try.. I keep MID's tho.
>>
>> Heres what you actually said...
>> Message-ID:<XnsA02F63254151Dbearbottoms1gmail.AC@130.225.254.104>
>>
>> This is what I said
>> Message-ID:<XnsA02F801CB2C1EHHI2948AJD832@no>
>> Packet switching, fiber and routing all play a part. As well as server
>> load. IE: If the Cox DNS server is busy, symantec might outrun it's
>> replies from YOUR physical location. That does NOT mean it'll be the
>> same for everyone else using Cox.
>>
>> I stand by what I said. Symantec is far slower for my systems, as is
>> proven in the dnsbenchmark jpg I already posted. Your claims of
>> symantec always being faster than your ISP (I don't even use Cox, but
>> Cox is faster on my benchmark) were wrong for a variety of reasons.
>> Your pathetic attempts to talk down or otherwise try and belittle me
>> do you no good. You're an idiot and we all know it.
>>
>>
>>
>
> Nice try, but you can easily prove yourself wrong by running the custom
> list process which you admitted you haven't done and as a result are
> talking outta your ass.
>
> You lost. Simple as that. You are a ****, a liar and a coward.
>
> Best to move on Dustin...your in over your head. I'm moving on.
>
Will you be leaving the group then? D

FromTheRafters <(E-Mail Removed)> wrote in
news:jlta8l$86g$(E-Mail Removed):

> Bear wrote:
>> Dustin<(E-Mail Removed)> wrote in
>> news:XnsA02FB25AF5894HHI2948AJD832@no:
>>
>>> Bear<(E-Mail Removed)> wrote in
>>> news:XnsA02F89DA34FB2bearbottoms1gmail.AC@130.225.254.104:
>>>
>>>> Dustin<(E-Mail Removed)> wrote in
>>>> news:XnsA02F8311ADAA0HHI2948AJD832@no:
>>>>
>>>>> Bear<(E-Mail Removed)> wrote in
>>>>> news:XnsA02F63254151Dbearbottoms1gmail.AC@130.225.254.104:
>>>>>
>>>>>> Bear<(E-Mail Removed)> wrote in
>>>>>> news:XnsA02C4560CC195bearbottoms1gmail.AC@130.225.254.104:
>>>>>>
>>>>>>> Norton ConnectSafe
>>>>>>
>>>>>> Damn, Cox's servers are closer than Symantec's to my location yet
>>>>>> the DNSBenchmark shows Symantec's DNS servers to be faster. In
>>>>>> fact, it is fastest of the performance of 4,849 resolvers.
>>>>>>
>>>>>> http://bearware.info/screenshots/DNSBenchmark000.png
>>>>>
>>>>> http://bughunter.it-mate.co.uk/dnsbenchmark.jpg
>>>>>
>>>>>
>>>>>
>>>>>> Must be something going on other than the speed of electricity.
>>>>>>
>>>>>
>>>>> As already explained.
>>>>
>>>> You did not ... I did. You were hung up on how close a server was,
>>>> and I explained to you that other factors were at play. You only
>>>> spouted that out after I proved you wrong and only since today.
>>>> Yesterday was a different story Mr. Crawfish.
>>>
>>> Nice try.. I keep MID's tho.
>>>
>>> Heres what you actually said...
>>> Message-ID:<XnsA02F63254151Dbearbottoms1gmail.AC@130.225.254.104>
>>>
>>> This is what I said
>>> Message-ID:<XnsA02F801CB2C1EHHI2948AJD832@no>
>>> Packet switching, fiber and routing all play a part. As well as
>>> server load. IE: If the Cox DNS server is busy, symantec might
>>> outrun it's replies from YOUR physical location. That does NOT mean
>>> it'll be the same for everyone else using Cox.
>>>
>>> I stand by what I said. Symantec is far slower for my systems, as is
>>> proven in the dnsbenchmark jpg I already posted. Your claims of
>>> symantec always being faster than your ISP (I don't even use Cox,
>>> but Cox is faster on my benchmark) were wrong for a variety of
>>> reasons. Your pathetic attempts to talk down or otherwise try and
>>> belittle me do you no good. You're an idiot and we all know it.
>>>
>>>
>>>
>>
>> Nice try, but you can easily prove yourself wrong by running the
>> custom list process which you admitted you haven't done and as a
>> result are talking outta your ass.
>>
>> You lost. Simple as that. You are a ****, a liar and a coward.
>>
>> Best to move on Dustin...your in over your head. I'm moving on.
>>
> Will you be leaving the group then? D
>

That's what I would call high hopes

--
Bear
http://bearware.info
The real Bear's header path is:
news.sunsite.dk!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-
mail

G. Morgan <(E-Mail Removed)> wrote in
news(E-Mail Removed):

> Dustin wrote:
>
>>G. Morgan <(E-Mail Removed)> wrote in
>>news:(E-Mail Removed):
>>
>>> Bear wrote:
>>>
>>>>
>>>>Damn, Cox's servers are closer than Symantec's to my location yet
>>>>the DNSBenchmark shows Symantec's DNS servers to be faster. In fact,
>>>>it is fastest of the performance of 4,849 resolvers.
>>>>
>>>>http://bearware.info/screenshots/DNSBenchmark000.png
>>>
>>>
>>> You don't want the ones colored brown, that means they play games
>>> with misspellings and sites they view as 'bad'.
>>
>>He also didn't actually run the benchmark. Notice no blue bar across
>>the top and no grid lines.
>
> Oh, yeah. He just did the first step.
>

Don't let Dustin suck you in. Be your own man. Run the custom list like
Dustin didn't do and see for yourself....well, I'm assuming your a man.

--
Bear
http://bearware.info
The real Bear's header path is:
news.sunsite.dk!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-
mail

Bear <(E-Mail Removed)> wrote in
news:XnsA02FB75FD7549bearbottoms1gmail.AC@130.225.254.104:

> Dustin <(E-Mail Removed)> wrote in
> news:XnsA02FBEFFDDC81HHI2948AJD832@no:
>
>> G. Morgan <(E-Mail Removed)> wrote in
>> news:(E-Mail Removed):
>>
>>> Bear wrote:
>>>
>>>>
>>>>Damn, Cox's servers are closer than Symantec's to my location yet
>>>>the DNSBenchmark shows Symantec's DNS servers to be faster. In
>>>>fact, it is fastest of the performance of 4,849 resolvers.
>>>>
>>>>http://bearware.info/screenshots/DNSBenchmark000.png
>>>
>>>
>>> You don't want the ones colored brown, that means they play games
>>> with misspellings and sites they view as 'bad'.
>>
>> He also didn't actually run the benchmark. Notice no blue bar across
>> the top and no grid lines.
>>
>>
>
> That is an image of the custom list results which you didn't do and
> have no clue, talking about results which you have no knowledge of as
> you didn't perform the process, and that is a direct image from the
> results. I can call you out on that too...and you would be proven
> wrong on that one also. Dustin...you lost and don't have the balls to
> admit it.
>
> See ya round.
>


Bear, the custom list is a flawed test.. By far. I'm doing it now..

First,the default list after running the benchmark.
http://bughunter.it-mate.co.uk/dnsbenchmark.jpg

Here's the first result from the custom test build:
http://bughunter.it-mate.co.uk/dnscustom1.png

and this is the result after actually RUNNING the benchmark after getting
this custom list:
http://bughunter.it-mate.co.uk/dnscustom2.png

At no time during either list loading OR test! did symantec come anywhere
close. The custom list even ranks charter the fastest for me, as I sort of
expected it would; since the list is designed to find the 50 fastest DNS
servers relative to MY position in the network. IE: Symantec isn't going
to be faster in many cases for many reasons. Your claim of it being
otherwise is untrue.

When you created the custom list, you DID NOT run the benchmark after
doing so. Had you of, it would look like dnscustom2.png. Just creating the
custom list creates the same thing you'd see in dnscustom1.png as I've
provided on my site. You did NOT run the benchmark test on the custom
list. The png file you provided only shows you created one. I created one,
AND ran the benchmark. Oh, and none of them, default or custom
before/after test EVER showed Symantec in the top 5.

And this is why doing the custom list is a flawed! way of doing this:

This GRC DNS Benchmark is scanning 4,849 global DNS resolvers to determine
whether they are accessible and responsive from your present location. If
so, the Benchmark measures the resolver's minimum response time, as well
as whether it appears to be operating reliably and correctly.

While this is underway, every qualifying resolver is dynamically "ranked"
from fastest to slowest. The top line of the display above shows the
minimum response time of the fastest resolver found so far, as well as the
minimum response time of the "50th fastest."

Once the ranking scan is completed, the IP addresses of those 50 fastest
qualifying resolvers will be loaded into the Benchmark so that you can
immediately perform a comprehensive analysis of their performance and the
IPs will also be written to a file named "DNSBENCH.INI", located in the
same directory as the Benchmark. This "DNSBENCH.INI" file will then
automatically be loaded whenever the Benchmark is run in the future.

Unlike the Benchmark's built-in default list of safe and well-known
commercial resolvers, this global list contains all of those resolvers,
plus others of unknown origin, ownership, disposition, reliability,
availability and access. We are expressly not vouching for, or
recommending, that you use any of these. So you must use your own
judgement based upon the designated ownership, the resolver's network
name, and anything else that might give you a clue about whether such a
resolver might be wise to use.

You may repeat this list-building anytime you wish to recreate your
personalized custom resolver IP list. This should be done when this
machine is moved to another location or to another ISP.

How's that for "****" Bear? You'll soon learn why Aardvark affectionally
calls me that, if you haven't already.



--
Character is doing the right thing when nobody's looking. There are too
many people who think that the only thing that's right is to get by,
and the only thing that's wrong is to get caught. - J.C. Watts

G. Morgan <(E-Mail Removed)> wrote in
news(E-Mail Removed):

> Dustin wrote:
>
>>G. Morgan <(E-Mail Removed)> wrote in
>>news:(E-Mail Removed):
>>
>>> Bear wrote:
>>>
>>>>
>>>>Damn, Cox's servers are closer than Symantec's to my location yet
>>>>the DNSBenchmark shows Symantec's DNS servers to be faster. In
>>>>fact, it is fastest of the performance of 4,849 resolvers.
>>>>
>>>>http://bearware.info/screenshots/DNSBenchmark000.png
>>>
>>>
>>> You don't want the ones colored brown, that means they play games
>>> with misspellings and sites they view as 'bad'.
>>
>>He also didn't actually run the benchmark. Notice no blue bar across
>>the top and no grid lines.
>
> Oh, yeah. He just did the first step.
>

It looks like this if you have the program create the png files for you:

First, custom list loaded, no test
http://bughunter.it-mate.co.uk/dnscustom1.png

Heres the custom list after the benchmark test (again, I used the
programs png export feature instead of outright screen cap). You can
clearly see a difference tho.

http://bughunter.it-mate.co.uk/dnscustom2.png

Bear stopped at the first part. He created the custom list, but never
followed thru.


--
Character is doing the right thing when nobody's looking. There are too
many people who think that the only thing that's right is to get by, and
the only thing that's wrong is to get caught. - J.C. Watts

Bear <(E-Mail Removed)> wrote in
news:XnsA02FC79CF5399bearbottoms1gmail.AC@130.225.254.104:

> G. Morgan <(E-Mail Removed)> wrote in
> news(E-Mail Removed):
>
>> Dustin wrote:
>>
>>>G. Morgan <(E-Mail Removed)> wrote in
>>>news:(E-Mail Removed):
>>>
>>>> Bear wrote:
>>>>
>>>>>
>>>>>Damn, Cox's servers are closer than Symantec's to my location yet
>>>>>the DNSBenchmark shows Symantec's DNS servers to be faster. In
>>>>>fact, it is fastest of the performance of 4,849 resolvers.
>>>>>
>>>>>http://bearware.info/screenshots/DNSBenchmark000.png
>>>>
>>>>
>>>> You don't want the ones colored brown, that means they play games
>>>> with misspellings and sites they view as 'bad'.
>>>
>>>He also didn't actually run the benchmark. Notice no blue bar across
>>>the top and no grid lines.
>>
>> Oh, yeah. He just did the first step.
>>
>
> Don't let Dustin suck you in. Be your own man. Run the custom list
> like Dustin didn't do and see for yourself....well, I'm assuming your
> a man.
>

http://bughunter.it-mate.co.uk/dnscustom1.png
http://bughunter.it-mate.co.uk/dnscustom2.png

I not only ran the custom list this time, I ran the benchmark using it.


You only created the custom list. lol


--
Character is doing the right thing when nobody's looking. There are too
many people who think that the only thing that's right is to get by,
and the only thing that's wrong is to get caught. - J.C. Watts

"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
news:(E-Mail Removed):

> From: "Bear" <(E-Mail Removed)>
>
>
>>>>
>>> Will you be leaving the group then? D
>>>
>> That's what I would call high hopes
>>
>
> The kind of high hopes that cause one to go to South Amererica and
> fly back controlled dangerous substances that "Seal'd" your fate?
>

Don't forget cheating the IRS.


--
Character is doing the right thing when nobody's looking. There are too
many people who think that the only thing that's right is to get by, and
the only thing that's wrong is to get caught. - J.C. Watts

Bear <(E-Mail Removed)> wrote in
news:XnsA02FC5A7B19E4bearbottoms1gmail.AC@130.225.254.104:

> That's what I would call high hopes

On this tho Bear, I agree with you:

If you were president, how would you handle the drug issue?

Decriminalize drugs. Take the profit out of it. Deal with the social
problems. The criminal element would disappear. Alcohol is legal. Are you
an alcoholic? I am not. Do we have problems with alcohol...yes. We would
no matter what.

Do you remember answering that question? [g]
http://prorev.com/bottoms.htm

--
Character is doing the right thing when nobody's looking. There are too
many people who think that the only thing that's right is to get by, and
the only thing that's wrong is to get caught. - J.C. Watts

Dustin <(E-Mail Removed)> wrote in
news:XnsA02FBEFFDDC81HHI2948AJD832@no:

> G. Morgan <(E-Mail Removed)> wrote in
> news:(E-Mail Removed):
>
>> Bear wrote:
>>
>>>
>>>Damn, Cox's servers are closer than Symantec's to my location yet the
>>>DNSBenchmark shows Symantec's DNS servers to be faster. In fact, it
is
>>>fastest of the performance of 4,849 resolvers.
>>>
>>>http://bearware.info/screenshots/DNSBenchmark000.png
>>
>>
>> You don't want the ones colored brown, that means they play games
>> with misspellings and sites they view as 'bad'.
>
> He also didn't actually run the benchmark. Notice no blue bar across
the
> top and no grid lines.
>
>

Well ****. You /are/ right. I didn't run the test and my png was the
result of the process of developing the custom list which at that time I
thought was the test...a bit weird. Seeing your response made me go run
the test and Cox came out on top and Semantec was about .12 seconds
behind.

So I apologize to you for being a dick and I admit I was wrong. Damn.

I'll post this in the other forum. You know I hate it.

--
Bear
http://bearware.info
The real Bear's header path is:
news.sunsite.dk!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-
mail

Bear wrote:

>Don't let Dustin suck you in. Be your own man. Run the custom list like
>Dustin didn't do and see for yourself....well, I'm assuming your a man.

I have already done that, the last time was a month ago. I know
how it works, thanks.

--
I drank some boiling water because I wanted to whistle. -Mitch Hedberg