Quote from: gourmet on October 14, 2013, 07:02:26 AM

Quote from: mdopro1 on October 13, 2013, 05:42:53 AM

Yup! Feels like I need to find a smaller pool. My reward is shrinking by each round.

You have to take into accout the round frequency also.
Smaller pool will change nothing for you. You will have higher rewards, but less frequently.

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

Quote from: Mudbankkeith on October 14, 2013, 10:58:01 AM

Hi mdopro1

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

Of course, great help.

Quote from: visdude on October 14, 2013, 10:49:56 AM

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##).

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.