Team Warped (OS/2)

I ever was wondering why my Athlon1GHz had a crunching rate at only 7-8 Mnodes/s. Well its not a hot new system, I agree, but even real oldies like the P-II’s (300-400MHz) I have in my herd were not that far away at around 5 Mnodes/s, and the P-III 700MHz in my HP Omnibook was crunching at almost 10Mnodes/s.
Why the hack was the fastest CPU that slow compared to the others?

Then, although I must have known that earlier, while checking my herd statistics on ‘the Cowboy’ I realised that not all systems were running the same or similar client versions.
The recently installed clients on the P4 and AMD K8 dualcore WIN$ machines were on 2.9013-500, or -498 for the Win98 notebook,
the Linux test system P-II 400MHz has the the most actual client 2.9015-504 and my work horse eComStation was running on … shocked …
ancient 2.9008-490 (a version down from 2004).
But well, it is just a cruncher, a cracker doing some numbers back and forth and around, should not make a big deal…

Ok, lets get the newest from distributed.net.
Said… and done.
Got 2.9015-504 for OS/2 and waited until the next packages were done. Stopped the crunchers, flushed buffers and copied the new client into the directory.
Fired it up and all is well - until I recognised the output….the crunching rate was now up to 13 Mnodes/s - almost double than before.
I have been a damn idiot running that old client for so long … wasting hours of crunching … wasting lots of kWh electricity.
All could have been so much more efficient…

Lesson learned: Always the newest client! Check the download page on distributed.net at least once in a term, if you are running an actual OS.

You may notice that the stats graphs here on the Cowboy site change format from time to time. You might also notice that the tabular stats stop updating off and on.

The reason is that I am working on a new version of Cowboy that won’t use so many CPU cycles when updating the pages here. Right now, updates bring the Cowboy server to its knees for 30-45 minutes, every 6 hours. When I test the new server software, it updates the stats site with different graphs and HTML.

I need it to capture lots of logs with the new software, so the old site will sometimes stop updating for a day or so - none of the logs are lost though. The old server processes them when I turn it back on.

Tests on the new software shows it can do the same job in about 3 minutes with little impact on the computer! I am getting rid of the old Nexus database and replacing it with MySQL.

Other stuff…

I just added a new OGR box named “Ferrari”, a

dual

Core-2 Quad machine. Thats right - the equivalent of 8 CPU’s in a single box! It won’t be up full time until maybe Monday, but it should ramp up our team’s OGR rate a bit.

A quick run-up showed each core doing about 26 meganodes per second - not too shabby:

