WTS 1,286 Catcoins.

PST me with your offer.

Lowballs not welcome.

Taking Doge, LTC, or BTC.

Good job fellers 

That's a terrible config for 2 reasons:

1) --shaders gets overwritten when --thread-concurrency is specified
2) no --gpu-thread (-g) flag specified.

try this:

10 bucks says the OP got his UTC:PST/CST conversion wrong  

http://doge.netcodepool.org/

Registrations open once again.

Help us hit 3ghs+ !

Remember, use port 4094.

Another quick note to our Doge NetcodePool miners:

The front-end is being worked on.  

The back-end which has the pool is working just fine.  

Always remember that our front-end is completely abstracted from the back-end which contains our pool, so just because the front-end may not be available does not indicate at all the status of the seperate back-end pool part.

Keep those miners pointed to us!  Your work is being recorded as normal and you will get paid out as usual.

Just a heads up for any of our Netcodepool DOGE Miners who may be having issues logging into their account:

http://forum.netcodepool.org/forum/showthread.php?tid=736

Just to remind people:

Doge.Netcodepool.org:4094

If your miners were/are having troubles connecting to the pool, update your port to 4094!

REGARDING DOGE.NETCODEPOOL.ORG:

Our pool and its operations are completely encapsulated in their own back-end area and are completely abstracted from the front-end.

In other words, the frontend may be down (stats, etc) but the backend pool is up.

Your shares, payout information, and work done are all safe and sound.

We are up as of 12:38pm.


EDIT: Our connection info: 

Let the operator(s) present their cases before slamming judgement upon them.

K?

Remove the --shaders option.  It will overwrite the --thread-concurrency flag.  

You are also missing the --gpu-threads flag.  Add -g 1.

Also, if you want 170khs+, you will need to make the --thread-concurrency 6xxx to 8xxx range AND you will need to raise the intensity to 17+.

Your flag line should look something like this: --thread-concurrency 8100 --intensity 18 --worksize 256 -g 1


Note that raising the intensity that high will render your windows desktop unusable.

MC has turned me into a very lazy miner.  

About queue, expiry, scantime: Keep them default.  I don't touch them and i have 0 issues with connectivity.

About worksize: Keep this @ 256.  It has nothing to do with the pool difficulty, but rather GPU work unit.  HD 7xxxx series cards appear optimized for -w 256.

About gpu threads: 7950s love gpu thread @ 1, with a high(er) Thread Concurrency number.   7950s appear optimized to run with 1 gpu thread and a high concurrency.  Ensure that your thread_concurrency number is a multiple of 2 (2^n). 

About vector: Unused, good for delete as you already have.


Your primary GPU related settings are: intensity, thread_concurrency, worksize, and gpu_threads.  When you're using the config file format, tune those and leave everything else at default (unless a pressing need presents itself.)

I would also recommend setting your GPU fan to a constant 80-90%.

Naw, .0092/.0077 return is not the norm.  When i see a day like that, it's almost always because coins are maturing etc.

You should be doing .02-.05/.06 as a range.  

I run ~4.1-4.2mhs with 5 7950s / 1 7970 / 1 5850 and i make (with BTC at current prices and .10 kwh) almost $300 profit a month after electricity.

Just make sure you are undervolting your 7950s and keeping them relatively stockish.

Past stock clocks / undervolt @ .975/.1 you are paying roughly 1 watt / khs.  

Very good.   

H20, do you have LTC in the coin rotation?

Houston we have a problem/  

http://i44.tinypic.com/300czte.jpg

mySQL errors..looks like its attempting to log into a WDC pool that mighta been taken offline due to the recent fork.

I definitely think BTC will head back down (not crash).. eventually.

Scrypt and its alts are here to stay.

You may need to switch to CGMiner, i don't think it supports BFGminer.

Use CGWatcher to monitor your miner(s).