In light of yesterday, I want to join TA - But am I setup right ?

[KiLLaZ]

I've always ran SETI@Home for my own personal usage because distributed.net's "Telnet" like cliet has always scared me and I was always too lazy to figure it out.

Anyway, I wanna help TA back into #1 with my 1.2Ghz T-Bird and 950 Duron systems, but was just wondering if I was setup right. I have my e-mail address under general cliet options and have DES=0,CSC=0,OGR=0,RC5 under work load precedence. These are the only two settings I've changed and they are the same for both computers... Is this all I have to do ? Then just wait a day and sign up with TA ? Anything else to "optimize" my settings ?

Thanks a bunch in advance!

 

[ViRGE]

That should work for the most part. You may however want to check out the speed page to see how fast your cows will crack; so that you can customize the buffer sizes for better flushing times. Also, if you're a stats addict, check out http://www.teamanandtech.com/faqs/dnet/beginner/mika_proxy.asp to see how to use the team's personal Dnet proxy.

 

[Netopia]

KiLLaZ,

Your response (joining the team) is EXACTLY why I wish we could get LARGE and IMMEDIATE front page coverage that we have been displaced in addition to a PLEA from Anand for more people to join. I think that many would be willing, as are you, to either temorarily switch or crack if they haven't before.

At any rate... WELCOME!

Joe

 

[KiLLaZ]

Also, I was just wondering... how would one go about cracking on a computer with dial-up ? Can't stay connected ALL night....

 

[ViRGE]

You only need to be connected to exchage work units. The client can crack for days on it's own provided that it has enough WUs.

 

[TwoFace]

Hey KiLLaZ welcome to the TeAm

Here's a suggestion to what you should make your dnetc.ini look like if you're on dialup:

[parameters]
id=youremailaddy@whatever.com

[misc]
project-priority=RC5,DES,CSC,OGR

[display]
progress-indicator=auto-sense

[rc5]
fetch-time-threshold=72
preferred-blocksize=33

[ogr]
fetch-workunit-threshold=5

[networking]
nofallback=true
autofindkeyserver=no
keyserver=proxy.teamanandtech.com
dialup-watcher=passive

[logging]
log-file=log.log
log-file-type=fifo

This will set you up to do RC5 first, but still have a small buffer of OGR stubs in case you run out of RC5 work, the contest ends or something like that. It'll also fetch and flush whenever you're online with the comp and buffer enough RC5 blocks for 72 hours of work, you shouldn't have to do anything, but it won't dial out if it runs out of work. It'll flush to the RoundRobin of proxies that all flush to Mika's so you can check your stats here

That's all I can think of at the moment... good luck

With love and respect your fellow TA member

Two-Face

 

[dennilfloss]

Shouldn't it be dialup-watcher=active? I'm on 56k and mine updates its buffers as soon as a block is completed while I'm online but does not dialup by itself. BTW, my buffer (fetch-time work unit=) is set at 3000, just in case.

 

[TwoFace]

Ah Denis, active "should" dial out, but you can disable that from windows too, by "manually" dialing out everytime you need a connection or if you don't have the connect automatically option enabled... with it set to passive it won't try to connect PERIOD, if you're not online already

I used a time limit on the buffer instead of a set amount of WUs thus he can use the same .ini on several machines and they'll all buffer what's necessary to last 72 hours (in this case) according to their speed ... it's a little more elegant IMO, but there's nothing wrong with using a set buffersize if you know how much you need...

Might I suggest one little thing for you tho'? Set your limit to 3200 instead of 3000 that way you're using a multiple of 32 and won't cause unnecessary fragmentation of the keyspace

With love and respect your fellow TA member

Two-Face

 

[dennilfloss]

I also have the connect automatically option enabled in Windows and the TA Cube client never tries to connect on its own. However, it detects my connection very well.

Now I am confused since, AFAIK, all TA Cube dialup disks have connection-detect set to active and no one has ever reported it trying to connect.

I'll use 3200. At 3000, not all my blocks were of 32WU size but it always added up to 3000.

 

[TwoFace]

Ah, Denis I see why you're confused... at least I think I do... have you EVER ran out of blocks? I doubt you have as much as you're online

Try it once just for fun... set your block and buffersize to 1 and shutdown the client, rename the buff-in.rc5 and fire it up again... it'll then connect and fetch first one and then a second block. Disconnect from the net and let it crack those two blocks and you'll probably see it will dialout for you... it shouldn't dialout if the buffers aren't empty, if you haven't got frequent buffer checks on that is... I haven't looked at the borg disks, but I guess they don't have that otherwise I'm certain you would've heard about it Once it either dials or doesn't you can merge the old buff-in.rc5 with the new one by running the client with the -import <filename> option and you've got your old buffer back... remember to set the .ini back to blocksize 33 and buffer = 3200 tho'

Have fun

With love and respect your fellow TA member

Two-Face

 

[dennilfloss]

I indeed have never ran out of blocks. I made sure of that and I also suggest to all my recruits to have a 3000WU (now it will be 3200) buffer. I also have them manually update buffers at least twice a week because the automatic update sometimes stalls on DSL connections. I make them work their drone asses off.

I'm too lazy and about to go to bed. I'll take your word for it.

Russ is the authority on the Borg disks. I'm no techie, just a simple ass laminator.

 

[TwoFace]

Hehe, sleep tight Denis

I think I'll try once I get home from work... since I've actually never tried it myself... I just know how it *should* behave... oh well we'll see if I try it once

With love and respect your fellow TA member

Two-Face