None of the variables from other miners are directly portable to cgminer. Presumably what you want is the dynamic mode OFF which happens whenever you set an intensity with -I (number).

I'd say the cryptopp_asm32 on windows is likely broken.

Agreed, it seems to be fine from the pool side but the reporting is way off.

ckolivas, any idea what needs to be done to fix this? I'm happy to take a look and submit a pull request if I can fix the problem.

Sorry for being a PITA, but the ncurses bug is still there. The memleak seems to be gone in 1.6.1 though, it's been an hour already and the process is at 370M. Let's see if it leaks overnight or not. Also, it still doesn't build with older curl (at least make it fail at configure stage :-( ):


Thanks!

Ok, configure scripts are witchcraft to me.

I'm having trouble finding any interest in supporting older distributions and libraries in light of that knowledge limitation of mine. If you have patches, I'd be more than happy to accept them 

A typical mining rig isn't your production-class server running old stable userland. I don't see any point putting developer time in working on older curl compatibility. It probably won't be used by many, if anyone at all.

just my 2c.

Given the single purpose of the mining rig, the smaller, the more stripped, the more stable, the better.. that does not match, sadly, the goals of most new distros. I've been running on Fedora14/15 and am actually trying to move backwards to Centos5 for the greater stability... currently being stopped short compiling 1.6.1 with:


which sounds a lot like problems with older curl to me..
.

New version: 1.6.2

Executive summary:
New --failover-only feature for those who complain too much work goes to the backup pool even without the primary pool failing. NOTE that you may get more idle periods with this enabled (which is why it leaked work to the backup pool in the first place).
New scheduling features to specify a start and stop time.
Various fixes and more verbose pebkac warnings.


Full changelog:

- Add --failover-only option to not leak work to backup pools when the primary
pool is lagging.
- Change recommendation to intensity 9 for dedicated miners.
- Fix the bouncing short term value by allowing it to change dynamically when
the latest value is very different from the rolling value, but damp the change
when it gets close.
- Use the curses_lock to protect the curses_active variable and test it under
lock.
- Go back to requesting work 2/3 of the way through the current scantime with
CPU mining as reports of mining threads running out of work have occurred with
only 5 seconds to retrieve work.
- Add start and stop time scheduling for regular time of day running or once off
start/stop options.
- Print summary on quit modes.
- Put some sanity checks on the times that can be input.
- Give a verbose message when no active pools are found and pause before
exiting.
- Add verbose message when a GPU fails to initialise, and disable the correct
GPU.
- Cryptopp asm32 was not correctly updated to the incremental nonce code so the
hash counter was bogus.
- Get rid of poorly executed curl check.
- If curl does not have sockopts, do not try to compile the
json_rpc_call_sockopt_cb function, making it possible to build against older
curl libraries.
- Most people expectusr/local when an unspecified prefix is used so change to
that.
- Rename localgen occasions to getwork fail occasions since localgen is
unrelated now.


Links in top post.

What GPU does include the PCs, and what driver/SDK version are installed?