Author

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 214. (Read 703148 times)

jr. member
Activity: 756
Merit: 2
PAtrick I know you can add auto exchange groups as long as they are Yiimp
But as we added Nicehash BEAM in 150.5 that is not how I can add it.
legendary
Activity: 3346
Merit: 1094
Hi Patrike, any chance of adding support for AMD cards for BEAM, specifically OpenCL miner:  https://www.beam.mw/downloads

Keep up the great work!
Thanks for your suggestion and nice comments.

I've not checked out that one before. Does anyone know how this one compares to lolMiner, where the latest alpha versions supports Beam on AMD OpenCL?

Awesome Miner isn't using this alpha version of lolMiner by default because it only supports this algorithm at the moment.
legendary
Activity: 3346
Merit: 1094
Will the API for Bminer be supported at some point?
Bminer has been supported for a long time, both as Managed Miner and External Miner. Is there a specific API feature you are missing?
legendary
Activity: 3346
Merit: 1094
Hi Patrike !

When I'm minning Beam with Gminer 1.23 AM sends this command :

Code:
miner.exe  -a 150_5 -s beam.eu.nicehash.com -n 3370 -u 3LgnBTzLFZiKyDpAc9n7V42zphkz3cjx21 -p x --pers auto -w 0 --api 4028

And the --pers auto doesn't work with sparkpool, if I remove this it works well with a bat file, but I can't manage to remove --pers auto in AM.

Thx
Awesome Miner is currently adding "auto" if you didn't specify any personalization string in the Properties of the Pool you have defined in Awesome Miner.

The example above was for Nicehash. Can you share the exact command line you use for Sparkpool? For sparkpool I do now that you need to add "--ssl 1" for Gminer to connect correctly.

How do you see that "--pers auto" creates a problem - do you get any error message in Gminer while connecting to Sparkpool? When I add "--pers auto" it still connects fine.
legendary
Activity: 3346
Merit: 1094
Hi, anyone know how to get awesomeminer to pass the correct configuration info to Grinpro miner?  Can do it manually using Grinpro of course, but when I have awesominer do it, it doesn't initialize the GPUs

Figured out a little workaround to get it working, in the GrinPro folder:  
    1.  Deleted the config.xml file
    2.  Ran GrinProMiner.exe
    3.  Closed it after it successfully created a new config.xml
    4.  Right clicked on the new config file and changed it to "Read Only"
    5.  Started to GRIN as I checked out my mining stats on AwesomeMiner

*Using 6 Sapphire RX580 8G, getting just under 12 gps
Great that you found a workaround for this issue.

Grin Pro is a bit unique as it requires the configuration file to be populated with a list of GPU's. Awesome Miner was supposed to do that but I noticed that when you tell Awesome Miner to use all GPU's (the default selection), it didn't do this correctly.

If you instead use the GPU selection feature in Awesome Miner and check each GPU individually, Awesome Miner will produce a working configuration file for Grin Pro miner.

I will of course improve this behavior in the next release to make sure it runs better when configured to use all GPU's.
legendary
Activity: 3346
Merit: 1094
Hi, Patricke. Great work. Please add an algo æternity(Cuckoo Cycle)  for the coin AE.

Best wishes.
Thanks for your nice feedback!

I will add AE to the next release so it shows up in the list of coins with an icon and algorithm. There are however no coin statistics provider that includes any statistics for this coin so you will not yet be able to see any mining income. Once it's supported by any of the coin statistics providers it will show up with the correct stats in Awesome Miner as well.
legendary
Activity: 3346
Merit: 1094
In main "Miners" tab using the coin menu "Define Pool Coin" to select a coin, the coin logo images selected do not persist.  As soon as there is a profit switch on any other coin, the previously selected coin reverts to Unspec. "?" coin image.

This happens even with single coin algos. The profit info persists but not the coin image. v6.1.8
The "Define Pool Coin" is mapping a pool URL to a specific coin.

When you use the profit switcher in this case, is it a single coin pool you are mining on? The pools on Nicehash, zpool and so on should have the default "Unspecified X" coin as the coin isn't known.

Is your scenario like this, where both pool#1 and pool#2 are single coin pools?
1) You mine on pool#1 and the coin is Undefined. You define the coin to be A
2) The profit switcher moves on to pool#2 where the coin is Undefined as well. You define the coin to be B
3) The profit switches moves back to pool#1 - but the coin isn't remembered as A as it should be?
newbie
Activity: 11
Merit: 0
Hi Patrike, any chance of adding support for AMD cards for BEAM, specifically OpenCL miner:  https://www.beam.mw/downloads

