Anyone tried these updates with MMQs?

Agath was indeed a customer, and did indeed receive his money.  The TIMING of receiving it is interesting, as it was within days of him starting to pursue legal action.

(Apologies if I'm telling too much, Aga.)  Agath reached out to me when he received it last night.

Any plans to add this in the near future?

On a side note, Phinnaeus, I very much respected your work (and calm) during the Pirate fiasco.  I feel as if that scenario is a bit different than this.

Frankly, is raises a hell of a lot more than that.  I have many, many suspicious about Tom, but my conjecture might be completely off (though I don't think it is).  I don't think his issues are an excuse in the least, and I personally, face-to-face, offered him an out specifically crafted for him, with exactly what he wanted.  He left town instead.

PERSONALLY, I don't think Tom started this venture with the intent of stealing money.  However, the end result is the same: Lots of people are owed money, and Tom is missing in action, with zero accountability.  What is most troubling is there were several of us who attempted to him help to varying degrees, and all he ever did was avoid and deny the need.

Tom has lied to me several times on several things, ranging from white lies, omissions, fabrications, to downright boldface lies.  I would say there are more untruths to the situation than hard facts.

I'd like to reiterate that I find the "doxing" of his family worthless and detestable.  That information will not help those who are owed, and only brings you down to that level.  I found Tom in about 4 hours on the ground.  Pictures of his baby won't help you do that.

It really pains me to write all this.  From a business perspective, I should walk away and keep my mouth shut, but I'm really struggling.  Those of you who are owed BTC have been wronged, and it's childish for Tom to run and hide from it.  On the flip side, Tom desperately needs help in his personal life, and I sincerely hope he pursues it.  All of these things are bad for the community and bad for Bitcoin, and that greater effort is what this is supposed to be about.

Maybe a scammer tag will help drive Tom back to the fold so he can share, honestly and completely, what happened and how we can all move forward.  Frankly, I doubt it.  He is not behaving rationally at this point, maybe hasn't in months.

I STRONGLY urged Dave to leave BTCFPGA after my meeting with Tom.  I thought he had nothing to gain, and a ton to lose through "guilt by association."

Dave insisted on trying to complete all the CC refunds, so people would get money back.  He did not, and never did, have access to the BTC.  He and I both attempted to have Tom transfer BTC to Dave so he could handle refunds, but that never happened.

Dave tried his very best, beyond what I would have done (and certainly beyond what anyone else in this forum would have done).  To insinuate he was a part of Tom's behavior is ridiculous and unfounded.

I am extremely interested.

Will email you my current setup.

Call your credit card company and "dispute" the charge.  They should walk you through the process.

Frankly, I don't think the business is lost if Tom comes to terms with the state of his affairs.

I also SINCERELY hope he comes through this okay.

Good to know.  Thanks.

Where in the LA area?

Damn!  I didn't know he would escrow.

I will, but it's the same issue as before.  The process continues to report on the miner, but the miner apparently stops.  Hashing drops to zero over 3 or so minutes.

Awesome!  Hope you enjoy it!  (Or at least get more from a resale     )

I spoke too soon... it died.  Ugh... what a bad night.

Will rewrite the shell script tonight to try to use the new command line args.

Looking good so far on 1.60 on MMQs.  It's been running stably for 3 hours now on 2 miners.

I'm going to guess this was the change that did it:


I'll let everyone know more tomorrow morning if it stays up all night.

Actually, I'd leave it up to the user.  Frankly, I need both.  A time to first check samples, and the the frequency of checking rates thereafter.

I'd like to make a suggestion: please add something to the effect of minimum_accept_timeframe, so that we can change the frequency that the accept rate is checked.  If I could force TML to check every minute (instead of every 10) that my rate is above 700, I think TML would be superior to BFG.

However, from my tests, the 10 minutes max that a miner may sit idle forces the average hashrate below that of other software.

In short, I would love to be able to have the miner decide to reset itself every minute if hashrate drops below 700.

Actually, I think I might have forgot the 2001 copy of Madden.  (LOL!)    Let me know if you want it shipped as well.... for your PS2, of course....