Bitcoin Forum
June 16, 2024, 01:50:53 PM *
News: Voting for pizza day contest
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 [32] 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
Author Topic: TT-Miner 2024.1.2 BLAKE3, KAWPOW, ETHASH, ETCHASH, EPIC, SHA512256D, SHA3D, ETI  (Read 131985 times)
Shivoreun
Member
**
Offline Offline

Activity: 130
Merit: 10


View Profile
April 19, 2019, 02:20:40 PM
 #621

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

P.S. Sorry for errors in English - it's not my native language...
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 19, 2019, 02:37:02 PM
 #622

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

Hi,

0.0.0.0 will be translated to localhost (127.0.0.1). The default port is 4068. So if you have only a single network card installed on your rig you may want to try:
-b 127.0.0.1:4034

Did it work with an older version of TT and is now broken with 2.2.2, or is this just the first time that you try to get TT to work with Awesome Miner???

Thanks for reporting.
abudfv2008
Full Member
***
Offline Offline

Activity: 728
Merit: 106


View Profile
April 19, 2019, 03:39:38 PM
 #623

TrailingStop
Is there any way to disable Crashdump file creation?
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 19, 2019, 04:02:27 PM
 #624

TrailingStop
Is there any way to disable Crashdump file creation?


No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened?Huh Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.

lansettan
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
April 19, 2019, 04:36:14 PM
 #625

Hi,


TT-Miner Version 2.2.2 is available.

The new miner is available as command line version only, I dropped the windows GUI release because there was no need for it. So far, I have support for windows 7, 8.1 & 10 and Nvidia. The miner required about 4-5 minutes until it shows a stable hashrate. To get independent information about miner speeds you should always compare hashrates @ the pool, shares @ the pool or just the profit you made.

The DevFee is 1% for all algos.


