• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Whats easiest way to get a non-networked machine RC5 cracking?

kmmatney

Diamond Member
I want to have a few extra non-netwroked machines RC5 cracking over the weekend. What's the best way to go about doing this? Can I just start the client from a floppy on a networked computer, download a lot of workunits, and then set it going on the non-networked machines? Then re-run it on a networked machine? Anyone do this before )I would guess so).
 
You got it, we call it "sneakernetting." When it's time to harvest your output, shut down the client, *cut* the buff-out.rc5 file and paste it into a folder for safekeeping, in case your floppy is corrupted. Then stop the client on a networked machine, paste the buff-out.rc5 file into its folder, and restart it. It'll send in your WUs on behalf of your non-networked machine.

By the way, if you're a new member of Team AnandTech, welcome to the Team! 🙂
 
kmmatney, I faced that same problem. What I did is I installed the client on a network share, then ran it from that network share on each of the computers (you just have to make sure the INI file is set up right, which is very simple). Then, you use email to "fetch" the blocks and update the installation on the share to provide all the pc's with work to do. Every few days, you take the buff-out.rc5 file on that shared directory, cut it, and email it to dnetc to "flush".
Works very well, except that depending on the number of PC's you have, you have to flush fairly often to avoid *ahem* doing a bad megaflush 😱

If you need any help setting it up, drop me a PM or email.
 
Good ideas above, if there is no internet connection on those machines, you may also wish to consider Sneaky. You load Sneaky in the Dnet folder in your non-networked machines and one that has the internet connection. You can then use Sneaky to copy WU's onto a floppy, transfer to your hungry herd and then fetch and flush back to your connected machine.
 
<Then stop the client on a networked machine, paste the buff-out.rc5 file into its folder>

DON&quot;T forget to flush the networked PC's outbuffer first, or you will wipeout it's work! :Q

The Sneaky program is the best way to go! 😀

But, if it doesn't work for you, here is what you can do manually:

To get fresh WUs to crunch:
On the networked PC:
o Stop the client
o rename the buff-in.rc5 file to buff-inhold.rc5
o change the dnetc.ini file parms:

[rc5]
fetch-workunit-threshold=64000 <--- set to a large multiple of 32 to pull in the max amount of WUs, or just above the amount the PC will crunch until the next time you can fetch/flush
preferred-blocksize=33

o At the command line, in the dnet directory, Do a DNETC.EXE -fetch
o rename that buff-in.rc5 file to buff-ina.rc5

o repeat the fetch and rename for as many WUs as you need, or for as many PCs as you need, incrementing the file name: buff0inb.rc5, buff-inc.rc5

o Once you have the amount of WUs you need for a PC, copy the buff-in files (except the original renamed file to floppy), rename the buff-inhold.rc5 back to buff-in.rc5 and restart the client.

At the non-networked PC:
o copy the # of buff-in files you need for this PC to the dnet directory on the HD
o go to the command line, and go to the dnet directory
o run the command DNETC.EXE -import buff-ina.rc5

o repeat for each of the buff-in files you have for this PC. Nice thing is, you don't have to stop the client!

0 repeat for each non-networked PC


Now, to move the output buffers from the non-networked PCs to the networked PC:
On the non-networked PC:
o Stop the client
o rename the buff-out.rc5 file to buff-outa.rc5
o copy the buff-outa.rc5 file to floppy
0 restart the client

o repeat for each non-networked PC, making sure to give each output buffer a different name

At the Networked PC:
o copy the buff-out files from the floppy to the dnet directory on the hard drive
o go to the command line, go to the dnet directory, and run DNETC.EXE -import buff-outa.rc5

o repeat for each buff-out file
0 run the DNETC.EXE -flush command once all the buff-out files have been imported.


 
Thanks for the replies. I'll be able to bring in 2 Athlon 900's,2 Pentium 1 GHz machines, and and a Duron 750 this way. I'll look into the Sneaky program first. Then try the last method if it doesn't work. I just need to make a guess at the WU I need for each machine.
 
You can go Here to the speed page, and figure out the keyrate. Then you can do the math to figure out approximately how many WUs you will need for each one. 🙂
 
You can also just email-fetch new buffer files and email-flush completed buffer files.

but for a couple bucks, you could get a cheap network card too. 🙂
 
Well, these computers are in a somewhat remote warehouse. No easy/cheap way to network them. Sneaky seems to work OK. The main problem I have is hooking up to the proxy.teamanadtech.com server. It hardly ever works on my work computer, so I have to keep resetting the client to auto-find the keyserver. Setting the keyserver to autofind allows me to connect up and get packets to work on. My computers have spent way too much idle time not being to hook up to the TeamAnandtech proxy server.
 
Back
Top