Quote from: djkice on May 06, 2018, 08:37:30 AM

Quote from: cde2006 on April 29, 2018, 05:39:04 AM

Please add support for z-enemy miner. Thanks!

https://bitcointalk.org/index.php?topic=3378390.0;all

just rename z-enemy.exe to ccminer.exe and use the ccminer script
works fine

Thank you!

Quote from: christiano88 on May 06, 2018, 12:56:19 AM

Please please please add support for SRBMiner...it is really popular.

Quote from: christiano88 on May 07, 2018, 06:34:12 AM

how about xmrig? Or at least SRBMiner..

Please give me links to it. Thank you!

Quote from: varons666 on May 02, 2018, 02:37:36 PM

Requirements - Windows 10 Pro x64 Creators Update or higher (May not work on others)

Tested and working on Windows 7 Pro X64.

Thank you! Yes script can work on almost all versions of Windows but it can be some undefined errors...

Quote from: az001 on April 26, 2018, 04:01:33 AM

Any chance you could add this miner:
https://github.com/palginpav/hsrminer/tree/master/Neoscrypt%20algo/Windows
?

THANKS

Noted. I need more information how to configure it. Information about errors and problems to fix by my script.

Quote from: dlh1963ua on May 11, 2018, 01:49:22 PM

Quote from: djkice on May 06, 2018, 08:37:30 AM

just rename z-enemy.exe to ccminer.exe and use the ccminer script
works fine

does not work
does not determine the number of cards and with "gpurestart = 1" option restarts

as a solution: "gpus = 1"

ccminer log
[2018-05-10 08:26:45] 2 miner threads started, using 'x16r' algorithm.

z-enemy log
[INFO ] 18/05/11 11:18:34 Mining 'x16r' with 2 threads.

Code:

+===================================================================+
   AutoRun v.1.9.8 for z-enemy_RVN_suprnova Miner - by Acrefawn
   ETH: 0x4a98909270621531dda26de63679c1c6fdcf32ea
   ZEC: t1S8HRoMoyhBhwXq6zY5vHwqhd9MHSiHWKv
   BTC: 1wdJBYkVromPoiYk82JfSGSSVVyFJnenB
+============================================================[53]===+
Process ccminer-x64.exe is running for 00:09:46 [0/5].
Rig [RIG14] using [1/1] GPUs.
+===================================================================+
Total current speed: 33/0 [0/99]
Total average speed: 14/0 [0/5]
Current GPU speed:
- G0 16, G1 17.
Current GPU temp:
- G0 63C, G1 66C.
+===================================================================+
[Disabled] GPU Overclock monitor
[Disabled] Autorestart at 00:00
[Disabled] Autorestart at 12:00
[Enabled] Autorestart miner every 72h
[Disabled] Autorestart computer every hour
[Enabled] Last share timeout check
[Disabled] Telegram notifications
[Disabled] Additional program autorun
+===================================================================+
Now I will take care of your miner and you can relax...

Noted, need to test it. Thank you very much!
Upd script recognize cards amount by counting "Intensity" words. Tested on latest version and it is working fine for me.

Quote from: jdash on May 14, 2018, 11:50:07 PM

i have question.

i cant run the program, getting parse error dtsm_miner.bat saying something like parse "error on temp-target 80"

dtsm miner wont run using its default "--temp-target 80" in config_dtsm.ini

i had to remove it to run the program, anyone knows how to correct it? thanks

Quote from: 370Z-EHCR on May 15, 2018, 05:07:39 PM

Hi,

After removing "--temp-target 80" in the .ini file, you must also remove this string in the Dstm_miner.bat file too. Else the miner will simply refuse to work.

Other than that, this has been a great script to use and work with. Thank you Acrefawn!

Fixed. Thx for reporting!

Quote from: 370Z-EHCR on May 16, 2018, 03:43:23 AM

Dear Acrefawn,

I got more issues to flag unfortunately.

I am using FarmWatchBot v2.0.0 with DSTM miner v0.6.1 to mine Zcash. I have 3 GPUs, a GTX 1080 Ti, a GTX 970 and a GTX 750 Ti. They have hashrates of about 730, 280 and 90 Sols per second respectively, making my total hashrate at approximately 1100 Sols/s. I also use MSI Afterburner to overclock and tune my GPUs.

However, the first of my woes is that it has come to my attention that my average hashrate is always reported to be only at approx 280 (which is what my GTX 970 gives) instead of 1100, while the last hash often shows the correct values at around 1100 (I italicised the word 'often' due to the following issue below).

