PPROXY ADDRESS

[cwizard]

Virus has done a great job with the pproxy stats. The address is:

http://24.72.9.177/byemail.php

For all you new sysopt RC5 team members. Configure the client to upload to the pproxy to show up on the stats:

keyserver: 24.72.9.177 port:8080 (NEVER FALL BACK.) This parameter may not be available in the new clients. If you can't find it, you don't need it.

[This message has been edited by cwizard (edited 10-02-99).]

Made link active for lazy people like me -Joel

[This message has been edited by Joel Kleppinger (edited 10-02-99).]

[NoCtrl]

There really should be a few words about Virus's proxy page and a link from SysOpt.com. It would be very helpfull and I think Virus more than deserves it for the effort.

[izzzy12k]

I think so too.

Maybe we outta create a topic here in this forum for everyone to put some feedback and ideas for our RC5 team page.

izzzy12k

[This message has been edited by izzzy12k (edited 10-03-99).]

[cwizard]

I agree that Virus needs to get some credit and RC5 a more noticeable presence on Sysopt. I read the link that Izzzy12k put to some equipment sales a while back and when I went there it was the Anadtech guy that was running their warpcorp project liquidating the equipment to try to pay for it. I thought it was rotten that the Anadtech team members abandoned the guy who was running their warpcorp project leaving him holding the bag with a big electric bill and thousands of dollars out of his own pocket. That's not right.

Virus has built a really sophisticated stats database and is maintaining it with his own expenses in terms of equipment and connection time and, in my opinion due to the frequent feedback, it would serve as a motivator for those team members who are cracking without enthusiasm. When you can see the results frequently, you tend to consider how you can increase your output.

Just my 1.75 worth (2c adjusted for inflation)

[codybear]

i have two other systems sitting idle that can be used for crunching....can I somehow transfer the finished blocks to my main computer and send them from it??

the other ones are a 233 and a 300 but as of now neither have modems....

[skippy]

Yes, you can get those other computers crunching blocks! Grab some blocks by sending a message to fetch@distributed.net
with the message:
blocksize=xx
numblocks=xxx
You can choose a size between 28 and 33 for the blocksize (33 is only available on new clients. If you are not sure, stick with 31 since it is pretty safe between the clients)
numblocks can be any number between 1 and 500. You might want to make this one high so you don't have to do this all the time.

Then load the rc5 client on a floppy along with the file (buff-in.rc5)that distributed will send you. Set up the client and move the buff-in to the folder that the client installed to.

To retrieve the blocks when they are completed, copy the buff-out.rc5 to a floppy and move that file to your main computer's folder with the rc5 client in it. (WARNING- you will overwrite the blocks that are on the main computer, so do a flush first so your buff-out is empty.) Once they are on your comp, choose flush and they will be sent.

Be sure and use the same client on all machines when you do this!

[SysOpt]

I agree... Take a look:
http://www.sysopt.com/rc5team.html

I made two mentions of the proxy stats server.

Scott

[This message has been edited by SysOpt (edited 10-03-99).]

[cwizard]

Codybear:

I see someone else answered your question but I have a different method that I use that works for me.

I have a bank of computers that are inconvenient to attach to a modem. This is what I do:

First, make sure you have the always offline option selected.

To get them started, on my internet attached machine, I changed the name of the buff-in.rc5 to buff-in.use. Then I did a manual fetch. This created a new buff-in.rc5. When it was completed, I changed the name of buff-in.rc5 to buff-in.1 and buff-in.use back to buff-in.rc5.

Then, I COPIED buff-in.1 to a:buff-in.rc5. The purpose is to prevent block loss if there is a mess up.

Take the buff-in.rc5 to the unattached machine. Copy the buff-in.rc5 file then erase it from the floppy to avoid duplicate processing. Start client.

Use the same method to retrieve the blocks. On the unattached machine stop the client and change buff-out.rc5 to buff-out.1. Copy buff-out.1 to floppy and transfer to internet connected machine. Change buff-out.rc5 to buff-out.use. Rename buff-out.1 to buff-out.rc5 and manually flush. When done, delete the empty buff-out.rc5 and rename buff-out.use to buff-out.rc5. Restart client.

To reload the remote machine, on remote machine change buff-in.rc5 to buff-in.1. Copy to floppy and take to internet machine, copy to internet machine. Change buff-in.rc5 to buff-in.use. Rename buff-in.1 buff-in.rc5 and reload. When done, change name back to buff-in.1 and buff-in.use back to buff-in.rc5. Copy buff-in.1 to floppy. Take back to remote machine and copy overwriting buff-in.1. Rename buff-in.1, buff-in.rc5. Start client.

When a fresh buffer is successfully crunching, you can delete the inbetween buff-in.1 files. When you have successfully upload the buff-out.1 files, you can delete them.

This is rather detailed but it is the only way I know to:

1. avoid processing duplicate blocks
2. avoid losing processed blocks to bad floppys or mistakes.

This process has saved me several times.

Hope this helps.

[NoCtrl]

Alright! Thank you Scott. [img]/forum/smile.gif[/img]

[This message has been edited by NoCtrl (edited 10-03-99).]

[cwizard]

The updated page looks good. Thanks.

[Virus]

I'm back. And boy am I glad to finally be back. Does it ever suck having no internet access. It's like being locked in a cage.

I've got lots of stuff to catch up on. My G400 is finally in (after 5 months). I got 5 new systems at work to setup for rc5 cracking. E-commerce software to finish by the 14th. And a lot of work to do on the new stats script.

BTW, thankz for all the wonderful comments. I really don't deserve all of the attention. It's Kevin Pesce that deserves your congrats. He is the creator of the stats script, that I and most rc5 teams use.