Hi - Yes, that's the GRC news server. As to the Beta - that's mostly a
naming convention with NT and ObiWan. Their Beta's are like most others'
production code, and their released versions are rock solid - never had a
problem of any sort. On their Betas, the only issue that has ever come up
for me was an occasional high CPU usage spurt - never anything that bothered
anything else. FWIW, their install/uninstall is the cleanest I've seen -
like clockwork - just in case you do have a problem. Again, I highly
recommend it to you - the benefits far, far outweigh the risks - the
performance improvement is substantial. One other BTW - you can also use
Bind for AdBlocking.
--
Please respond in the same thread.
Regards, Jim Byrd, MS-MVP
In news:e5rgnvcb3i0jq8h3voiqg5gqseb0ik93an@4ax.com,
siljaline <siljaline@invalid.com> typed:
> On Mon, 29 Sep 2003 16:29:36 GMT, "Jim Byrd"
> <jrbyrd@spamlesscomcast.net> wrote:
>
>> Hi R. - You might want to be aware of a real "solution" (rather than
>> just a block) for the Verisign problem. Get the BindPE
>> Treewalk_Delegate.exe here: http://ntcanuck.com/Beta/ While you're
>> there, get the ORSC-Root also. You can read about the basic BindPE
>> here: http://ntcanuck.com/, but the Treewalk_Delegate is the
>> version you
>> want to get to solve completely the Verisign problem (at least until
>> Verisign changes something). Installs cleanly, (and uninstalls the
>> same
>> way), and works like a charm. You find all of your browsing
>> considerably speeded up. Very highly recommended. FWIW, you'll
>> find an associated news group here:
>> news.grc.com/grc.techtalk.dns.bind_pe_beta
>
> Hi Jim,
> I'm trying to convince my ISP to implement the Bind patch,
> server-side. Appreciate your feedback but I *really* don't like
> running anything BetaHave VeriSign blocked in HOSTS and
> AdShield...
>
>> news.grc.com/grc.techtalk.dns.bind_pe_beta
> Is that on the GRC news-server?
>
> Regards,



Have VeriSign blocked in HOSTS and
Reply With Quote