>Ah, lots of real good ideas!
>
>First, I've missed that the 'ill URL'-message is probably generated by
>VSoup. Thus the question comes up to the address of Gerry: what
>actual command line parameters are you using?
The CMD file contains:
d:\yarn\vsoup.exe -mx -k0 nntp://%nntpserver% gbritton
Nntpserver is set in config.sys.
>
>Second, VSoups nntp command sequence to fetch an article is as
>follows (you're trying to get some news from comp.os.os2.announce):
>
>--------------------------------------------------------------------------------
>MODE READER
>
>GROUP comp.os.os2.announce
>
>(perhaps one has now to do authinfo, if the server returned 480:
>
> AUTHINFO USER <yourname>
> AUTHINFO PASS <yourpass>
> GROUP comp.os.os2.announce
>
>)
>
>XHDR LINES <article-range>
>
>ARTICLE <article-number>
>--------------------------------------------------------------------------------
>
>For each command there will be a response from the newsserver
>containing a code and hopefully some readable text indicating success
>or failure.
>
>Gerry, your task is no to check it manually via telnet (as suggested).
>The other thing you could do is to start VSoup with one single
>connection (-t1).
This returned the following, without abending:
VSOUP.EXE: 1 article read
VSOUP.EXE: 1 thread was connected successfully
VSOUP.EXE: totally 24358 bytes received, 575 bytes transmitted
VSOUP.EXE: 4.1s elapsed, throughput 6081 bytes/s
Do you suggest lowering the threads to 1, and seeing if VSOUP behaves
exactly like Souper?