Page 1 of 1


PostPosted: Tue Nov 05, 2013 4:30 am
by joe53
I have been using the 6.34 client for some years now, averaging about 18,000 ppd, running 24/7. I found it had stopped getting WUs for a few days, and when I attempted to post this problem to the "V6.34Beta SMP2 with passkey [Not Bigadv]" forum I could not access it. I get the following:
SQL ERROR [ mysql4 ]
Got error 134 from storage engine [1030]"

I reported this to admin, but all they could suggest was that I should register and log in here to get help. I've been registered here for years.

I was able to get 6.34 back up and working with a bit of research on my own, but the experience left me with a few questions:
1) Where do I post questions for support of this client in the future?
2) Should I change to version 7? It seems to me to still be in beta, and I'm not sure what advantages it offers.

Re: Questions

PostPosted: Tue Nov 05, 2013 5:04 am
by Jesse_V
This is indeed a bug with the forum. I'm seeing it too. That's where it should be reported, it just looks like that link has issues. Bruce and/or UncleFungus are the ones who could probably fix it.

V7 is not in beta, you are encouraged to upgrade. Just do a bit of reading on how it works so you're not completely in the dark. You should be able to copy your username, ID, and passkey info and you should continue to get bonus points. Finish the v6 WUs first, then upgrade to V7. Make sure v6 and V7 don't run at the same time, you wouldn't want them competing over computational resources.

Re: Questions

PostPosted: Tue Nov 05, 2013 7:09 am
by 7im
Why does it seem to still be in beta?

Re: Questions

PostPosted: Tue Nov 05, 2013 8:54 am
by joe53
Thank you Jesse a 7im for your replies.

I'm glad to hear that version 7 is out of beta, and I will upgrade. I don't spend a lot of time in this forum, and my info was obviously out-dated.

Re: Questions

PostPosted: Tue Nov 05, 2013 9:12 am
by PantherX
Please note that I have informed the appropriate personal about this issue.

Re: Questions

PostPosted: Tue Nov 05, 2013 9:22 am
by uncle_fungus
I've fixed the SQL error on accessing that particular forum.