Next up, my last hash can sometimes go all the way down to just 5 Sols/s and cause the program to attempt to restart the miner, while in fact this is not the case at all.

For the above 2 issues, I have to set the average hashrate in the .ini file to be 0 to avoid this issue.

After which, I have just started receiving notifications that there is a long share timeout after the miner encounters rejected shares with code 20 ("Invalid Equihash solution") or 21 ("Stale job!"), again attempting to restart the miner. This was not the case in the past where the mining will still carry on as per normal even after encountering rejected shares. I had to disable last share timeout check in the .ini file in order to circumvent this problem.

Last but not least, not forgetting that the miner refuses to work with the string "--temp-target 80" in the .ini and DSTM_miner.bat files, as mentioned in the previous two posts in this forum.

I also need to mention that I just upgraded from DSTM v0.6 to v0.6.1 last night and these were the issues found when I was giving the new DSTM miner an extended test run throughout the night. It might not be your program's fault, but I thought it will be worth mentioning these issues to you in case you can provide a hotfix for those who use DSTM v0.6.1. These issues did not surface when I was using DSTM v0.6.

I will provide pictures later as I am currently working. Nonetheless, thank you for creating this program to allow me to watch over my miner when I'm not at home!

Fixed. Thank you for detailed report. Test it please on 2.0.1 and report me again!

Quote from: jeebzato on May 18, 2018, 07:38:38 PM

Hi Acrefawn! Would it be possible to add the ability to run special commands (batch file) prior to restarting the miner?

I am currently using cast-xmr but overclocking my cards using overdriventool. This app doesn't persist (so no process to monitor). It applies the settings and then closes.

The GPUs I use are Vega64s, which sometimes also need to have their drivers reinitialized (using device manager, disabling and re-enabling). There is a Windows app that can do this via command line but again there is no way for me to do this with your script right now. I think this would help the cast-xmr vega64 community significantly.

thank you!

Noted

Quote from: zimpixa_miner on May 24, 2018, 09:40:00 AM

Bug report

Code:

[2018-05-23][21:13:28] Miner was started. Script v.2.0.0.
[2018-05-23][22:06:58] Received new job 1c
[2018-05-23][22:06:58] Miner restarting, please wait... Miner ran for *00:54:02*.
[2018-05-23][22:07:05] Process bminer.exe was successfully killed.
[2018-05-23][22:07:35] miner.log moved to Logs folder as miner_5.23_22.7.log
[2018-05-23][22:07:38] Miner was started. Script v.2.0.0.
[2018-05-23][22:29:58] Received new job 2c
[2018-05-23][22:29:58] Miner restarting, please wait... Miner ran for *00:22:52*.
[2018-05-23][22:30:05] Process bminer.exe was successfully killed.
[2018-05-23][22:30:35] miner.log moved to Logs folder as miner_5.23_22.30.log
[2018-05-23][22:30:38] Miner was started. Script v.2.0.0.
[2018-05-23][22:31:23] Received new job 2c
[2018-05-23][22:31:23] Miner restarting, please wait... Miner ran for *00:01:17*.
[2018-05-23][22:31:30] Process bminer.exe was successfully killed.
[2018-05-23][22:32:00] miner.log moved to Logs folder as miner_5.23_22.31.log
[2018-05-23][22:32:03] Miner was started. Script v.2.0.0.
[2018-05-23][22:36:18] Received new job 2c
[2018-05-23][22:36:18] Too many errors. Threshold of 5 runtime errors reached. A restart of the computer to clear GPU cache is required. Restarting... Miner ran for *00:04:47*.
[2018-05-23][22:36:21] Computer restarting...
[2018-05-23][22:38:10] Config_Bmnr.ini loaded.
[2018-05-23][22:38:40] miner.log moved to Logs folder as miner_5.23_22.38.log
[2018-05-23][22:38:43] Miner was started. Script v.2.0.0.
[2018-05-23][22:59:48] Received new job 3c
[2018-05-23][22:59:48] Miner restarting, please wait... Miner ran for *00:21:33*.
[2018-05-23][22:59:56] Process bminer.exe was successfully killed.

Script badly recognised new job ending with C as error

Fixed. Thank you!

Update tomorrow!
Please report issues on my GitHub page it is more simpler to read it. Thank you very much to all for your trust and support the project!