Icon
Yup, that's what I did. But the address in SGMiner was the 17FP4wt......one. Not mine. I'll replace mine in the CONF file..see what happens.
Got it to go, replaced my the BTC address in the CONF file with my own...all working good. Its currently on the x13 algo.....hashrate is 3.8Mh/s....that seems low for a 290, no?
in all cases - no matter what the miner is 'supposed' to do - ALWAYS change the addresses ... ALWAYS ...
the way i work with any miner is simple ...
scrap all the config files - and build your own ... even if it means an extra 1 hour to setup ...
your hashrate is very important to you - so unless you are hashing to donate to the dev - change everything ... if you do want to donate - please have a look at this thread - https://bitcointalksearch.org/topic/a-chainworks-industries-cwi-project-donate-by-mining-dbm-1089744 ... its just one of the ways to hashback to the dev ...
glad you found the issue ... happy mining ...
#crysx
Thanks man, much appreciated. For building my config files, should I use my old ones for CGMiner back when I was mining Scrypt, or will it be all new ones?