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

Seventeen or Bust Upgrade! - Edit: Bugs fixed!

Ken g6

Ken g6

Programming Moderator, Elite Member
Moderator
here!!! 😀😀😀

Edit3: All versions are now fixed! 🙂 Please update your clients as soon as possible, and for Windows clients, please delete your zXXXXXXXX files from V2.2 before continuing.

Previous edits:
Edit: Possible bug found by me. 🙁

If you haven't upgraded, maybe you should wait. If you have, and you decide to go back, be sure to delete all your z[0-9]* files first. And if you have a P4, it'd be nice if someone could test v2.0 for the bug.

Edit2: Louie is working on a fix. Since all V2.2 results will have to be retested, it's probably better to go back to V1.x or 2.0 for now.
Click to expand...
 
Okay, so I was being a little too dramatic. 😛

But the new client helps all kinds of machines to some degree. Apparently, it even helps P4s a little, too. 🙂

P.S. For any newbies installing the new client, don't uninstall the previous version. If you do, here's what to do.
 
Thanks Ken_g6!!!

I will update my crunchers accordingly.

Unfortunately I will be losing the use of most of my SoB fleet. Sneakernetting won't be possible for about two months. I am adding some crunchers on my home fleet to compensate though 🙂
 
Suggestion:

If your problem is that you can't get to the crunchers for two months, not that you're losing them, here's what I suggest. While you have access, store up nine or so sequential results sneakernetted from each system. Maybe make a copy once every hour for a work day (you can automate this if you can script). Then take those home, and send one in, in sequence, once a week. By the end of that time, the work units should be done, and they won't be rejected as too old. 🙂

That's how I megaflushed once. 😉

Edit: Here's the NT batch script I used to use:

Edit2: I should probably mention that you need to run several copies of this script in parallel, one copy for each block being received. E.G.:
cacheblocks.bat blk12345678.sob 10 1800
cacheblocks.bat blk87654321.sob 10 2400
 
Giving this thread a bump because I only noticed the upgrade last night, and I'm sure there are a few crunchers who haven't seen it yet.

I got a decent boost from around 410k to 720k cEMs/s. Sure makes me feel like my Athlon's CPU time is worth a little more now 😛
 
Bump to alert you to a possible bug. Please see the first post for more.
 
i just stumbled upon that thread over on the free-dc forums. great research ken! *bump* to inform those who are interested.

so this issue is only if you stop and restart the client? what about if you mow straight through the data and upload without restarting it?
 
From Joh14vers6 in that thread:
No problem with the client for P4.

[snip]

Optimization for non-SSE2 procs seems to be broken!!!
Click to expand...

Yes, Unforgiven, it seems to me that running straight through should work, but I haven't tried it on larger WUs (e.g. ones that have intermediate blocks) yet.

Edit: I tried the first prime Seventeen or Bust ever found, and it worked straight through. So if you don't stop the client (or if you're running with SSE2), the result is probably good.
 
Oh man, I probably stop about 30 times per test.

From Alien88:
Thanks for finding this.. Louie has been informed and is working on a fix. At that point what we will probably do is put all the v2.2 tests back into the queue to be retested and then those that dont have a matching residue will be retested again.

This is something that wasn't tested, and I honestly didn't even think about testing so I doubt Louie did. But.. it'll all be sorted out soon.
Click to expand...

Well done on catching the bug, Ken!
 
I've run some tests, and the new Windows client has my seal of approval. 🙂

Still waiting for word about Linux.
 
Originally posted by: Ken_g6
I'm not entirely sure the bug is fixed. There seem to be some issues with Linux in the upgrade thread.😕 For now I'm waiting to see what happens.
Click to expand...

Oh crap. I also have a P2-400 in Linux running the client and I thought it was safe. It's only done 5% but that takes an age at 100k cEMs/s 😛

 
Good news. :thumbsup: Louie tells me that the bug in non-Windows systems only happens when you restart from 0% with a zXXXXXXXX file. A fixed version should be released soon, but the good news is you probaly don't have to delete your zXXXXXXXX files unless you restarted at 0% *twice*! 🙂
 
Looks like we'll be number 2 in all 3 stats catagories for the New Year :thumbsup: We're #3 in last day production right now but we'll be above the dutch and in #2 by tomorrow 😉 Text
 
Hi, i just joined SB two days ago and am using 2.3 and it seems to be fine! Hopefully I can contribute something to the team!

And by the way, HAPPY NEW YEAR!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top