• 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.

D20L Welcomes TA_Federation, Amok, redly1 and JHutch to the Team!

mastertech01

Moderator Emeritus Elite Member
Ive had tremendous network problems and great difficulty getting all my machines reporting, but I did stop by and noticed two new members of the TeAm and couldnt find any introductory thread for them so here it is. Im sorry we are late.

Welcome to TA Federation and JHutch to the D2OL Team and we are VERY happy to have you aboard! 😀 Thanks for signing on with us!

Edit1: Hey added two more members overnight! Now up to 91! 😀 Welcome Amok and redly1 to the TeAm! Great to have you aboard!
 
Welcome to the D2OL team TA_Federation and JHutch. Just in time to help us stomp up two more places tomorrow.

Hope your stay is long and prosperous.

Slatz
 
Hehe,
thx for the warm welcome. 😉

Although I'm the only Fed member currently doing D2OL for now, maybe some will join me.
With this client and the setup by the D2OL crew it is very easy to monitor all results send in by individual machines.
If I can get more Fed members to do it, maybe we can use the node-ID to distinguish the different contributors. 😀
 
Just for the record I have dabbled in D2OL and I'm a Feds member 🙂

If I pick it up again (let me know when there is a stable client!) I'll be sure to crunch under the Feds name.

Regards
 
Thanks for the welcome. Its good to be back 😉.

But, I also seem to be having a problem already 🙁. I loaded the client and turned it loose last night, and after a little while checked to insure that it was running smoothly, and it had went through a couple of candidates np. Then I went to bed, woke up, and noticed that it was initializing after having processed 8 candidates overnight. I thought it was kindof slow to have only went through 8, but decided it just takes a while and went on my way. Came back several hours later, and it was still initializing and hadn't processed any more data. I killed the client and just now started it back up. Hopefully it will get back into gear and resume processing data. If not, I may be back in a little while to get you guys to help me figure out what's wrong.
 
It may have a corrupted candidate.. if it does it again Geoffs can direct you on how to flush the candidates so it wont come back into cue. There have been a few of these lately
 
Back
Top