[RC5] Win32 CLI 391 not checkpointing when using "-hide"

Ryan Curtis orion at baker.cnw.com
Wed Jan 28 13:32:28 EST 1998

I had a similar experience with the Win95 hidden client.  I entered 
"ckpoint.des" for the checkpoint file.  When the computer started up, it 
read the ckpoint.des file but never modified the file.  Everytime I 
started that computer, it would pick up the same two blocks from the 
checkpoint file and work on them.

When I put the entire path of the checkpoint file in the INI, it worked 
fine.  If you don't have the entire path called out, it seems to get lost.

dlmeyer at uiuc.edu wrote:

>Just downloaded and installed the new WIN32 CLI 391 client, for my NT SMP
>box, and decided to try something the "-hide" option on one of my single
>CPU NT workstations. In the process of setting up and testing, I noted
>that despite the CKPOINT2 value being set in both the INI and the
>commandline, the client does not create the checkpoint file. (Can only
>confirm under DES, did not check under RC5...)

To unsubcribe, send 'unsubscribe rc5' to majordomo at lists.distributed.net
rc5-digest subscribers replace rc5 with rc5-digest

More information about the rc5 mailing list