Author

Topic: Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux) - page 367. (Read 3839163 times)

legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
v9.1:

- additional range checks in code for better stability.
- reduced devfee, it's 2% now (72sec instead of 90sec) if you use secure SSL/TLS connection, currently Flypool and Suprnova pools support encrypted connections, see Readme for samples.
- improved "-di detect" option: now after GPU order detection miner starts mining with the detected order.
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

Since encryption is added I think its safe to release Linux version with ONLY ssl support, don't you agree?

No this isn't the reason why he doesn't want to release linux. Its because in Linux you can easily disassemble the program.

yeps +100% . i think it was linux version that "showed" the SA code inside CM's miner.

now with ssl at flypool & suprnova, well there's good & bad, good for miners, you are "secured" & it is also "secured" for CM

"secured" means, your connection is a little more secured & it also means CM's "reduced fee" is VERY much or more secured, making it more difficult to be bypassed.

v9 compared to v8, v8 way more stable, v9 so so ... let's see future improvements ... upgrade.

some rigs have 0 issues v9 smooth like butter but on some other rigs, is having issues like everyone else.
member
Activity: 108
Merit: 11
CPU: i5 4570 (was collecting dust on my shelf)
MB: ASRock H81 Pro BTC R2.0
RAM: 8GB G.Skill Ripjaws X series DDR3 1600 Mhz
PSU: EVGA 1200 G2 & EVGA 1600 G2 (Again, collecting dust on my shelf)
HDD: 128GB SSD with 20GB virtual memory
OS: Windows 10 Pro
GPU: 6x Sapphire R9 Fury Nitro - bone stock (free power)
Radeon Software Version: 16.12.1 (ReLive software not installed)

Total Speed: 2,000 H/s
Currently running Claymore v9.0 since minutes after release.  Rock solid, no reboots, no freezes, etc.
Just installed 16.12.1, will update if there are any impacts to stability.
legendary
Activity: 1084
Merit: 1003
≡v≡
everyone is evil , everyone wants to dissasemble his miner.
I won't mind to add my own fee (which I get every week from my employer) on top of Claymore's so I can get my coins on time, does this counts evil ?
hero member
Activity: 2548
Merit: 626
everyone is evil , everyone wants to dissasemble his miner.
legendary
Activity: 1084
Merit: 1003
≡v≡
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
Yeah, make a shortcut on desktop to the ZecMiner exe on the network.  The only downside is logfiles.  Also, you would need to restart miner on all rigs. If they autostart, you could just powercycle them.  Even if you just remoted them all, it would be faster, since it would be less work to do on each rig (close and restart).  May be issue replacing version when rigs were using, not sure if it affects network though.

You could also make a bat file to copy from a specific network folder to desktop folder, then start miner, and use environment variables in config of course.

Edit:
Instead of power cycling, you can tell each rig to run "reboot.bat" (you need to create it, such as "shutdown -r -t 00"), so you would just need to run that on all rigs monitored by Ethman.

I need to do a research about it, I need to reduce miner updating time, even config updating time.

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
3 Hours .... , 2 min per rig . WOW 90 Rigs , nice man
I have only 15 Rigs 6x390 , and update to new version takes 20 min.
94 actually and I do it remotely so I have to wait until it starts mining and etc. it's a routine job and it sucks

94 rigs?? Holy hell dude I'm here just trying to keep 1 running lol
I'm just maintaining them that's it. It takes so much time and effort that I came with two new awesome ideas to replace hdmi dummies with much cheaper ones like 10Cents per rig and remote reset solution, both are under development and if everything will work fine I'll share it here for sure
sr. member
Activity: 449
Merit: 251
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
Yeah, make a shortcut on desktop to the ZecMiner exe on the network.  The only downside is logfiles.  Also, you would need to restart miner on all rigs. If they autostart, you could just powercycle them.  Even if you just remoted them all, it would be faster, since it would be less work to do on each rig (close and restart).  May be issue replacing version when rigs were using, not sure if it affects network though.

You could also make a bat file to copy from a specific network folder to desktop folder, then start miner, and use environment variables in config of course.

Edit:
Instead of power cycling, you can tell each rig to run "reboot.bat" (you need to create it, such as "shutdown -r -t 00"), so you would just need to run that on all rigs monitored by Ethman.

I need to do a research about it, I need to reduce miner updating time, even config updating time.

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
3 Hours .... , 2 min per rig . WOW 90 Rigs , nice man
I have only 15 Rigs 6x390 , and update to new version takes 20 min.
94 actually and I do it remotely so I have to wait until it starts mining and etc. it's a routine job and it sucks

One more thing, Windows has the open confirmation for new unknown files, and default block in Win10 (helps prevent spread of viruses), I think this can be avoided if using .bat file to start miner.
member
Activity: 60
Merit: 10
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
Yeah, make a shortcut on desktop to the ZecMiner exe on the network.  The only downside is logfiles.  Also, you would need to restart miner on all rigs. If they autostart, you could just powercycle them.  Even if you just remoted them all, it would be faster, since it would be less work to do on each rig (close and restart).  May be issue replacing version when rigs were using, not sure if it affects network though.

You could also make a bat file to copy from a specific network folder to desktop folder, then start miner, and use environment variables in config of course.

Edit:
Instead of power cycling, you can tell each rig to run "reboot.bat" (you need to create it, such as "shutdown -r -t 00"), so you would just need to run that on all rigs monitored by Ethman.

I need to do a research about it, I need to reduce miner updating time, even config updating time.

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
3 Hours .... , 2 min per rig . WOW 90 Rigs , nice man
I have only 15 Rigs 6x390 , and update to new version takes 20 min.
94 actually and I do it remotely so I have to wait until it starts mining and etc. it's a routine job and it sucks

94 rigs?? Holy hell dude I'm here just trying to keep 1 running lol
legendary
Activity: 1084
Merit: 1003
≡v≡
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
Yeah, make a shortcut on desktop to the ZecMiner exe on the network.  The only downside is logfiles.  Also, you would need to restart miner on all rigs. If they autostart, you could just powercycle them.  Even if you just remoted them all, it would be faster, since it would be less work to do on each rig (close and restart).  May be issue replacing version when rigs were using, not sure if it affects network though.

You could also make a bat file to copy from a specific network folder to desktop folder, then start miner, and use environment variables in config of course.

Edit:
Instead of power cycling, you can tell each rig to run "reboot.bat" (you need to create it, such as "shutdown -r -t 00"), so you would just need to run that on all rigs monitored by Ethman.

I need to do a research about it, I need to reduce miner updating time, even config updating time.

- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
3 Hours .... , 2 min per rig . WOW 90 Rigs , nice man
I have only 15 Rigs 6x390 , and update to new version takes 20 min.
94 actually and I do it remotely so I have to wait until it starts mining and etc. it's a routine job and it sucks
newbie
Activity: 10
Merit: 0
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
3 Hours .... , 2 min per rig . WOW 90 Rigs , nice man
I have only 15 Rigs 6x390 , and update to new version takes 20 min.
sr. member
Activity: 449
Merit: 251
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
Yeah, make a shortcut on desktop to the ZecMiner exe on the network.  The only downside is logfiles.  Also, you would need to restart miner on all rigs. If they autostart, you could just powercycle them.  Even if you just remoted them all, it would be faster, since it would be less work to do on each rig (close and restart).  May be issue replacing version when rigs were using, not sure if it affects network though.

You could also make a bat file to copy from a specific network folder to desktop folder, then start miner, and use environment variables in config of course.

Edit:
Instead of power cycling, you can use ethman to tell each rig to run "reboot.bat" (you need to create it, such as "shutdown -r -t 00"), so you would just need to run that on all rigs monitored by Ethman.
legendary
Activity: 1084
Merit: 1003
≡v≡
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
It takes me 3+ hrs to update all my rigs to new version when Claymore announces it, so with this I can do it all at once ?
full member
Activity: 188
Merit: 100
Ethereum4ever
Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here..  Cry
v9 and v9.1 runs perfectly for me since release. and i overclock my rx 480 with afterburner.
2 cards running in Win7 and 4 cards in Win10.
+1
all works perfectly on 6 rx 380
sr. member
Activity: 305
Merit: 250
sr. member
Activity: 449
Merit: 251
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
You can set environment variables in Windows, then use in config.  So you can have identical config for all your rigs, since they could pull worker name from environment.  You can also do this through ethman when uploading configs to rigs.  You could also run all rigs off same network share, making it really easy to update all rigs, and change config, since each would still have it's own worker.  Downside of this is logs would all be in same folder so would be useless for troubleshooting.
newbie
Activity: 29
Merit: 0
Anyone try new AMD driver RELIVE ? work ? more performance or minor consuption ? .
AMD RE? No way

Installed it on my test rig, REgot that code error43 again, that thing of the past RElives again. RErun AMD clenup utility, that 500MB package still lives in my drive. DIdn't bother DDU, REformat, dd *.img
legendary
Activity: 1084
Merit: 1003
≡v≡
- added ability to use environment variables in "epools.txt" and "config.txt" files. For example, define "WORKER" environment varibale and use it as "%WORKER%" in config.txt.

anyone ?
what is the use of this ?
legendary
Activity: 924
Merit: 1000
Dark Passenger Bitcoin miner 2013,Bitcoin node
Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here..  Cry
v9 and v9.1 runs perfectly for me since release. and i overclock my rx 480 with afterburner.
2 cards running in Win7 and 4 cards in Win10.
+1
newbie
Activity: 50
Merit: 0
Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here..  Cry
v9 and v9.1 runs perfectly for me since release. and i overclock my rx 480 with afterburner.
2 cards running in Win7 and 4 cards in Win10.
full member
Activity: 160
Merit: 100
Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.

Same problem here..  Cry
YIz
hero member
Activity: 686
Merit: 502
Serious stability issues with my rigs using 9.0 and 9.1. works for a few minutes and then the system restarts.
Jump to: