Topic: AOCLBF 1.8.4 by WinD - Dynamic clocks adjusting Completely AUTOfanspeed - page 2. (Read 39960 times)

Your miner supports 6 video card?

I run mine with serverdoc, hence if AOCLBF dies it gets restarted with a batch of other important processes.(I double my miner as my server too)

  Use the newest beta of AOCLBF. to use a different kernel just copy and overwrite the files in the phak folder with the kernel of your choice. use 2.6 if your using 7xxx card 2.5 if using 6/5xxx...Gui miner is more stable but has less features in my opinion. I think you can solomine the same way u do in phoenix just put in the local address instead of the pool address. but umm anywhoo...
DUDE. it just dawned on me how to fix (temp.) the error. Is it possible to have AOCLBF exit and restart itself every 12 24 36 or 48 hrs like an extra setting that you could choose?  I know this program is prolly dude for an overhaul since phoenix 2 is out but still. I thik that would put an end to this problem so we can move on to other stuff 

Hi everyone. I really like this program. Ever since this poclbm issue recently and the entire SDK2.6 problem, I'm running many of my rigs with the guiminer and diaphatk kernel. This is more an emergency measure though. I haven't been able to get aoclbf to run with diaphatk so far. I do not want to switch to CG miner, since my results with it were dissatisfying.

I'd like to go back using aoclbf so I can have a backup pool option. Furthermore, is there a way to solo mine using aoclbf's backup function?

The reason is following: I mined 7 blocks in 8 months at slush's pool and one block in one month at btcguild yet only got about 250 BTC paid out alltogether. This makes me wonder if it wouldn't be great to have a solo mining option. I will never catch up and who knows with decreasing btc prices, the difficulty might go down again another time.

With diaphatk I got most of my performance back, but the 100%CPU bug is still there. It was kind of nice deciding whether to spare the cpu or go for full performance, but now with the additional pcoblm bug, I got confused. I do not want to spend another few weeks figuring out how to get things back up and running smoothly.

So, quick recap:

Which aoclbf is best to use with SDK2.6 (catalyst 11.2-12.1)?
Should I use the old version of guiminer that is not affected by the recent bug?
Which files do I copy exactly, and where?

Thank you for your help!

Just an update. Tried with the down clock disabled. Tried with the auto restart disabled. Still got the error. Going to try with both disabled.

Its easy to recreate the error.  Just put in wrong pool info  or disconnect the internet from the machine
and let it switch back and forth between main and backup pool... eventually it will crash. 

Also my rig with 4x6870 and 3x 6970 errored today. Im going to try something diff to see if i can help.
On one rig (4x6870) im going to disable the restart option. seeing as how the accepted shares reaches into 10s of thousands and phoenix is still going after the error the restart option isnt as important as it was. and the other rig im going to disable the down clock feature. Maybe one of these are causing the error as they are using resources to actively monitor something. what do you think?

Im ashamed to say that i don't know what ur talking about. walk me thru and ill launch it as a script on my fastest rig to test. or some one else can try.

well thank you
but I wonder where error is. I would like to ask to launch AOCLBF from script itself 'cause compiled one doesn't give me info what line in script causes an error.
FRanz33 can you do that?

beta 2 is much better. just had two array errors today for fist time since release. One Box has 3 6970's 940/825 aggression 11 with 6 gb ram other box has 4 6870's 930/830 aggression 9 6gb ram. Im wondering if maybe a higher than normal aggression causes twohe error to occur more often. Maybe not but whatever your doing makes it more stable. As far as OSD goes i prefer it to be auto off as most my units mine in office areas and are used by other people. Perhaps you can make it a savable option to Auto hide or Auto show. An auto Click thru would to and a more robust option menu when you right click the tray icon. Just throwing out ideas. Thank you for all your hard work!

Power cut makes me restart 10-15 times a day

nohow so far..will be realised as option later
is it really big troble for you? Do you often restart AOCLBF?

How to make OSD visible default?

looks very good so far... fixes lots of problems

if phoenix 2 is more powerful then 1.x one I will think about it..

Phoenix 2 is in beta.  will you support it ?

Its important for me to see OSD, that gives me temperature of the cards.

Stability, i am not using continuously for 24 hours, but at least 12 hours it run with out any error or problem.
12 hours perfect.

may be will do this as option if it is so important
how about stability in new beta?

Is their any way to make OSD on & not minimize AOCLBF?
like command line parameters which can be given to show OSD on.
New versions not showing OSD which makes it useless, unless every time has to click & select OSD on/off

ok, working