Keep up the great work!
full member
Activity: 675
Merit: 100
Will the API for Bminer be supported at some point?
newbie
Activity: 11
Merit: 0
Hi, anyone know how to get awesomeminer to pass the correct configuration info to Grinpro miner?  Can do it manually using Grinpro of course, but when I have awesominer do it, it doesn't initialize the GPUs

Figured out a little workaround to get it working, in the GrinPro folder:  
    1.  Deleted the config.xml file
    2.  Ran GrinProMiner.exe
    3.  Closed it after it successfully created a new config.xml
    4.  Right clicked on the new config file and changed it to "Read Only"
    5.  Started to GRIN as I checked out my mining stats on AwesomeMiner

*Using 6 Sapphire RX580 8G, getting just under 12 gps
newbie
Activity: 21
Merit: 0
Hi Patrike !

When I'm minning Beam with Gminer 1.23 AM sends this command :

Code:
miner.exe  -a 150_5 -s beam.eu.nicehash.com -n 3370 -u 3LgnBTzLFZiKyDpAc9n7V42zphkz3cjx21 -p x --pers auto -w 0 --api 4028

And the --pers auto doesn't work with sparkpool, if I remove this it works well with a bat file, but I can't manage to remove --pers auto in AM.

Thx
newbie
Activity: 11
Merit: 0
Hi, anyone know how to get awesomeminer to pass the correct configuration info to Grinpro miner?  Can do it manually using Grinpro of course, but when I have awesominer do it, it doesn't initialize the GPUs
newbie
Activity: 107
Merit: 0
Hi, Patricke. Great work. Please add an algo æternity(Cuckoo Cycle)  for the coin AE.

Best wishes.
newbie
Activity: 52
Merit: 0
In main "Miners" tab using the coin menu "Define Pool Coin" to select a coin, the coin logo images selected do not persist.  As soon as there is a profit switch on any other coin, the previously selected coin reverts to Unspec. "?" coin image.

This happens even with single coin algos. The profit info persists but not the coin image. v6.1.8


legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.1.8

 User interface
  - View Details dialog, Profit switching page, includes information about defined power usage for each pool considered by the profit switcher
 Mining software
  - Added mining software: Grin Pro Miner for Grin mining on both nVidia and AMD. Requires Microsoft ASP.NET Core 2.2.1 Runtime to be installed.
  - SrbMiner 1.7.7
  - CastXMR 1.7.1
  - JCE CPU miner 0.33p
  - JCE GPU miner 0.33b17
 Corrections
  - UI adjustment to Profit Profile, Override section

Please note that if you are planning to use Grin Pro Miner, you need to install ASP.NET Core 2.2.1 first:
https://dotnet.microsoft.com/download/thank-you/dotnet-runtime-2.2.1-windows-x64-asp.net-core-runtime-installer
newbie
Activity: 22
Merit: 0
Block all incoming connections takes precedence over any other rule.

I manually changed the allow rules created by awesome miner for the mining software to block rules. Have been mining since I originally asked about this without any issue or popup (picture of my rules linked). The problem is that when new software is added/updated new rules will be created by awesome miner as allowed rules.
https://imgur.com/a/w7YBXdZ

If you make this an option you could just leave the default as it is now(allowed rules), just in case "blocked" rules might break anything for someone.
Thanks for the update.

I've made a quick implementation to support this case. I've introduced a new setting that you can set directly in the Awesome Miner configuration file as I don't want to expose this in the user interface.

1) Once the next version of Awesome Miner is available, install it, run it once and then exit the application.
2) Open the configuration file (%appdata%\AwesomeMiner\ConfigData.xml) and search for "ConfigureWindowsDefenderAllowedApps".
3) Change the property from true to false and save the file.
Thanks, I tried but it showed a popup the first time a mining software ran.
While testing further I found out 2 possible reasons why:
1 When creating a block rule the rule is created with Profile Private(current profile), while when creating an allow rule the rule is created with Profile All.
2 When creating a block rule the rule is added to the registry a couple of seconds after the miner software is launched, while when creating an allow rule the rule is added to the registry a few milliseconds before the miner software is launched.
I didn't test extensively but I'm guessing #1 has something to do with defaults, for #2 my guess is some firewall api limitation or maybe it is not the cause of the issue.
Hopefully you can take another look at it, otherwise I'll just create a script that runs now and then and modifies the rules as needed.
Even that my lan is relatively secure and have trustworthy people connecting to it, I don't want to leave my mining software open.