[Apr 10 22:57:25 UTC] Automatic processor detection found 8 processors.
[Apr 10 22:57:25 UTC] Loading crunchers with work…
[Apr 10 22:57:26 UTC] The keyserver says: “Moo from the new and improved
haystack.ivo.nu”
[Apr 10 22:57:26 UTC] Retrieved project state data from server. (cached)
[Apr 10 22:57:28 UTC] OGR-P2: Retrieved 28 packets from server.
[Apr 10 22:57:28 UTC] Automatic processor type detection found
an Intel Pentium III (Katmai) processor.
[Apr 10 22:57:28 UTC] OGR-P2: using core #3 (GARSP 6.0-asm-rt1-mmx).
[Apr 10 22:57:28 UTC] OGR-P2 #a: Loaded 25/11-23-6-2-28
[Apr 10 22:57:28 UTC] OGR-P2 #b: Loaded 25/11-23-6-2-30
[Apr 10 22:57:28 UTC] OGR-P2 #c: Loaded 25/11-23-6-2-33
[Apr 10 22:57:28 UTC] OGR-P2 #d: Loaded 25/11-23-6-2-50
[Apr 10 22:57:28 UTC] OGR-P2 #e: Loaded 25/11-23-6-2-51
[Apr 10 22:57:28 UTC] OGR-P2 #f: Loaded 25/11-23-6-2-52
[Apr 10 22:57:28 UTC] OGR-P2 #g: Loaded 25/11-23-6-2-53
[Apr 10 22:57:28 UTC] OGR-P2 #h: Loaded 25/11-23-6-2-54
[Apr 10 22:57:28 UTC] OGR-P2: 20 packets remain in buff-in.ogf
[Apr 10 22:57:28 UTC] OGR-P2: 0 packets are in buff-out.ogf
[Apr 10 22:57:28 UTC] 8 crunchers (’a'-’h') have been started.
[Apr 10 23:00:27 UTC] *Break* Shutting down…
[Apr 10 23:00:27 UTC] OGR-P2 #h: Saved 25/11-23-6-2-54 (4.79 Gnodes done)
0.00:02:59.23 - [26,697,614 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #g: Saved 25/11-23-6-2-53 (5.21 Gnodes done)
0.00:02:59.23 - [29,076,747 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #f: Saved 25/11-23-6-2-52 (5.12 Gnodes done)
0.00:02:59.23 - [28,564,086 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #e: Saved 25/11-23-6-2-51 (4.79 Gnodes done)
0.00:02:59.23 - [26,741,590 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #d: Saved 25/11-23-6-2-50 (5.29 Gnodes done)
0.00:02:59.23 - [29,530,347 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #c: Saved 25/11-23-6-2-33 (4.65 Gnodes done)
0.00:02:59.23 - [25,916,046 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #b: Saved 25/11-23-6-2-30 (4.57 Gnodes done)
0.00:02:59.23 - [25,478,305 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2 #a: Saved 25/11-23-6-2-28 (5.12 Gnodes done)
0.00:02:59.23 - [28,540,177 nodes/s]
[Apr 10 23:00:27 UTC] OGR-P2: 28 packets are in buff-in.ogf
[Apr 10 23:00:27 UTC] OGR-P2: 0 packets are in buff-out.ogf
[Apr 10 23:00:27 UTC] Shutdown complete.

Kevin

I did some quick debugging of the Cowboy server code, fixed some bugs and replaced a missing file.

It seems to be working again after a day or two down time. Your stats here on Cowboy should come back to normal over the next few days/weeks. The outage will not affect your cracking rate on DNET.

We now have an overclocked Intel Core 2 Quad, water cooled stats server.

Click here for some photos.

Kevin

I am moving the web server and the Cowboy stats engine to Samovar. There are some teething pain issues that I am struggling with. I have installed the latest Apache, PHP, Perl, and am still configuring things.

There may be delays in Cowboy stats updates and my blogs seem to have a slight case of Alzheimer’s.

Hang in there!

Kevin

I just bought a replacement for Deepblue, the Cowboy server. I mention it, because the replacement should be a screamer. Deepblue is getting a bit long in the tooth and needs a new PSU and fans - I’ll keep it in my herd, but have decided to shift it to my wife’s office to replace her even slower computer. Gobbles, her old machine, will begin CAD duty in my art studio and will continue to crunch on OGR.

The new box is going to be an overclocked, water-cooled Intel Quad-Core 2 with 2 GB of RAM, 4 SATA RAID 0+1 drives and an overclocked gamer video card. The video card is supposedly compatible with the next generation of OGR/RC5 crunchers that should outrun even the Quad processor CPU! Watch for new DNET clients that can run on the processor in your video card. Video cards have the capability of crunching much faster than a motherboard CPU. Hopefully, I’ll be able to crunch OGR work on the Quad CPU and the video card simultaneously. In the short term, it will be CPU crunching only.

It will take a while to build it (the parts are currently on order from Newegg.com) and to configure it. Newegg says the parts should arrive sometime next week. Look for a machine named Samovar (named after the water cooling system) in my herd in the next couple weeks. I’ll post pictures soon.

Here is the list of hardware components in: Samovar

Kevin

It looks like the OGR contest has run out of easy to crunch blocks, and now most of my cows (and probably yours too) are working on slower-to-crunch ones. I have adjusted all my DNETC.INI settings as follows:

[ogr_p2]
fetch-workunit-threshold=xx

decreasing them by half. If it used to say “30″, I reset them to 15.

If the threshold number is too large, it will take days to weeks to crunch all your blocks. Your graphs will get spiky looking. If the number is too small, your cow will be asking the server or proxy for new blocks all the time, and that is inefficient.

If we start crunching easier blocks in the future, then we can all adjust this number upwards to cut down on network bandwidth. I’ll keep you posted.

Kevin

The following message was posted by Bovine on the RC5 mailing list the other day. I’ll post it here for anyone that is not a mailing list subscriber:

Dear friends,

It is with great sadness that we must announce that RSA Labs has
decided to terminate the RSA Secret-Key Challenge, which impacts the
RC5-72 project and all of the remaining RC5 challenges. This means
that RSA Labs will not confirm any solutions or award any additional
prizes, should a correct solution be found. Furthermore, we have
received a statement indicating that they will not be disclosing the
solutions to the unsolved challenges. More details can be found on
http://www.rsa.com/rsalabs/node.asp?id=2100 (Note that the page should
state that the RC5-32/12/8 solution was recovered on 14 July 2002, not
28 January 1997.)

Although RSA Labs is halting their official sponsorship, there is
still the option open to us to continue the project without their
prize or validation. We would like to solicit your feedback regarding
this option. Discussion is welcome on our rc5 mailing list (see
http://lists.distributed.net/mailman/listinfo/rc5 if you are not
already a member). In the coming days, we will provide a facility to
allow official votes to be made.

If the choice to discontinue the RC5-72 project is made, the official
transition plan will be as follows: In one week’s time from the
announced decision, the distributed.net keyservers will begin
indicating that the RC5-72 project is closed to all connecting dnetc
clients. All results received after that time will be discarded. A
couple of days before then, we will begin slowing down RC5 work unit
generation to allow the network to drain. If we receive sufficient
feedback indicating that you would like us to continue operating the
RC5-72 project, we will continue to generate work units and the
project will remain open.

We intend to continue operating the OGRp2 project, and are currently
in the development stages of additional types of projects. More
details regarding these future projects will be announced at a later
date. In the mean time, we encourage everyone to continue
participating in both the RC5-72 and OGRp2 projects.

Moo! ]:8)

Currently, the RC5 mailing list members are discussing the future of RC5 (OGR will continue as before). Some members want to cancel the contest and move on to some other contest, others want to continue RC5 without the prize money. Confirming the “winning” key might be problematic, since we won’t have a neutral referee (RSA Labs) and the complete plain text of the encrypted phrase is unknown.

Continuing would mean many more years of work, especially if there is a substantial drop of in participation. Note that the RC5 contest is currently at less than 1/2 % complete and it has been running for several years.

If you have an opinion on this matter, you might want to subscribe to the mailing list (go to the dnet web site and follow the links) and voice it quickly.

It may be a while before new contest cores can be written for the DNET client, if the decision is made to cancel RC5 support and replace it with a different contest.

I anticipate that most of the other teams will switch to OGR, at least in the short term. This will put a lot of pressure on us, if we want to stay as highly ranked as we are. I’m doing my part, but we will need some more CPU cycles to stay on top in the long term. Think about upgrading your older machines and adding friends, family and neighbors machines to the effort. Try overclocking your older machines - it just might help!

I’d like to hear your views on the RC5 contest cancellation here too.

Kevin

Strange thing - my outgoing email up and quit the other day. Since I am a software developer, I ran through all the usual debugging tricks. It looked like my local ISP, Comcast, was somehow blocking my outgoing email traffic! Incoming still worked fine. I used my computer at work to email them and they swore blind that they weren’t blocking my mail. They lied.

It turns out that they are actually and they finally ‘fessed up tonight. In a misguided attempt at blocking spam they have decided to change the standard email port from 25 to port 587. This is the technical equivalent of moving a few doors down the block because you get too many traveling salesmen knocking at your door. The trouble is the salesmen will soon find your new address, and start banging on that one too.

Yes, changing ports will block spam on their system briefly. Just until the virus writers add a few lines of code to get the new Comcast email port number out of your registry and use that instead automatically using port 25. It will be back to business as usual and the spam floodgates will be wide open again. Only the Comcast customers suffer.

I just checked my Windows registry, and low and behold, the email port number is in there half a dozen times. If I were a virus writer (and I am most assuredly not!), it would take about an hour to write some programming code that grabs the non-standard port number and work around Comcast’s idiotic port switcheroo. I can assure you that such a virus development effort is well underway by script kiddies around the planet, even as I type this.

The decision Comcast made to change email ports is just plain stupid on several levels. It will result in a massive tech support headache for them - just about every customer that has their standard email port blocked will be calling them to get their email “turned back on” again. They will have to walk tens of thousands of twit users through the process of reconfiguring their email browser. I wonder how the Comcast stockholders would feel about a poorly informed business decision that will hit their bottom line big time. Tech support is a major expense for an ISP.

Comcast tech support informs me that they are phasing this policy in, system-wide. I just got hit early on. I had a most unpleasant phone conversation with them, and they refused to unblock the port on my cable modem.

The good news: My “home” ISP (yes I have two of them) was sympathetic and offered a solution - they have an alternate email server port open that I can use instead of the blocked port 25. Kudos to Westnet/Silicon Beach out in California for being customer oriented and quick to offer a good solution. Westnet really knows how to run a business, and I have been very happy with their tech support over the years.

My advice is to avoid Comcast as an ISP. If they are dumb enough to make a major change to a basic service like this without informing their victims (oops, I meant customers) then what’s next?

Kevin

We are getting close to moving up to #5 in the world on OGR! If Team AnandTech keeps up their current rate and we do too, then we will overtake them in about 70 days from today!

Lets go Team Warped!

I will provide updates as we get closer to passing them.

Great work guys!

Kevin

I just added Poindexter, an LGA775 Intel Quad-core computer running at 2.7 GHz per core, overclocked from its base CPU speed of 2.4 GHz. So far, it seem stable at 15% overclocking, so I’ll keep it at that speed until something breaks, then maybe back off on the overclocking. Its nice and toasty warm at 75C on the CPU chip.

Hmm…. I have a little cooling capacity left, so maybe it will work at 20% overclocking? I’ll find out soon

I used the ASUS Striker Extreme motherboard with 2 GB of RAM and RAID-5 drives for a total of around 230 GB of HDD. This sucker cooks

Its a total gamer system, but I am using it for software development and DNET only. I got a totally riced-out mini-tower computer case, with a light-up Nissan 350Z logo on the front panel. I thought it appropriate, since that is my daily ride to work

Got a hot new DNET workstation? Tell us about it on the blog! Post some pictures too.

Kevin

Colin Hildinger, the originator of Team Warped has returned after a long hiatus! He is currently submitting log files to the Cowboy server and is a welcome (re)addition to our team. Colin has not been able to do much with DNET over the last few years due to work constraints, but is now back in style. Please make him feel welcome.

Lets crack some keys!

Kevin

Well, we got kicked out of the #5 position in team ranking by Ars Techinica Roast Beef, pushing us back down to #6 in the world. Roast Beef’s key rate is only slightly faster than ours, so if we can pour on the coal, it might be possible to catch up with them again. We should be back up at #5 in about 3 months - if we maintain our work rate and one of the slower teams maintains theirs.

I just added a couple of dual processor machines and a fast AMD box. Check out Taz (weighing in at 107 Meganodes per second!), Papasmurf, zipping along in the high 80 Meganodes/Sec, and Pepper, running about 70 Mn/Sec. Papasmurf is still being installed, so it won’t be online 24/7 for a few more days - I am not sure how fast this one is, but it may even outrun Taz.

Happy crunching!

Kevin

Kevin,

I just wanted to let you know that I finally got all my cows back up and running. You will see them now under the verizon.net address. I moved over every thing to that email address also on distributed.net. One or two machines may come up and down periodically as I do some more tweaking but I think I got them all going now.

Bob Bencivenga

OS/2 Die Hard

Sorry folks - last Thursdays storm knocked down a large portion of Washington State’s power grid and I just now got the lights back on. Team Warped Towers suffered from downed trees, no heat and water, and worst of all, no septic system.

Some of the downed trees came within inches of destroying buildings on my property and that of my immediate neighbors, so this was pretty serious.
The good news for the Team Warped membership is that I am investing in a standby generator to handle such emergencies in the future. The Genrac guy should be out tomorrow to give me a quote. I am tired of camping out in my own home.

Anyway, Cowboy is back up and running and your stats should recover in a week or two. They really weren’t affected by the Cowboy outage, since you still submit work directly to Distributed.net, even if Cowboy is off line.

Write me if you have any questions.

Happy holidays!

Kevin

The Cowboy site and this blog have been up and down the last two days due to internet connectivity issues and an unrelated power outage.
My cable modem provider dissconected me by mistake for about 18 hours and I am having some major electrical work done here at the Team Warped Towers industrial complex.
Everything should be back up and running now. We are still waiting for the Dnet stats server to come back up, but thats another story…

Kevin

I’d like to welcome Juergen Gaida to the Team Warped web site. Check out his stats here!

Kevin

The vast Team Warped web stats server room got a little quiet the last 36 hours or so. The lights were on, but apparently nobody was home.

I finally figured out that Cowboy runs a lot faster if you actually plug it into the LAN. Its back on line and accepting log messages from your cows again. Sorry for the droop in everyones stat graphs, but your actual work got logged on DNET. Not to worry!

I don’t know if my router/firewall hiccuped or if I have a flakey CAT5 cable. Everything was plugged in, but there was no connection from Deepblue to the outside world. I power-cycled everything and it is working again. We did have a power bump or two and torrential rains the last few days - maybe that was it.
Now, if Fiddles and Decibel can figure out whats wrong with the DNET stats server and fix it once and for all…
Kevin

Since Collin Hildinger dropped out of the DNET challenge about 2 years ago, we have effectively been without a team captain.

I wrote Decibel at DNET a month or two ago, mostly looking for a way to get in touch with Collin (who seems to have fallen off the face of the Earth). Decibel posted a message on our team page stating that I wanted to be captain! Well, that wasn’t exactly true, but time passed and nobody complained about the potential management change, so today, Decibel sent me the captain’s password.

I am happy to report that I have accepted the postion and hope to take our team into its second decade of operation.

I have been working on the DNET challenge for 9 years this month, all of it on Team Warped!

Please note that the captain is simply the contact person for the team - it is not like I get a 7-figure salary and a corporate jet or anything.

As my first official act, I have slightly updated the OS/2 blurb and redirected the link from the IBM Warp site to the eComStation site. I also put a link to the Cowboy site and this blog, inviting any other Team Warped members to drop by and chat or post their stats. I left most of the rest of the text the same.

The old IBM Warp link mostly talked about moving off OS/2 and on to windoze and Linux, so I didn’t think it was appropriate.
I invite other team members to submit text for our Distributed.net Team Warped page. I am still running Warp 4, so I don’t know much about eCS. If someone has some interesting information about eCS that would fit on the Team Warped description page, send it to me and I’ll be happy to post it. It has to be short - about the same length as the current text, so don’t get too long winded.

I hope to hear some ideas for the team page soon!

Kevin

Are you running a windoze box with an AMD CPU? Check out the new beta client on distributed.net. Its a good bit faster than the non-AMD-optimized ones. Look for version 498. There isn’t one out for OS/2 yet, but they usually follow up in a month or two on the other platforms. The new client doesn’t do anything for Intel processors, so if you aren’t running AMD/Windoze, I wouldn’t bother.

You really should be running at least v497 on all your machines though. This 497 is substantially faster than the older ones on Intel processors.

If you want to upgrade dnetc.exe, here is how you do it:

Don’t forget to flush your old work units before installing (overwriting) the old dnetc.exe with the new one. You can do that by opening a dos box and running:

c:\program files\distributed.net> dnetc -flush

Wait for the flush to finish. Then enter the following command if you are running dnetc as a windoze service (highly recommended):

c:\program files\distributed.net> dnetc -shutdown

Then overwrite dnec.exe with the new one

now delete the old, empty data files:

c:\program files\distributed.net>del *.ogf

c:\program files\distributed.net>del *.r??

delete your checkpoint file, if any:

c:\program files\distributed.net>del *.bin

Now execute the following commands if you want to run dnetc as a service, otherwise, just restart dnetc and you are done.

If you switch from running as a startup folder option to running as a service, you’ll lose the on-screen graphics, but you’ll gain a cleaner desktop and slightly better performance. If dnetc is running on someone elses machine, then running as a service is the way to go, since the end user can’t easily mess with the program settings or stop it. The service runs silently hidden in the background and
most users won’t notice its there. To install as a service do the following:
install service:

c:\program files\distributed.net> dnetc -install

start the service (run dnet)

c:\program files\distributed.net> dnetc -svcstart

Services automatically restart themselves on bootup, so you don’t need anything special for dnet in the startup folder.

Thats it!

Kevin

Fiddles at Distributed.net reports the stats server is back up and running, but as of this post, it is still about a week behind in processing stats. Cowboy will report your correct standings as soon as the dnet web site starts reporting up-to-date stats on everyone. Stay tuned!

Kevin

I just upgraded the blog software here to the latest version. Let me know if there are any issues.

Kevin

It is now about 4 days until we reach #5 in the world!

At our current rate we should move up to the #4 slot in a little over a year - assuming the other teams above and below us don’t pour on the coal.

Kevin

If we hold our current workunit rate and Team Slashdot does the same, we will pass them by in about a month - well ahead of schedule. That will move us up to the #5 position in the world!

Keep up the great work guys!

Kevin

Some of you are sending log emails every 10 minutes or so from a given cow. Please take the time to check your Logs Per Day stats, found on your “View your individual cow stats” page. If your Logs/Day number is bigger than 12, you need to increase your mail log size in DNETC.INI:

mail-log-max=xxxxx

If you have a 20 Meganode/Second or faster machine, then you need to set xxxxx above to be at least 16324. The optimal setting is one that gives you an average of 6-12 logs per day. The logs/day number is your average over 90 days, so it will take a while for the number to decrease after a change to your INI files.

Note that sending fewer logs per day *can* result in a higher block rate, so its in your best interest too.

I know - its my fault since I had a much lower number in my original setup instructions The latest DNET client that many of you are running seems to take poetic license with the log max number and actually send just a couple hundred bytes in each log message. Cowboy is processing 800-900 emails a day now and that number is increasing steadily.

I was the prime offender up until recently, and had to run around to all my cows and reconfigure their INI files. I have 46 cows in my herd, so I was a busy guy. I have high numbers now due to 90 day averaging, but they are dropping fast. I feel so much better

Anyway, if you could crank your cows down a notch or two we can up our combined keyrate a bit - thats a good thing!

Kevin

I just checked and found that DNET is again processing stats! Cowboy should spider the DNET site soon and update your overall herd stats, if it hasn’t done so already.

The distributed.net stats server as been off line for the last couple days. Cowboy continues to analyze logs and create cow stats graphs, but your team standings and overall work rate graphs will not update until DNET comes back on line. Check the DNET plan files for repair times and details.

It’s unclear to me whether to use this area as a support “forum”, but let’s see if I get swatted . . .

Hmmm . . . no “preview post feature”. Guess I’ll have to get it right the first time, including tags.

[later]
Oh, I see, no Preview button, but it does Preview after saving. Weird. No “Help” button either. I guess folks who use this sort of thing already know how and what and where. Like sex without a manual, eh?

No obvious way to conclude and post. Save, yes. Post, no. Don’t mind me, if you’re reading this, I must have figured it out.

=======================

I have five boxes running the dnetc client: two OS/2 and three Win of various flavours (95/98/XP). Only the stats for the two OS/2 boxes show up at my stats page.

The W95 & W98 boxen are on the same lan as the two OS/2 boxes.

The W98 box actually shows something that looks relevent:

[Mar 23 02:44:03 UTC] RC5-72: 20 packets (20.00 stats units) are in
buff-out.r72
[Mar 23 03:42:14 UTC] Connect to host 67.168.104.177:250 failed.
ETIMEDOUT: The connection timed out
[Mar 23 03:42:14 UTC] Mail:: Send deferred.
[Mar 23 03:41:29 UTC] RC5-72: Completed CB:3EEC5E0D:00000000 (1.00 stats units)
0.00:59:40.44 - [1,199,581 keys/s]

I see this same thing over & over.

The W95 box shows something very similar:

[Mar 23 02:44:03 UTC] RC5-72: 20 packets (20.00 stats units) are in
buff-out.r72
[Mar 23 03:42:14 UTC] Connect to host 67.168.104.177:250 failed.
ETIMEDOUT: The connection timed out
[Mar 23 03:42:14 UTC] Mail:: Send deferred.
[Mar 23 03:41:29 UTC] RC5-72: Completed CB:3EEC5E0D:00000000 (1.00 stats units)
0.00:59:40.44 - [1,199,581 keys/s]

I don’t recall what the XP box shows; it’s at work.

I’d like to welcome Al Savage - a fellow Washingtonian to our group. He has been active on DNET since 1998 in various challenges and is a welcome addition to our group!

We hope you enjoy the stats pages and please feel free to post here on the Team Warped (OS/2) Blog!

Kevin

As predicted, we have reached #6 in the world!

If #distributed can keep up the pace, they will catch up with us in about 36 days from today. I don’t see any other contenders threatening us, so we will likely hold on to the #6 or #7 spot for a while. Slashdot and Anandtech have slacked off considerably in the OGR challenge, so they are vulnerable to our superior workrate. We should catch Slashdot sometime in Fall 2006, at our current rates.

Keep up the great workrate and keep those cows mooooving!

Kevin

As I said before, Team “EvangeLista (Macs Rule! :-)” should fall to us soon, followed by Team “Slashdot.org 1365″ in a week or two. Team “#distributed” should overtake us soon, but the overall effect is that we will move up to #6 in the world and stay there for a while.

I have added several new cows and am working on adding a few more as soon as I can solve some firewall issues.

We need everyone’s help on this to add more workstations to the effort. If you can’t do that, then please update to the latest v2.9012.497 DNET client. It is MUCH faster than the old one you are probably using. I saw a 30% increase in speed on most of my cows by simply overwriting the old DNETC.EXE with the new one and launching it. Download the latest DNET client from here and install it NOW! This is a complete no-brainer. There are windoze and OS/2 versions of the same client. I think our Linux contingent has already upgraded.

Anyway, thanks for the CPU cycles. I really appreciate your help in this effort!

Kevin