Permission to come aboard
With little fanfare, I have joined your plucky little team. I have been cracking for just under two weeks, have some observations, and some questions.
I run dnet on 5 PCs, three mediocre ones at work, but with Net connection, a really slow PC at home and an Athlon 800 at home that cracks one unit every two minutes. Unfortunately, the two at home have no Net connection, so I have to do the sneaker-net turmoil. I was please to see that I hit 2nd page in less than a week, only because the majority of the 2nd and third page are abandoned cars. As of this writing I am number 175 and gaining ground.
My question concerns sneaker-netting. I have looked at the very sketchy instruction provided by this team, and I have also read the official help file provided by d-net. In the help file, users are instructed to:
* create a ckpoint.cp file on your non-networked machine
* email dnet for more blocks and save to floppy
* copy the buff-in file to ckpoint, something which I am afraid I don't know how to do in Windows. I am resigned to open a command line and type 'copy a:\buff-in.rc5 c:\dnet\ckpoint.cp
The client supposedly imports the blocks from ckpoint.cp to buff-in.rc5.
My questions are: if there are already blocks in buff-in, are they overwritten during the import process?
When the client is running, I see the number of units in buff-out, waiting to be flushed, but the number of units in buff-in always remains at zero. Namely, I never know how many units are currently waiting to be cracked. Therefore I run the risk of the home PCs finishing the buffer and then sitting there, wasting time and CPU cycles, until I get around to importing more blocks.
Am I doing something wrong?
I run a lot of machines sneaker net, never messed with a checkpoint file. I get massive amounts of blocks via e-mail, save them to disk and rename them as I save (1, 2, 3 etc). I then move the blocks from floppy, to the distributed.net directory on the machine. Then open a DOS windows, change to the distributed.net directory and type: dnetc -import 1 <hit enter> I add enough blocks for about a week (on an AMD 900, I would add 3 sets of 3000 blocks (by e-mail you would ask for: numblocks=3000) to add the second set of blocks, type in dnetc -import 2 and so on (or hit F3 and backspace to change the 1 to a 2)). Your buff-out file well hold all the completed work. When you get ready to dump your blocks, throw it a clean floppy, go to the dnet directory, change the buff-out file to 1 (2, 3 whatever) cut and paste it to the floppy, then go to the next machine and do the same, just remember to give each buff-out file a different name. When you have them all on the floppy, go to the Internet machine, cut and paste the files to the dnet directory, open a DOS window, CD to distributed.net and: dnetc -import 1 etc to import all the files to the buff-out.rc5 file. Then flush!
Welcome to the team!
Welcome aboard Rayven
I think Randy's post says it all.
permission granted , welcome aboard.
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke