Quote from: xunl on May 19, 2018, 09:45:34 PM

Feature request

In Phoenix miner, I can do
Phoenixminer.exe -list to get a list of GPUs and exit, NO MINING at all.
So I wrote a script to auto check if all GPUs boot up after windows start. If gpus are missing then reboot before start mining.
Can Claymore add something similar to list all gpus and exit w/o mining?

What's the difference: time to shutdown
When no mining operation is runing, shutdown /r /f /t 1 can take place right away.
When mining operation starts, even force kill the process can take a few seconds to minute to complete before reboot.

Since all the reboots are just fix errors and do not earn coins, the shorter the better.

Thanks

This is a weird request, did you actually look at the timestamp in the claymore log?
Or even look at the log?
Here is an example.

11:09:18:605   218c
11:09:18:605   218c   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
11:09:18:605   218c   º Claymore's Dual GPU Miner - v11.7 º
11:09:18:620   218c   º ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK º
11:09:18:620   218c   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼
11:09:18:620   218c
11:09:18:620   218c   b581
11:09:18:839   218c   ETH: 10 pools are specified
11:09:18:839   218c   Main Ethereum pool is eth-eu.maxhash.org:11011
11:09:20:668   218c   OpenCL platform: AMD Accelerated Parallel Processing
11:09:20:683   218c   OpenCL initializing...

11:09:20:683   218c   AMD Cards available: 8

As you see, Claymore took an ENTIRE TWO SECONDS to tell me how many GPU are present.
I defy you to better that by running some pointless info-only batchfile, read the output, e.g. all gpu present and accounted for, then run the actual start batch file. (in under 2 seconds).

Why don't you investigate why your rig is so unstable, that it needs stop, start, fail, reboot, before mining, THAT is indeed wasted time, it also indicates far more serious underlying issues with your rig, issues likely to cause stoppages, crashes, and forcing you to reboot, THAT is time worth saving, but is not solved, assisted or aided by this request imho.

Send some info on your rig, os, versions, hardware, check your system event logs, follow best practise guidelines, (no updates unless there is specific mention of a "something" you need, a problem YOU HAVE, that is specified solved etc), disable all services not relevant to mining, remove all scheduled tasks, lean-rig philosophy etc.

Ignore everyone who gives advice such as "update your driver" without actually specifying WHAT version they mean you to use, (moronic in the extreme!)

Read the claymore readme, especially the last sections.

If all else fails, divide and conquer, (remove half your GPUs/risers,cables, power cables, headers, and run the rig, if it exhibits the same issues of instability, remove that half of the hardware, and add back the other half. If that is stable, you can narrow down by adding back, half the other half removed hardware, (1/4 etc), keep dividing order/half, and eventually you will find the cause. Systematic, quantifiable testing and analysis.
Working by halves exponentially increases the odds you'll find the cause, (faster than one by one etc), and it also covers situations like too much load on psu for example.

Work with all clocks and powers at the factory settings, until you're confident it's stable.
THEN start the OC, and hard-core stuff.

Remember, if you're overclocking, you're pushing it. Some hardware is more tolerant than others, equally, you're possibly shortening the MTBF, so don't assume stability is a permanent situation, given time, there will be degradation, THAT is an absolute certainty.

Good luck.