Thought I would get things working with a single HD 7950 2gb. Have two R9 270X 4gb on the way.
When adding :

"GPU_FORCE_64BIT_PTR 0
GPU_MAX_HEAP_SIZE 100
GPU_USE_SYNC_OBJECTS 1
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100"

The miner loads but says none of the cl commands are recognized.
Then the dag file buffer cannot be created and dag file runs out of space.

I've searched and searched. it seems to be connected to a memory limit on the card. One that would be corrected by the commands above.
bTW AMD drivers are 15.12

At this point I'm out of ideas.
Thanks for nay help or opinions.

Claymore pls, can you make other dual miners aswell?
For example etherium + feathercoin(NeoScrypt) or Qubit,nicehash etc.. so it is possible ?

Thanks for your work  

Ethereum + feathercoin might not be a good idea. Both algorithms use a lot of memory access. qubit might be OK.

I'll never complain about adding new features but is there a reason for wanting to control GPU speeds and fans through the mining program compared to just using MSI Afterburner?

I see it now. Thank you.

These don't need to be in your bat file every time you start the miner.  They only need to be run once.  Whenever I have to reinstall windows I just run them in a separate .bat by themselsves.

You can check if they stick by right clicking on the start icon-->System-->Advanced system settings-->Environment Variables

Also, I've always used GPU_FORCE_64BIT_PTR 1, so probably doesn't matter for this miner.

Mr. Claymore
Miner suddenly stops after 2-3 hours. I send log to PM. Please check it.

I can'n make it stable.

Win 10,
cat 15.12
4*390 + 2*280x
8Gb RAM
8Gb VirtMem
DualMiner v2.0

Looks like a pool hangs on some block. If the problem is in miner, pool must reject old shares, but it responds "accepted", so the problem is on pool's side. Anyway, PM me the log file, I will check it. I will also add check so if miner gets same job for a long time it disconnects from the pool because it hangs.

after restart miner everything is normal

You can check the log, pool sends the same header (job) for a long time:

23:01:14:327   16cc   got 243 bytes
23:01:14:338   16cc   buf: {"id":0,"jsonrpc":"2.0","result":["0x56c1b889948349b145171845df85cbaae42e2052393518da6e68fe4c652a27f3","0x013d5197a3a035144a79e3e09dfec2505039ed176d81a0957e229886ddbee49b","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

......

23:43:57:438   16cc   got 243 bytes
23:43:57:451   16cc   buf: {"id":0,"jsonrpc":"2.0","result":["0x56c1b889948349b145171845df85cbaae42e2052393518da6e68fe4c652a27f3","0x013d5197a3a035144a79e3e09dfec2505039ed176d81a0957e229886ddbee49b","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}
 
42 minutes it sends the same job. Moreover, it accepts shares for this job all the time:

23:09:02:904   16cc   got 36 bytes
23:09:02:912   16cc   buf: {"id":4,"jsonrpc":"","result":true}
23:09:02:922   16cc   parse packet: 36
23:09:02:940   16cc   ETH: Share accepted!

.....

23:40:44:596   16cc   send: {"id":4,"method":"eth_submitWork","params":["0x75e8cb19ab613cb4","0x56c1b889948349b145171845df85cbaae42e2052393518da6e68fe4c652a27f3","0xfc152e9f3155f53c75a270b7db26d6b63fec19c54318a49ec1513246cf14479e"]}
23:40:44:725   16cc   got 36 bytes
23:40:44:728   16cc   buf: {"id":4,"jsonrpc":"","result":true}
23:40:44:728   16cc   parse packet: 36
23:40:44:737   16cc   ETH: Share accepted!

The problem is not in my miner. The only problem with my miner is that it should understand that entire pool (or at least its thread that serves you) hangs and disconnect, I will add it.