It sounds like you have some bad WUs.  There was another thread about error
100 that may be of interest to you.

To clear the error, first try deleting the
SETIDriverTransmitLoopDetector.txt files and try transmitting again.  In any
folders that this file reappears, delete the folder and reset the SETI
Driver Desired Cache size.  Those WUs were currupt and could not be
returned.

Mike Ober.

"Swen Sauerwald" <My-Trashcan@gmx.net> wrote in message
news:a9d0417239153fc7f1c9de83e03ca70f@ID-123334.user.uni-berlin.de...

Hello folks,

i have the following Problem:

I tried to submit several Results (5), transmitting started and worked
without problems for three Results. 2 doesn't get submitted, so i tried
it again: the 'Sending Result Screen' appears, lasts for a few seconds
and closes so fast, that it's impossible to read the whole Errormessage.
All i can see is: Unknown error...

After finishing the next WU, i tried it again, the new Result was trans-
mitted properly, but not the other ones. Another WU later i tried it
again, but this time the new Result wasn't transmitted either.

BTW, i played around with the Proxy-Settings (submitting with and with-
out Proxy), but it doesn't help.

BTW�, i found the following new Files in each Folder, which Result
wasn't submitted:

SetiDriverTransmitLoopDetector.txt       0KB
SETILogUpdated.txt                       0KB

BTW�, i'm using SETISpy 3.3.3, SETI Driver 1.6.4.0, CLI 3.08 and Windows
XP Pro SP1 (no changes made since a few days).

Does anybody know what's going on?

Best regards,
 Swen

PS: X-Post & F'up2 alt.sci.seti

-- 

http://setiathome.ssl.berkeley.edu/cgi-bin/cgi?email=catweasel@gmx.net&cmd=print_cert&certnum=0&size=0