Re: RE: Re: Re: clean ini file with server info

Lenny_Nero wrote:
> Dave said
>
>   
>> When I know exactly what I'm hunting for, I use NZB files.
>>
>> However, when I am just wandering, looking for something new or
>> interesting, I much prefer downloading headers and grabbing whatever
>> jumps out at me.
>>     
>
> That is the same for me, looking thru the groups via .nzb sites is like
> reading text via google groups ...stupid. I have got so much stuff over
> the years because I have seen the poster is someone I know that has a
> good, or alike taste to mine, and given the upload a try to find something
> new and very good.
>
> This cant be done via .nzb sites, and they never show every post. I have
> seen many things that I missed and did not want to pull the older headers,
> gone to binsearch or newsleech (my fave) only to be unable to find it.
>   

That all depends on how poorly your NZB source is designed.

I use Easynews, which allows me to view each and every complete file, 
search (including regex) across everything posted on usenet in around 
two months, and navigate within NZB and PAR/PAR2 files, eventually 
building my own custom NZBs which only contain *exactly* the content I 
want, finally downloading via BNR2.

I could use a HTTP download manager too, but using BNR2 means that I can 
pull from cheaper NNTP sources first, only falling back on Easynews when 
needed.

Even so, for just browsing rather then searching, I still prefer the 
BNR3 interface to any web interface.

> Limit you headers, or check your settings if you are having problems with
> BNR. BNR2 MUST only use 1 header thread/server at a time and BNR3 is much
> faster if you do the same, but has no problems if you use more. Then there
> is the max data in header block % number, if you have free headers just
> set it to 100%, but lower if you have to pay.
>   

I've had my best success by forcing BNR3 to use two threads to pull 
overviews from my most complete server first, then opening up 3-4 
threads/server to let BNR3 fill in the gaps from other news servers -- 
This process is usually much faster since it's just reading the already 
cached and indexed DB, rather then adding significant data to the DB 
(which blocks other threads)

That being said, I have a very powerful machine (scoring 5.9 on Vista's 
performance tests for processor, RAM and disk performance), other 
machines may have different results.

> Then there is the LISTGROUP, XOVER and XHDR settings, I still thing there
> are some small problem with BNR3 and XHDR so only use LISTGROUP, but with
> 2 I almost always used XHDR (if you want to learn ...use the search Luke)
>   

It's a shame, starting with a LISTGROUP to determine expired, current 
and new articles quickly, followed by an XHDR for only Message-ID to add 
Message-ID entries to the DB and then to populate the 
which-server-has-which-article tables, followed by a XOVER for the 
specified articles from only one server would be so much more efficient, 
especially when using several slower ISP-type (Rather then well run 
commercial NNTP services) servers with massive incomplete problems.

However, LISTGROUP and XOVER work reasonably well together, it just 
wastes bandwidth if you have multiple servers.

-- 
The Dave!
http://www.thedave.ca/




------------------------------------

Important Addresses:
Post message: [email protected]
Group owner:  [email protected]
BNR homepage: http://www.bnr2.org/
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/bnr1/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/bnr1/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/