Supported algorithms:
   - PROGPOW (BCI, more to come)
   - ETHASH (Ethash (ETH, ETC, Music, Callisto, etc)
   - UBQHASH (UBIQ)
   - MTP (Zcoin)
   - MYRGR / Myriad-Groestl (Myriad, DigiByte, Verge, etc)
   - LYRA2REV3 (Vertcoin)

Starting with version 2.1.11 TT-Miner support mining MTP and Ethash on Nicehash.

In the current version the miner support cuda 9.2, 10.0 and 10.1.If you want to make sure that TT-Miner uses a certain cuda version please append one of these values, id you do not append any of them, the miner will always use the algo for the latest cuda version:

   -92      for cuda 9.20   (ETHASH-92, UBQHASH-92)
   -100      for cuda 10.00   (ETHASH-100, PROGPOW-100)
   -101      for cuda 10.10   (ETHASH-101, MTP-101)

Please note these requirements for the different cuda toolkit releases:
Cuda-Toolkit               Linux                Windows      
CUDA 10.1.105          >= 418.39         >= 418.96
CUDA 10.0.130          >= 410.48         >= 411.31
CUDA 9.2.148            >= 396.37         >= 398.26


Note for xzc mining on Nicehash: Please make sure that you do not have -RH or -rate on your command line. Nicehash doesn't not like hashrate reporting and will disconnect if this notification is sent.


Please find below the available parameter and arguments, arguments in [] are not required:

-a, -A, -algo      ALGONAME   select the algorithm to use for mining
         ETHASH         Ethash (ETH, ETC, Music, Callisto, etc)
         UBQHASH      Ubiq version of Dagger-Hashimoto (UBIQ)
         PROGPOW      ProgPoW (BitcoinInterest)
         MTP               MTP (Zcoin algo)
         MYRGR         Myriad-Groestl (Myriad, DigiByte, Verge, etc)
         LYRA2V3         Lyra2 Revision 3 (Vertcoin)

This parameter will always load the algo that fits best to the installed driver. If you want
to make sure that TT-Miner uses a certain cuda version please append one of these values:
         -92      for cuda 9.20   (ETHASH-92, UBQHASH-92)
         -100      for cuda 10.00   (ETHASH-100, PROGPOW-100)
         -101      for cuda 10.10   (ETHASH-101, MTP-101)

Please note these requirements for the different cuda toolkit releases:
Cuda-Toolkit      Windows      Linux
CUDA 10.1.105      >= 418.39   >= 418.96
CUDA 10.0.130      >= 410.48   >= 411.31
CUDA 9.2.148      >= 396.37   >= 398.26


-d, -device, -devices   Comma or space separated list of devices that should be used mining. IDs starts with 0
-gpus
 

-work-timeout      NOT supported (ignored)
-coin            NOT supported (ignored)
-i, -mi, -intensity   Comma or space separated list of intensities that should be used mining. First value
            for first GPU and so on. A single value sets the same intensity to all GPUs. A value
            of -1 uses the default intensity of the miner. A sample may look like this:
      -i 18,17,-1,18      sets intensity of 18 to the first and fourth GPU, 17 to the
                  second and the third keeps the default of the miner. The GPUs
                  are the GPUs you may have selected with the -d parameter. If you
                  have installed 6 GPUs and use -d 3 4, the parameter -i 19 18
                  will set the intensity of 19 to your system GPU 3 and 18 to GPU 4.

-i auto INT INT INT     TT-Miner will iterarate throu some gridsizes to find the best for you system and algo combination.
            -i auto 1024 8192 256 will go from 1024 to 8192 with a stepsize of 256. If the iteration finishes TT
            will print the results to the screen.

-ig, -gs         intensity grid/grid-size. Same as intensity (-i, -intensity) just defines the size for the grid directly.
            This will give you more and finer control about the gridsize.


            API options Monitor/Control:
-b, --api-bind      IP[:port]      enables the monitoring API of TT-Miner to the IP address. If you
                     omit the port, port 4068 is used as default
--api-type         Protocol      TCP/WebSocket - parameter ignored
--api-password      password      assigns a password to the API


            Parameter without argument
-RH, -rate         Reports the current hashrate every 90 seconds to the pool
-n, -list, -ndevs      List the detected CUDA devices and exit
-logpool         Enable logging of the pool communication. TT-Miner creates the pool-logfile in the folder 'Logs'.
-log            Enable logging of screen output and additional information, the file is created in the folder 'Logs'.
-luck            Show a second information line that shows you how long it should take to find a new solution (share).
            Additionally the time already spend on the new solutions is printed and also a 'luck' value
            in percent that shows you the progress. Values below 100% indicate that there is still time
            left until the next solution should be found. Values above 100% indicate that the miner needs
            more time to find the new share than expected. These values are 'long term' statistical
            indications.
-U, --nvidia      Mining using CUDA devices (just for combability - can be omitted)
-X            Mining with OpenCL (just for combability - NOT supported)
-G, --amd         Mining using AMD devices (just for combability - NOT supported)
-h, --help          Show this help and exit
-v, --version      Show TT-Miner version and exit
-nocolor         Disables color output


            Pool definition - defines all values that are required for a connection to a mining pool.
-P            [scheme://]user/wallet[.workername/username][:password]@hostname:port

            The minimal definition to connect to a pool is:
            -P YOUR_WALLET@YOUR_SERVER_IP:YOUR_SERVER_PORT

            With all options it look like this
            -P stratum+tcp://YOUR_WALLET.YOUR_WORKER:YOUR_PASSWORD@YOUR_SERVER_IP:YOUR_SERVER_PORT

            'stratum+tcp://' is not required because TT-Miner will automatically detect the
            correct stratum protocol in use.
            The first -P will define your primary pool, all following -P definition will work as
            backup/failover pool.

-o, -url, -pool      YOUR_SERVER_IP:YOUR_SERVER_POOL
-u, -user, -wal      YOUR_WALLET[.YOUR_WORKER] or YOUR_USER
-o, -pass         YOUR_PASSWORD
-worker         YOUR_WORKER

-pool2         YOUR_BACKUP_SERVER_IP:YOUR_BACKUP_SERVER_POOL
-wal2            YOUR_BACKUP_WALLET[.YOUR_BACKUP_WORKER] or YOUR_BACKUP_USER
-pass2         YOUR_BACKUP_PASSWORD
-worker2         YOUR_BACKUP_WORKER

-PP INT         Process-Priority
            This option set the process priority for TT-Miner to a different level:
             1 low
             2 below normal
             3 normal
             4 above normal
             5 high
            Default: -PP 3
         
            Screen-Output
-PRHRI INT      Performance-Report Hash-Rate Interval
            Performance-Report & information after INT multiple of one minute. Minimum value for INT to
            1 which creates a hashrate interval of a minute. Higher Intervals gives you a more stable
            hashrate. If the interval is too high the displayed average of your hashrate will change
            very slowly. The default of 2 will give you an average of 2 minutes.
            Default: -PRHRI 2

-PRT INT         Performance-Report & information after INT multiple of 5 seconds
            Set INT to 0 to disable output after a fixed timeframe
            sample -RPT 24 shows the performance report after 24 * 5 sec = 2 minutes
            Default: -PRT 3

-PRS INT         Performance-Report & information after a INT shares found
            Set INT to 0 to disable output after a fixed number of shares
            sample -RPS 10 shows the performance report after 10 shares were found
            Default: -PRS 0

         Mixed sample:
            - You want to see the performance report all 25 shares and all 30 secs:
               -PRS 25 -PRT 6
            - You do not want to see any performance report:
               -PRT 0


No changes and exceptions to windows defender required – the TT-Miner is not suspected to contain a virus. Please check also VirusTotal information:
https://www.virustotal.com/#/url/f80ff82eb6654f4f038ac5a7d8a3678a11b6af73086484fb2a9c9daef4a7edf8/detection


A sample command line might look like this:
TT-Miner.exe -A PROGPOW-100 -P YOUR_WALLET.YOUR_WORKER@POOL_SERVER:POOL_PORT

Stating from version 2.1.5 TT-Miner can understand most of the used command line arguments. If you already use any miner it should be OK just to replace the program name an leave the remaining arguments as they are. If you have a combination that TT-Miner does not understand please let me know so that I can fix that.


If you look for possible command line options please start the miner with the -h or --help option: TT-Miner.exe -h


Download link:
https://TradeProject.de/download/Miner/TT-Miner.zip
SHA-256: ca1e9c213d70361f7544f5ff6de0bd79d858e821d467098c9548b64ad7a1a12b


Older versions:
https://TradeProject.de/download/Miner/TT-Miner-2.2.1.zip
https://TradeProject.de/download/Miner/TT-Miner-2.2.0.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.19.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.18.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.17.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.16.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.15.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.14.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.13.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.12.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.11.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.10.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.9.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.8.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.7.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.6.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.5.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.4.zip
https://TradeProject.de/download/Miner/TT-Miner-2.1.3.zip


The miner required the latest C-runtime from Microsoft. If some dlls are missing when you start the miner you might need to install the CRT. You can get the CRT from Microsoft:
https://go.microsoft.com/fwlink/?LinkId=746572


TT-Miner is NOT free of bugs, so if you find one please help to make TT-Miner better and report it to me so that I have a chance to fix it.

Happy mining!


thanks
Shivoreun
Member
**
Offline Offline

Activity: 130
Merit: 10


View Profile
April 19, 2019, 05:12:45 PM
 #626

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

Hi,

0.0.0.0 will be translated to localhost (127.0.0.1). The default port is 4068. So if you have only a single network card installed on your rig you may want to try:
-b 127.0.0.1:4034

Did it work with an older version of TT and is now broken with 2.2.2, or is this just the first time that you try to get TT to work with Awesome Miner???

Thanks for reporting.
Thanks for reply Smiley

Previously I was using 2.1.14 and there were no such problem Undecided Didn't tested another older versions yet...
Then, what I should set in "-b" option to allow API requests from any address?.. Looks like, that regardless of the settings, the miner accepts only connections from locahost Sad

P.S. Sorry for errors in English - it's not my native language...
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 19, 2019, 06:12:17 PM
 #627

Hi to community.
The remote API response in v2.2.2 is not working? Or there is some trick needed to get it to work?
I'am using Awesome Miner, and it can get the stats from the miner, but any other software can't connect to the specified port. The Awesome Miner uses --api-bind 127.0.0.1 network, but I assume this will allow only localhost connections, that's why it's working.
I've tried the -b 0.0.0.0:4034 and --api-bind 0.0.0.0:4034 (and different ports), but miner is not responding. According to the TCPview, the tt-miner.exe is binding on the specified port (4034), but no connection Sad

Is there some additional options that should be set to get remote stats via API?..

Hi,

0.0.0.0 will be translated to localhost (127.0.0.1). The default port is 4068. So if you have only a single network card installed on your rig you may want to try:
-b 127.0.0.1:4034

Did it work with an older version of TT and is now broken with 2.2.2, or is this just the first time that you try to get TT to work with Awesome Miner???

Thanks for reporting.
Thanks for reply Smiley

Previously I was using 2.1.14 and there were no such problem Undecided Didn't tested another older versions yet...
Then, what I should set in "-b" option to allow API requests from any address?.. Looks like, that regardless of the settings, the miner accepts only connections from locahost Sad

Hi,

the miner does not filter any addresses. It looks to me like you have 2 (or more) network interfaces and the API bind to the wrong. The address you use for the api command is to tell the miner which network interface to enable for api access. If you have only one localhost is fine, if you have more it makes sense to tell the miner which one to use. You can check your IPs with 'ipconfig -all' command in the console. Let me know if that help or if you still have problems to get connected.

abudfv2008
Full Member
***
Offline Offline

Activity: 728
Merit: 106


View Profile
April 19, 2019, 06:20:37 PM
 #628

TrailingStop
Is there any way to disable Crashdump file creation?


No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened?Huh Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.


The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 19, 2019, 06:25:02 PM
 #629

TrailingStop
Is there any way to disable Crashdump file creation?


No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened?Huh Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.


The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Got it. I compile you a beta without crashdump. If you can it would be great if you can DM me the crashdump anyway because I would like to fix any bugs that are in the miner. The crashdump would help me a lot to find a bug.

TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 19, 2019, 06:43:45 PM
 #630

TrailingStop
Is there any way to disable Crashdump file creation?


No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened?Huh Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.


The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Hi,

I send you a DM with the link to the beta that doesn't create a crashdump file anymore. Let me know if that works OK for you.

Thanks.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 20, 2019, 02:17:11 AM
 #631

Hi, is GPU power info being passed in API?

I see power info correctly as TT-miner is running, but not via API

With cryptoDredge i get GPU power info passed via API to Awesome Miner...

Want to make sure i have everything setup/configured correctly in TT-Miner...

Thank you!


Hi,

to enable the power usage in Awesome miner you should follow the recommendations for "Map to system montioring".
https://support.awesomeminer.com/support/solutions/articles/35000086014-display-additional-gpu-information

Please let me know if that is what you were locking for.

Thanks.
Ngenah Euy
Jr. Member
*
Offline Offline

Activity: 207
Merit: 5


View Profile
April 20, 2019, 06:47:16 AM
 #632

is it also work for ZANO (ProgPOWZ)? thanks
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 20, 2019, 06:56:18 AM
 #633

is it also work for ZANO (ProgPOWZ)? thanks

Do not know - will check. Will let you know later today.
johndoughtoo
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
April 20, 2019, 10:28:24 AM
 #634

Hi, is GPU power info being passed in API?

I see power info correctly as TT-miner is running, but not via API

With cryptoDredge i get GPU power info passed via API to Awesome Miner...

Want to make sure i have everything setup/configured correctly in TT-Miner...

Thank you!


Hi,

to enable the power usage in Awesome miner you should follow the recommendations for "Map to system montioring".
https://support.awesomeminer.com/support/solutions/articles/35000086014-display-additional-gpu-information

Please let me know if that is what you were locking for.

Thanks.


That only works in managed miner mode (having the awesome miner software installed directly on each of the miner systems directly)
I do not use any "managed" miners - they are all external miners. And the only way to monitor an external miner is with the API.
Thank you for the info and option, If i install AM on the miner itself, this would be VERY HELPFUL.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 20, 2019, 01:06:26 PM
 #635

Hi, is GPU power info being passed in API?

I see power info correctly as TT-miner is running, but not via API

With cryptoDredge i get GPU power info passed via API to Awesome Miner...

Want to make sure i have everything setup/configured correctly in TT-Miner...

Thank you!


Hi,

to enable the power usage in Awesome miner you should follow the recommendations for "Map to system montioring".
https://support.awesomeminer.com/support/solutions/articles/35000086014-display-additional-gpu-information

Please let me know if that is what you were locking for.

Thanks.


That only works in managed miner mode (having the awesome miner software installed directly on each of the miner systems directly)
I do not use any "managed" miners - they are all external miners. And the only way to monitor an external miner is with the API.
Thank you for the info and option, If i install AM on the miner itself, this would be VERY HELPFUL.

Hi,

I will try to find a better solution for you.
Shaddyr
Jr. Member
*
Offline Offline

Activity: 48
Merit: 2


View Profile
April 20, 2019, 02:12:11 PM
 #636

One bug yet: miner don't report if one of the card had crashed. It continue to work with others but failed one is absent. And didn't notice anything about situation at console.

PS: have a CrashDump.dmp. Will send it to TS via PM.
Vivik
Full Member
***
Offline Offline

Activity: 197
Merit: 100


View Profile
April 21, 2019, 12:41:43 AM
 #637

Version 2.2.2 when installed by default works without problems on farm 8 card.
abudfv2008
Full Member
***
Offline Offline

Activity: 728
Merit: 106


View Profile
April 21, 2019, 06:58:56 AM
 #638

TrailingStop
Is there any way to disable Crashdump file creation?


No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened?Huh Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.


The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Hi,

I send you a DM with the link to the beta that doesn't create a crashdump file anymore. Let me know if that works OK for you.

Thanks.

Thank you - now mining with 2.2.3beta.
Can you add config file option, like other miners have? Length of cmd string is limited and I can't add 2-3 failover pools.
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 21, 2019, 07:01:08 AM
 #639

Version 2.2.2 when installed by default works without problems on farm 8 card.

Hi,

thanks you for your info - can you please add some additional information like, GPUs, OS, RAM, Virtual memory settings etc?
TrailingStop (OP)
Member
**
Offline Offline

Activity: 566
Merit: 16


View Profile
April 21, 2019, 07:05:33 AM
 #640

TrailingStop
Is there any way to disable Crashdump file creation?


No- if you see a crashdump something serious bad happens. Can you send one of them to me so that I can check what happened?Huh Please add some information link algo, coin, pool, gpu, version so that I have some more information to fix the bug? I will add an option into the next release to disable crashdumps.


The problem is that it equals RAM size. For small sized ssd on rigs it is a problem that leads to another.
Miner folder is synced with other rigs - so I get 4Gb/8Gb file syncing and flooding network.
Actually I don't care if miner crashed by some reason once/twice a day - it will be restarted in a moment, but another 4Gb file syncing is a problem.

Hi,

I send you a DM with the link to the beta that doesn't create a crashdump file anymore. Let me know if that works OK for you.

Thanks.

Thank you - now mining with 2.2.3beta.
Can you add config file option, like other miners have? Length of cmd string is limited and I can't add 2-3 failover pools.

Ah- I never reached that limit. Will try to add something like this in the release after next.

Thanks for your suggestion!
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 [32] 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!