I can't believe what people post on here ,
In Dire Need Of Assistance 
Because software that other people wrote and likely spent hundreds of hours on that you use for FREE does not do EXACTLY what you want when you want it, how you want it , by remote control, and dance around the room too
It is an open source project dude.
SO ,
You have a few choices if you feel this is a priority to resolve and want to go about it 'properly'
1) Code a fix, test it, do a git pull and if everyone likes it , maybe your work will get merged. (at least your build will work)
The benefit of putting your fix on github is others can benefit from this 'awful problem' you have found in the mining software.........
2) Post a bounty for someone to do this for you if you cannot code or don't want to take the time to bother. (Again hopefully the 'fix' since this is priority number one) can get released so the entire rest of the world will benefit from it.
There is more of a sense of 'entitlement' in these forums now than years ago before I refused to even god dam join.
If you are fortunate enough to own a mining rig,
MINE WITH IT[/size
Watch TV or play games on something else.
I'm sorry to scold you personally and single you out.
This is directed at all the cry babys and children on this and other threads who need to be put back into perspective.
You people and the devs who run the x11, x13 , x15 coins should be verrrrrrrrrrrrrrrrrrrrrrrrrrrrrrryyyyyyy greatful for the work Wolf and others have done or miners would be mining at a fraction of the hash rate they are now and the people buying all the hash power to secure their blockchains from attack (since not enough people believe in their projects to mine the coins just for the coins) would be paying a lot more btc per hash..............
Think about that for a while.....
I'm in dire need of assistance with an issue which has been plaguing me ever since SGminer was introduced despite the fact that I've invested more time troubleshooting than I care to mention. The rig in question is composed of 2 r290x & 1 r290 and my problem is encountered trying to disable the second GPU from startup w/ the following command-line: -d 0,2 via .bat or "devices" : "0,2" via .config file. This results in GPU2 being absent from the miner although it seems to be mining given the hefty load on GPU observed by Afterburner and GPU1 starting in a disabled state while GPU0 is active for some very odd reason. The purpose of all this is so that I can game or watch movies on GPU1 while GPU0&2 are mining. I'm well aware that I can simply disable GPU1 manually after the miner is launched but every time the kernel switches, so do my clocks which subsequently crashes my rig. The sole solution which comes to mind is by putting my desired clocks for all algorithms for that particular GPU in my config file but I would prefer having it disabled all together.
I really hope someone can get to the bottom of this one in which case I would like to offer my thanks in advance!
The horse you're riding on must be so high your head is way up in the clouds given how far you've deviated off topic. The effort you've invested trying to ridicule me instead of offering your advice is very impressive. I've refrained from posting about this issue for years with good reason given your absolutely useless response.
I'm certain a respectable number of users will gradually stumble upon my post as well as damm315er's since they've unfortunately encountered the same issue and deem it conclusive instead of creating yet another thread. Reporting a bug is the first step in getting it resolved although this particular issue has been already acknowledged, additional complaints can only aid in its resolution.
I almost forgot to thank you for your useful advice. Please be so kind as to give me your BTC address so I can send some coins your way.
Here's some advice for you buddy and please keep this in mind, say half as much you'll sound twice as smart.
Think about that for a while.....Last but not least, get laid and let us all know what the weather's like up there.
@MaxDZ8, glad to know we're on the same page.
@Wolf0, Wo000ooooo00000 Woooooo0000000ooooooo