Thanks again.
The default behavior of Awesome Miner is to add this Allowed Apps rule. In that case things should just work and you shouldn't see any dialogs from Windows Defender. Is that correct according to your observations as well? I don't have any plans to change how these rules are set at the moment, as what Awesome Miner do works very well in a very large number of mining environments out there.

If you use the new property set to false, Awesome Miner will not do anything with the firewall configuration. I assume it's in only in this case you are getting the warnings from Defender? With the automatic configuration disabled in Awesome Miner, you are basically on your own here and you can manually configure (or not configure) the rules as you want.
I'm feeling that I'm failing to communicate what I want to say a lot, sorry about that and thank you for your patience. Maybe you make me nervous Wink

I meant that when configuring ConfigureWindowsDefenderAllowedApps as true the rules (allow rules) are being created with Profile=All, but when configuring ConfigureWindowsDefenderAllowedApps as false the rules(block rules) are being created with Profile=Private, I believe the difference in profile causes the popups to come up when ConfigureWindowsDefenderAllowedApps is set to false.
Thanks for the update. Your observations when running with ConfigureWindowsDefenderAllowedApps set to false are probably what to expect, as it's totally up to Windows to decide when to block, when to show the dialog and what rule to add in that case. Awesome Miner will do nothing, which is the purpose of setting the property to false.

Although I understand your observations here, I don't fully understand what you want Awesome Miner to do here. It can already do:
1) Add allowed apps automatically. This is the default, has been around for years and works fine for the purpose of mining.
2) The new mode when ConfigureWindowsDefenderAllowedApps set to false will result in Awesome Miner doing nothing. You are on your own to do what you want here. Any dialogs, blocking and so on you see is related to configuration of Windows and not Awesome Miner.

There are no feature in Awesome Miner to configure the allowed apps in any new way - either it's configured in a way that work (#1) or it's not touching anything (#2). Sorry if I missed your point here.

ConfigureWindowsDefenderExclusions defines whether firewall rules are created by awesome miner or not.
ConfigureWindowsDefenderAllowedApps(the one you added recently) defines whether the rules are created by awesome miner as allow rules(true) or block rules(false).
When ConfigureWindowsDefenderAllowedApps is set to true(default) the created rules are being created by awesome miner with Profile=All, when it is set to false the rules are being created by awesome miner with Profile=Private. I'd like the rules to be created with Profile=All regardless of ConfigureWindowsDefenderAllowedApps being true or false. I believe having Profile=All on the block rules(when ConfigureWindowsDefenderAllowedApps is set to false) might prevent popups to come up.
ConfigureWindowsDefenderExclusions is only for addings paths as exclusions to the anti-virus scan and that feature is always on by default. Otherwise Windows Defender will start removing all mining software it considers a thread.

"When ConfigureWindowsDefenderAllowedApps is set to true(default) the created rules are being created by awesome miner with Profile=All"
Correct assumption. In this case Awesome Miner makes a configuration that is proven to work well with mining

"when it is set to false the rules are being created by awesome miner with Profile=Private."
Not correct assumption. Awesome Miner do nothing to the Allowed Apps here. It will not touch the rules at all when this property is set to False. The behavior you experience is what Windows is doing when Awesome Miner no longer takes responsibility for configuring Defender for you. Any rules added at this point is what Windows is doing. This was the point I was trying to make above that when you tell Awesome Miner to not setup the Allowed Apps for you, you will be on your own and you will most likely run into issues with Defender unless you manually find a way to setup everything.

I'm have to admit that I'm not really an expert on all these Defender settings and the exact behaviors of when Windows is adding these rules automatically. If I knew more of the details, I would of course want to help out more with suggestions how to make these configurations. This is the reason why my answers above is based on everything from an Awesome Miner and mining point of view.
You are right, having ConfigureWindowsDefenderExclusions=true and ConfigureWindowsDefenderAllowedApps=false made windows auto create the block rules with Profile=Private. I misunderstood what ConfigureWindowsDefenderAllowedApps=false would do.

Manually changing the allow rules created by awesome miner to block rules worked fine for me (as shown on the picture), so I will just let awesome miner create the default rules and run an extra script every minute or so to change them from allow to block rules.

Thanks.
legendary
Activity: 3346
Merit: 1094
Please add CryptoNight Lite V8 (For Masari) Wink
Thanks for the suggestion. I will include that one but probably call it Cryptonight Fast2 as that looks like an even more common name for it. I will update SrbMiner and CastXMR for this as well.
legendary
Activity: 3346
Merit: 1094
Awesome Miner version 6.1.7

 GPU mining
  - The Managed Profit Switcher can be configured with a list of custom pools without having to define a pool group
 Mining software
  - BMiner 14.0
 Corrections
  - Corrected an issue related to updates of statistics on the Coins tab
  - Adjusted Gminer total hashrate to be calculated as a total of all GPU's to workaround rounding errors in the Gminer API for Grin mining

Have just tried the update, however, could not know how to add or edit the list of customer pools of the profiles, how to roll back.

Please help to check.
thanks
Hi,

Is it the Profit Profile specific custom pools you are referring to? They are configured in the Profit Profile, Override section, just like before. You can add, edit and remove pools from the list here.

Can you describe the exact steps where it's not working? Thanks!

If you do consider a downgrade - please backup the configuration file first, as downgrading isn't an officially supported scenario. More about backups:
https://support.awesomeminer.com/support/solutions/articles/35000098571-awesome-miner-configuration-file
Version 6.1.6 can be found here:
https://www.awesomeminer.com/download/v616/AwesomeMiner.msi

I could not find the add/edit/remove button on the  Profit Profile, Override section, I don't know if it's os display issue, I'm using win7 x64. (if could add those on the mouse right click button pop menu will be great)

Please note.

thanks
Thanks for letting me know. I'm guessing that you run with font scaling or similar enabled in Windows? If you don't use 100%, maybe you could test if it works better on 100%?

I will make the UI area a bit larger to work around the issue.

I have not use font scaling and run the original 100% resolution in win7 x64, and could not find the button.

Please note.

Waitting for your next update.

thanks

Thanks for the update on this. I will make a change to the next release that include a change that hopefully will resolve the issue. The next release will soon be made available.

However, I don't have any way of reproducing this problem myself. Would it be possible for you to send me a screenshot?
legendary
Activity: 3346
Merit: 1094
Anyone know how to make AM work with AMD cards?
I just scored a good deal on four RX 570 8G but sadly can't use them to mine Grin or Beam yet. Sad
Any help would be appreciated.
Awesome Miner doesn't support any mining software for these algorithms on AMD yet. The popular mining software that supports these algorithms are for nVidia.

There are some new AMD mining software like GrinGoldMiner and GrinPro and they are very similar. Awesome Miner will support one of them later on. Right now you need to manually launch your AMD Grin mining software using the Generic Miner concept in Awesome Miner:
https://support.awesomeminer.com/support/solutions/articles/35000086017-generic-miner-use-any-mining-software

LoL miner works just fine for BEAM (0.7 version for BEAM only)
Thanks, good point. The reason why the 0.7 alpha version isn't included by default is that it only supports this algorithm like you point out.

you need Patrike, beam is very interesting, the other 150,5 miners do not support Beam, we have to install it as custom and it's something I do not like, but I will.

Please consider adding this version 7 alpha 3 that is used for beam
Thanks for the suggestion but I will not add this version right now as it only supports beam. If I make it predefined I will have to support it for a very long time.

Most likely this will be a version that is relevant for only a week or two before it's part of the main lolMiner releases. In these cases, you will have to manually add it. All download links are available on Github so the setup process should be fast.
legendary
Activity: 3346
Merit: 1094
Block all incoming connections takes precedence over any other rule.

I manually changed the allow rules created by awesome miner for the mining software to block rules. Have been mining since I originally asked about this without any issue or popup (picture of my rules linked). The problem is that when new software is added/updated new rules will be created by awesome miner as allowed rules.
https://imgur.com/a/w7YBXdZ

If you make this an option you could just leave the default as it is now(allowed rules), just in case "blocked" rules might break anything for someone.
Thanks for the update.

I've made a quick implementation to support this case. I've introduced a new setting that you can set directly in the Awesome Miner configuration file as I don't want to expose this in the user interface.

1) Once the next version of Awesome Miner is available, install it, run it once and then exit the application.
2) Open the configuration file (%appdata%\AwesomeMiner\ConfigData.xml) and search for "ConfigureWindowsDefenderAllowedApps".
3) Change the property from true to false and save the file.
Thanks, I tried but it showed a popup the first time a mining software ran.
While testing further I found out 2 possible reasons why:
1 When creating a block rule the rule is created with Profile Private(current profile), while when creating an allow rule the rule is created with Profile All.
2 When creating a block rule the rule is added to the registry a couple of seconds after the miner software is launched, while when creating an allow rule the rule is added to the registry a few milliseconds before the miner software is launched.
I didn't test extensively but I'm guessing #1 has something to do with defaults, for #2 my guess is some firewall api limitation or maybe it is not the cause of the issue.
Hopefully you can take another look at it, otherwise I'll just create a script that runs now and then and modifies the rules as needed.
Even that my lan is relatively secure and have trustworthy people connecting to it, I don't want to leave my mining software open.

Thanks again.
The default behavior of Awesome Miner is to add this Allowed Apps rule. In that case things should just work and you shouldn't see any dialogs from Windows Defender. Is that correct according to your observations as well? I don't have any plans to change how these rules are set at the moment, as what Awesome Miner do works very well in a very large number of mining environments out there.

If you use the new property set to false, Awesome Miner will not do anything with the firewall configuration. I assume it's in only in this case you are getting the warnings from Defender? With the automatic configuration disabled in Awesome Miner, you are basically on your own here and you can manually configure (or not configure) the rules as you want.
I'm feeling that I'm failing to communicate what I want to say a lot, sorry about that and thank you for your patience. Maybe you make me nervous Wink

I meant that when configuring ConfigureWindowsDefenderAllowedApps as true the rules (allow rules) are being created with Profile=All, but when configuring ConfigureWindowsDefenderAllowedApps as false the rules(block rules) are being created with Profile=Private, I believe the difference in profile causes the popups to come up when ConfigureWindowsDefenderAllowedApps is set to false.
Thanks for the update. Your observations when running with ConfigureWindowsDefenderAllowedApps set to false are probably what to expect, as it's totally up to Windows to decide when to block, when to show the dialog and what rule to add in that case. Awesome Miner will do nothing, which is the purpose of setting the property to false.

Although I understand your observations here, I don't fully understand what you want Awesome Miner to do here. It can already do:
1) Add allowed apps automatically. This is the default, has been around for years and works fine for the purpose of mining.
2) The new mode when ConfigureWindowsDefenderAllowedApps set to false will result in Awesome Miner doing nothing. You are on your own to do what you want here. Any dialogs, blocking and so on you see is related to configuration of Windows and not Awesome Miner.

There are no feature in Awesome Miner to configure the allowed apps in any new way - either it's configured in a way that work (#1) or it's not touching anything (#2). Sorry if I missed your point here.

ConfigureWindowsDefenderExclusions defines whether firewall rules are created by awesome miner or not.
ConfigureWindowsDefenderAllowedApps(the one you added recently) defines whether the rules are created by awesome miner as allow rules(true) or block rules(false).
When ConfigureWindowsDefenderAllowedApps is set to true(default) the created rules are being created by awesome miner with Profile=All, when it is set to false the rules are being created by awesome miner with Profile=Private. I'd like the rules to be created with Profile=All regardless of ConfigureWindowsDefenderAllowedApps being true or false. I believe having Profile=All on the block rules(when ConfigureWindowsDefenderAllowedApps is set to false) might prevent popups to come up.
ConfigureWindowsDefenderExclusions is only for addings paths as exclusions to the anti-virus scan and that feature is always on by default. Otherwise Windows Defender will start removing all mining software it considers a thread.

"When ConfigureWindowsDefenderAllowedApps is set to true(default) the created rules are being created by awesome miner with Profile=All"
Correct assumption. In this case Awesome Miner makes a configuration that is proven to work well with mining

"when it is set to false the rules are being created by awesome miner with Profile=Private."
Not correct assumption. Awesome Miner do nothing to the Allowed Apps here. It will not touch the rules at all when this property is set to False. The behavior you experience is what Windows is doing when Awesome Miner no longer takes responsibility for configuring Defender for you. Any rules added at this point is what Windows is doing. This was the point I was trying to make above that when you tell Awesome Miner to not setup the Allowed Apps for you, you will be on your own and you will most likely run into issues with Defender unless you manually find a way to setup everything.

I'm have to admit that I'm not really an expert on all these Defender settings and the exact behaviors of when Windows is adding these rules automatically. If I knew more of the details, I would of course want to help out more with suggestions how to make these configurations. This is the reason why my answers above is based on everything from an Awesome Miner and mining point of view.
Jump to: