I have been receiving a lot of damaged PAR file messages BUT the selected file does seem to finish downloading properly evetually. Does that error mean one of the RAR files is damaged and even the backup PAR file is damaged also? Also getting connect errors with a code of 400 too. This is a new usenet service I'm trying out. They aren't as fast as my primary connection, but I've never had trouble connecting to them manually.
[00:38:30] ERROR NNTPSocket - NS_Connect - news.tweaknews.eu-Error talking to Server:400 news.tweak-news.eu: Session timeout.
[00:38:30] ERROR NNTPSocket - NS_Connect - news.tweaknews.eu-Error talking to Server:400 news.tweak-news.eu: Session timeout.
[02:05:50] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:46:58] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:46:59] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:47:00] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:47:03] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:47:07] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:47:15] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:47:29] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:47:54] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:48:43] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:50:18] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:53:07] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile:
[07:56:14] ERROR - AutoPAR: PAR file is Damaged, Unable to Add Parfile: