Quote from: bumblebee33 on February 17, 2014, 05:14:17 PM

Quote from: Hueristic on February 17, 2014, 01:22:05 PM

Quote from: bumblebee33 on February 15, 2014, 09:48:03 PM

I want to share some other discovery I made today:

In the last few days I was playing around with several other settings like --queue --expiry and --scan-time. And the more time passed, the less blocks my miners picked up. I tried all kinds of things to get it working again like resetting router, restarting rigs, ... I was about to give up when it occurred to me that the part of these settings might still have been stored and corrupted my mining settings. Then I remembered something you do when testing out new settings, to delete the "scrypt130511Tahitiglg2tc8192w256l4.bin" file in the cgminer folder.

No more than 10 minutes passed after deleting this file and my miners found already the first block again.

To make a long story short - if you play around with several settings and experience bad luck, try deleting this file - as this will reset and rebuild your proper mining settings.

Also, another tip:

If you add at least 2 --fallover-only -o stratum+tcp://pool.com:xxxx -u user -p password backup pools to your .bat file, you will increase your chances of finding a block while solo mining, as you will use the stratum's servers data to update your miner when a block gets found, so you are always working on the latest block. (And thus avoiding orphaned blocks.)

For anyone doing this just a FYI there is no setting fallover-only, it is failover-only. Also deleting your bin will not change anything to do with the block you are working on it is nothing more than the method the miner uses to hash on your hardware with your settings, compiled.

If your card is acting weird though you can always delete the bin file and cgminer will re-compile it on the next start.

Wasted another 10 hours with nothing last night. Thats 40 hours total with nothing at 1Mh/s I feel like I've been.

http://www.youtube.com/watch?v=oHg5SJYRHA0

Cheesy

Yes, it was a spelling mistake, --failover-only - good that you spotted it.

I stated why I deleted the .bin file, because I was playing around with miner settings, not to delete anything related to the block itself.

You can check your chances of solving a block at the current difficulty with the mining calculator:

http://www.coinwarz.com/calculators/earthcoin-mining-calculator

By the way for your speed you should have solved it in 0.93 days - so less than a day. But sadly a great deal of luck is involved in it as well.

Another 5 1/2 hours with nothing. Sad

Still can't get other 450kh/s system to connect. I'm assuming If I run the wallet on the other system it will work on a different block?