[rc5] 64-bit client oddity?

Mike Lingk mlingk at enteract.com
Thu Oct 23 12:19:52 EDT 1997


I had this same problem, and after checking 4 blocks, it retrieved 5 more and sent back
4. Seems to be working correctly now after dropping the first block.

  -Mike Lingk

-----Original Message-----
From:	Jeff Woods [SMTP:jeff at delta.com]
Sent:	Thursday, October 23, 1997 10:13 AM
To:	rc5 at llamas.net
Subject:	[rc5] 64-bit client oddity?
 [10/23/97 15:01:56 GMT] Proxy says Moo..... (whatever)

<<<<<<<<<<<<<<<<<<<<
[10/23/97 15:02:19 GMT] Retrieved 20 blocks from server
[10/23/97 15:02:19 GMT] Block:  6400A121:10000000 ready for processing
[10/23/97 15:02:19 GMT] 19 blocks remain in file C:\RC5\buff-in.rc5
[10/23/97 15:02:19 GMT] 0 blocks are in file C:\RC5\buff-out.rc5
Child thread # 1 has been started.
[10/23/97 15:02:19 GMT] Block:  6400A121:20000000 ready for processing
[10/23/97 15:02:19 GMT] 18 blocks remain in file C:\RC5\buff-in.rc5
[10/23/97 15:02:19 GMT] 0 blocks are in file C:\RC5\buff-out.rc5
.....10%.....20%...

My question is:   since this is only a single CPU machine, what happened to
that first block?   What does "child thread #1 started" mean?   It never
did this before, on the 56-bit challenge -- it always checked the blocks
linearly (or at least, in LIFO mode).   Here, it seems to have skipped a
block somehow, and gone on to the next one in the file at once.

What happened?  Thanks!
----
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.

----
To unsubscribe, send email to majordomo at llamas.net with 'unsubscribe rc5' in the body.



More information about the rc5 mailing list