Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 529. (Read 4382714 times)

have auto-payout thresholds stopped working tonight? 

i've been above mine for hours, no payouts

$9.48 is a pretty good price. If that is for one and includes shipping it's a pretty good
deal as far as it goes. It won't generate much BTC at current difficulties and may well
not pay for it self any time soon, if ever. If you check Ebay, the going price is about
$15 or so with shipping. Some folks try and get $30, and will be waiting a long time for
a buyer.

Ooops, I meant $9.48

948$ is way overpriced, considering that it utilizes obsolete technology (110nm).

So is an old skool block erupter worth $948 plus shipping now, or is that still too pricey?

There's been typically a ten fold hash rate increase every 3 months recently. Best to work with that.

just to share some news: my KNC box just found Block #263890 ... cool stuff ... always good to contribute!

It happens with the best of us

This will be yet again an all time high difficulty increase. We are experiencing quite interesting times I believe.

I guess the next all time high change will be when Cointerra gear (hopefully) hits the market...It takes approximately 1227pcs 2TH units to provide the current network hasrate. I think they have a lot more preorders than that.

I'm afraid I've underestimated it this time... :-(
Hashrate has been quite stable for the first several days of the cycle, then it has turned upwards quite quickly.

Yep, my connection has been solid for so long now, I missed the obvious.

Looks like you may have lost the connection or something. Mine are ok. Assuming you X'd out total shares?

Anybody else have this today?

20399    2013-10-14 15:15:05    2:08:56    xxxxxxxx     none             none    263619    25.17135824    51 confirmations left
20398    2013-10-14 13:06:09    4:13:30    xxxxxxxx    28278    0.00000000    263599    25.14919247    31 confirmations left

And updates breaking things the way they worked before, like GPU being disabled by default. My problem with that ended up being Windows' limitation on parameters on shortcuts. Worked it out though. Thanks to everyone who helped.

It's amazing how many different ways there are to work with BFGminer(and CG).
The occasional share-out of information, like this, does trigger new ideas.
Also the different combinations of devices bring their own quirks to the discussion.

Whatever.  I wasn't making a suggestion to your situation directly.  I was merely stating my personal experience to Mudbankkeith.

Stating a com port might help if other ASIC devices are present on the same machine like block erupters. I'll look into that - Thanks a bunch.

I updated BFGMiner 2 latest version and it turns off GPU when ASIC is present. Shortcut parameters got too long to define GPU and ASIC all at the same time - hence 2 instances. Working good now.

I'm also now managing my blades with BFGMiner. 3 blades per rig on the same user. Seems like my variance has gotten bigger because difficulty increased drastically on that one user.

I didn't mean it literally - I like slush, but it's getting bigger.Of course, great help.

That's cumbersome in my application. My miners are at work and if anything happens or something crashes/power failures I would have to go back to work to perform the startup procedure - Nope!

But I use similar method. I use predefined shortcuts sitting on desktop and have a batch file launching these shortcuts. This batch file is in startup folder so in case of a power failure, computer turns back on automatically, windows logs in automatically and a startup script with time-delay runs. My script delays for devices and the operating system to finish loading - for example, if I run BFMiner too fast not all of my block erupters show up because I guess they are not ready to start working yet.

To prevent power issues, my block erupter USB hubs are on a UPS so they never power off in power failures. When power restores, my rigs auto start and all goes well. I don't have to drive to work ever - unless in rare case if I get BSOD on the rigs.

In case of BFL running computer, I have BFL and 2 GPUs - I am now running 2 instances with 2 separate copies, one controls BFL and the other controls GPUs. In my startup script I run GPU BFGMiner first because in my experience ASICs need a bit of time to get recognized on USB ports.

It's working well.

Hi mdopro1

Lots of Ideas here!
Does it help to in debugging your problem?

I don't use .bat files either.  I just use a shortcut with specific parameters for each instance; and yes, they're conveniently placed on the desktop.  In my case, I run the BE array first with its specific shortcut while the BFL device is turned off.  When the BE array is running and has settled, I then turn on the BFL device and run its specific shortcut.  Though the BFL device would run with the BE array in one instance using the BE-specific shortcut (-S all), BFGMiner would identify its chips as BE devices and would label it as such (ICA##).

If you run from *.bat files, then place the shortcuts on the desktop, then it should work ok.
To be on the safe side, for the bfl device, specify the com port number in the second *.bat file. That way you know its not even looking at anything else.