[rc5] 64-bit client oddity?

Jeff Woods jeff at delta.com
Thu Oct 23 12:13:09 EDT 1997


First, I removed the old version, the 56-bit GUI installed as a service.
I ran GUICNTRL.EXE and told it, yes, please remove the service when asked
-- it was NOT running at the time.  I also deleted the buff-in.rc5 and
buff-out.rc5 files.  

I then got the Win95/CLI (non-hidden) version, and set up this config file
for my single CPU Pentium 200 non MMX, for the 64-bit client:

[parameters]
id=jeff at delta.com
threshold=20:20
count=0
hours=0
timeslice=65536
niceness=0
logname=rc564.log
firemode=1
cputype=0
messagelen=0
smtpsrvr=mail.delta.com
smtpport=25
smtpfrom=RC5notify
smtpdest=jeff at delta.com
numcpu=1
checkpointfile=ckpoint.rc5
randomprefix=100

--------

Now, it started up fine, and did this (hand-typed, since can't cut and paste):

[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.



More information about the rc5 mailing list