 Show Posts
|
|
Pages: [1] 2 3 4 »
|
I'm having some questions about P2Pool mining, I'm mining on http://elizium.name node with 2 Antminer S3+'s, at about 920GH/s. But I've been mining for 12+ hours now, and I still have nothing. I added after my payout address "+518" but still nothing. Is this normal or...? You in the public node mining, luck is very big, this is normal.  |
|
|
|
Is it better to run your own node or use a public one? When using a pubic one does it matter which one you use? Also, with an S3+ do I need to change the diff?
As windpath stated, it's always recommended to run your own local node; however, it's not always possible to do so. There are plenty of publicly available nodes to which you can point your miners, windpath's certainly being one of the best in my opinion. It doesn't matter which node you end up using, but you should try to find one that has been up and running for a while, has a good ping time from your location and has a low number of dead/orphan shares. No, you don't need to change the diff using an S3+. The node on which you are mining will dynamically assign your miner a difficulty based upon the node's hash rate. If you look a few posts up, you'll see our Chinese friends have posted some screenshots of their settings. By the way, congrats to them on finding that block! If the node pool stress 100TH/S, Dynamic miners difficulty: 20000 - 30000. The efficiency is very low. If the node is the force 10TH/S, Dynamic miners difficulty: 1000 - 3000. Thank you for your blessing. I wish you good luck.  |
|
|
|
  请使用正确的难度。 P2POOL，这15天效率很低， 原因：中国矿工约有1.5PH/S，使用了超大的难度（+5120或者更多）， 我们及时的更改了错误，目前全部使用大约是难度比例1:1。 P2POOL这些天低效率，我们表示抱歉。 但是我们认识到了最好的难度选择是：选择和矿机算力相等的难度。 当前我们的蚂蚁S3+518（+512，S3不显示BestShare）， 1TH/S+1028， S3+518，平均5秒一个Accepted。 S3+5120，大部分计算都超时，被服务器拒绝，能挖到的Share，但是很难产生块。 希望这些数据能帮助到更多的P2POOL矿工， 使用正确的难度选择。 来自中国的P2POOL爱好者。 百度在线翻译 Please use the correct difficulty. P2POOL, this 15 days the efficiency is very low, Reason: the Chinese miners about 1.5PH/S, using the large difficulty (+5120 or more), We amend the wrong, all currently used is about difficulty ratio 1:1. P2POOL these days and low efficiency, we apologize. But we recognize the difficulty of selecting the best: the selection and calculation of force is equal to the difficulty of mining machine. Our current ant S3+518 (+512, S3 does not display the BestShare), 1TH/S+1028, S3+518, an average of 5 seconds for a Accepted. S3+5120, most computing timeout, was rejected by the server, can dig into Share, but it is difficult to produce block. Hope that these data will help to more P2POOL miners, The use of the difficulty of choosing the right. From Chinese P2POOL lovers. Baidu online translation |
|
|
|
It sounds like your network can't handle querying all the Ants that quickly? Even if the thread count is at the lowest?
M
If it's a network saturation issue, I can add an optional 1 second delay between calls. If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time. Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh. Sound doable? M Hello Mr. M Software is fast and smooth. But it will consume large amounts of network, resulting in network congestion, can not open a web page in normally. I tested 50 ants S3, use 64 threads, display refresh one second refresh cycle 300 seconds. 1 second to 50 units will be able to check the working condition of ants, everything is normal.. If I change the refresh cycle is 100 seconds, you will find there are 4-8 sets of ants S3 displays an error. Try two threads, still error occurs. I do not know it is the core network segment VLAN switch problems, or other reasons. Test 1,000 ants S3, first pause about 5-10 seconds, check to 30 mining machine working status after an error occurs. Finally, a large area of error and not working. Network is not down, you can not browse the Web, other computer turns ants console page. I think it is a program to check the dozens of mining machine, got a job status information, but these threads still remain and mining machines to connect and not disconnected, causing network congestion. You can try your method, do a version I also have a stupid way like this Option 1, for example, 64 threads, according to the IP address has been added to check the order of 64 mining machine working condition, after get a result, if there is no machine need to restart, then end off this 60 threads, pause for a few seconds, in order to continue check mining machine operation, until checked all mining machine. Option 2: You can set the time to detect 50 mining machine (IP2-51, 300 seconds after the break, continue to check the working status of 50 mining machine (IP 52-102), loop executes until the examination was part mining machine. Many thanks for your hard work, you've done well, I'm here got many machines, multi-network segment. You do not have the embarrassment, you have a good technique. You and your M monitoring are great!   hello Mr. M, I have solved the problem. I try to let the computer which been installed M monitoring software using the core network switch port VLAN assignment. All problems solved, 51 seconds to scan 1,200 ants mining machine. One second refresh time.Refresh cycle time is 1000s. I guess it should be out in a soft routing firewall, the packet may be too large to scan M monitoring, Because I saw an instant network uses 10Mbps. Firewall denied network access Mr. M, sincerely thank you, great software. best Wishs |
|
|
|
It sounds like your network can't handle querying all the Ants that quickly? Even if the thread count is at the lowest?
M
If it's a network saturation issue, I can add an optional 1 second delay between calls. If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time. Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh. Sound doable? M Hello Mr. M Software is fast and smooth. But it will consume large amounts of network, resulting in network congestion, can not open a web page in normally. I tested 50 ants S3, use 64 threads, display refresh one second refresh cycle 300 seconds. 1 second to 50 units will be able to check the working condition of ants, everything is normal.. If I change the refresh cycle is 100 seconds, you will find there are 4-8 sets of ants S3 displays an error. Try two threads, still error occurs. I do not know it is the core network segment VLAN switch problems, or other reasons. Test 1,000 ants S3, first pause about 5-10 seconds, check to 30 mining machine working status after an error occurs. Finally, a large area of error and not working. Network is not down, you can not browse the Web, other computer turns ants console page. I think it is a program to check the dozens of mining machine, got a job status information, but these threads still remain and mining machines to connect and not disconnected, causing network congestion. You can try your method, do a version I also have a stupid way like this Option 1, for example, 64 threads, according to the IP address has been added to check the order of 64 mining machine working condition, after get a result, if there is no machine need to restart, then end off this 60 threads, pause for a few seconds, in order to continue check mining machine operation, until checked all mining machine. Option 2: You can set the time to detect 50 mining machine (IP2-51, 300 seconds after the break, continue to check the working status of 50 mining machine (IP 52-102), loop executes until the examination was part mining machine. Many thanks for your hard work, you've done well, I'm here got many machines, multi-network segment. You do not have the embarrassment, you have a good technique. You and your M monitoring are great! |
|
|
|
It sounds like your network can't handle querying all the Ants that quickly? Even if the thread count is at the lowest?
M
If it's a network saturation issue, I can add an optional 1 second delay between calls. If you set it to refresh every, say, 1100 seconds, it'll continually be refreshing all 1000 ants, one at a time. Assuming all Ants respond in a timely manner, you're looking at about 17 minutes for a complete refresh. Sound doable? M Two threads of thread or 4, Yes, the error less. Still an error occurs. Since 1000 the ants, the impact is still very large. Your method can try. Because the translator is not, I can Google translate, Etc. translator came, I asked him to re-translate once. |
|
|
|
P2POOL池 矿机加难度方法 P2POOL池，这两天测试了新的难度玩法，蚂蚁S3，使用+5120难度，并没有什么影响，反而S值很好，而且蚂蚁S3不显示BestShare的问题也得到了解决，现在显示了。这样的好处是不但不影响任何，反而节约了网络消耗，还提高了S效率，我个人认为也是有效减少P2POOL池全网DOA的一个方法。 暂时定义+难度的方法为： 蚂蚁S3 +5120 蚂蚁S1 +1280 龙矿1T +10240 龙矿1.5T +15360 我个人今天开始测试蚂蚁S3+10240，明天开始测试100T池不加难度（实际难度大概在1万-10万）。 下面是我的S3测试图 非常抱歉，我的英文不好，只能中文 + 谷歌翻译。 P2POOL pool plus the difficulty of mining machine method P2POOL pool, this two-day test of the new gameplay difficulty, ants S3, use +5120 difficulty, and there is no impact, but the S value is very good, but does not show BestShare S3 ant problems have been resolved, and now shows. The advantage is that not only does not affect any, but to save the network consumption, but also improve the efficiency of S, I personally think it is an effective method to reduce the whole network of DOA P2POOL pool. + Difficulty being defined methods: Ants S3 +5120 Ant S1 +1280 Long ore 1T +10240 Long ore 1.5T +15360 Personally, I started testing today ants S3 + 10240, begin testing tomorrow 100T pool without difficulty (real difficulty probably 10000--100000). Here is my S3 test chart I'm sorry, My English is very bad, only Chinese + Google translation.     目前正在测试 蚂蚁S3+10240 Currently being tested ants S3 + 10240   下面这张月图，可以清晰地看见，4台S3（1.9T）S值在0-0.03波动。 长期挖P2POOL 并没有太大的影响，尽管目前效率低。 我相信这些都是暂时的。 This month figure below, you can clearly see, four S3 (1.9T) S values fluctuate 0-0.03. Long-term dig P2POOL not have much impact, although temporarily low efficiency. I believe that these are temporary.  |
|
|
|
Here's another beta of 3.4. This contains my rewrite of the Ant scanning routine. It now uses the API to find the Ants, making it much quicker, more responsive, and allows scanning of whatever segment you enter. Note that it'll still wait up to 5 seconds for each address to respond, so you can do the math to figure out how long it will take based on how many Ants you have (or don't have). MAntMonitor34b1.zipM Mr. M Hello Identified cause. Software is fast, very smooth. However, it will consume a large amount of network. Network almost collapsed, Can not view Internet pages. I set 50 ants, use 64 threads. Display refresh one second, Refresh every 300 seconds. Only need one second you can scan all 50 mining machine. All mining machine display properly. If I use the Refresh every 100. So will see 4-8 sets of mining machinery ERROR. I try to reduce the thread, there is no effect. I tested 1,000 ants, use 64 threads. Consider the following diagram, The network is consumed, Network recovery, The network is consumed, Cycle. Pictures lot, a lot, If affects everyone browsing, I'm sorry. Google Translation           2014/9/8 19:43:58: M's Ant Monitor v3.4b1 starting 2014/9/8 19:43:58: Initiated Ant refresh 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.022:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.22:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.012:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.12:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.049:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.49:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.059:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.59:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.016:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.16:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.008:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.8:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.051:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.51:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.032:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.32:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.028:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.28:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.036:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.36:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.030:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.30:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.054:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.54:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.038:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.38:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.002:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.2:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.058:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.58:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.010:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.10:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.050:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.50:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.034:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.34:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.014:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.14:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.046:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.46:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.026:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.26:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.062:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.62:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.042:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.42:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.006:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.6:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.018:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.18:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.060:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.60:4028 2014/9/8 19:44:19: ERROR when accessing API on 192.168.001.052:80: 由于连接方在一段时间后没有正确答复或连接的主机没有反应，连接尝试失败。 192.168.1.52:4028 2014/9/8 19:44:19: ERROR when querying S3:001.012:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.049:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.059:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.016:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.008:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.051:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.032:80 (step 3): Value cannot be null. Parameter name: s 2014/9/8 19:44:19: ERROR when querying S3:001.028:80 (step 3): Value cannot be null. 2014/9/8 19:47:10: ERROR when querying S3:002.007:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.002:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.014:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.015:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.008:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.013:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.005:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:001.254:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.011:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.012:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.018:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.010:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.006:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.009:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.016:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.004:80 (step 1): Value cannot be null. Parameter name: s 2014/9/8 19:47:10: ERROR when querying S3:002.017:80 (step 1): Value cannot be null. |
|
|
|
   More on a machine malfunction These machines work properly. This problem may also be .001.002 Monitoring alone an error of the machine, Display will become normal. Google Translation |
|
|
|
V3.2b version of the test results 253 ants around 10-12 seconds to refresh No problems to found. V3.2b2,V3.2 official version of the test results I set up 24 threads, refresh time: 5-10 seconds It can not work properly, and many machines are not shown. Totally confused, half machine can not be found. Please correct this problem, the speed does not necessarily to be very fast. Stable and effective work is the best. Mr. M, thank you for your hard work always.   |
|
|
|
I'm declaring 3.2 stable enough to publish. v3.2 - Fixed the problem with not being able to save the config if you've never used it before. - Changed to query the Ants via the API on background threads. The numbers of threads is configurable. The more Ants you have, the higher you likely want this value to be. It defaults to 4. - Changed to refresh the display grid X numbers of seconds after the Ant refresh has started. This value is configurable. If you have a large number of Ants, or have slow video, you'll benefit from setting this to a larger value. It defaults to 1. - Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory. - Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters. Download link: MAntMonitor32.zipM       |
|
|
|
Here's a beta version of 3.2. The huge change to this was it was restructured to do multi-threaded polling of your Ants via the API. Things to note: - This is a beta version. Chances are good I broke something. - That said, you should be able to revert back to the prior version simply by running the older version. - This is for API users only. I'm pretty sure the web scraping piece is broken, simply because I haven't taken the time yet to redo it to work with the new code. - It has 5 threads running behind the scenes: 1 dispatch thread, and 4 worker threads. I intend to have the worker threadcount controllable in the final version. - You'll see in the Log which worker thread is checking which Ant. - My main PC is an i7. That means have 4 CPU cores with hyperthreading, so the OS sees 8 cores available. I don't know how this will respond on CPUs with less cores available. - I only have 3 Ants: 1 S1, 1 S2, and 1 S3. I can't really test how this will work with more than 3 Ants, especially not 1000. As always, feedback is most welcome. Thanks! Download link: MAntMonitor32b.zipM Beta 3.2b 253 ants scan time = 95 seconds Speed increased 3.5-4.0 times. No multi-segment scan. No test 3 digit IP (192.168.001.002 - 001.253) sorted the problem, the problem actually is not too important. 3.2b1 has not been tested Thank you been trying to work. Google Translation |
|
|
|
Hello, M M's Ant Monitor It’s very good software, for thanks your and support your hard working, my boss (Mr. Wu, P2POOL first count force 1PGwNprChx745u6XdbcHttf7Y2MAaqXhsF) has sent 1BTC to 1PA1sji28iztspKxDquwFrNjp5SksjkCHE, please check. I got it, tyvm! Currently, we have 1,000 ants S3, core switches do VLAN (currently four network segments), each network segment 253 mining machine. Automatic search does not support multi-VLAN network segment, there is a little pain, can only add IP manually, if you add 1,000 mining machine, the software refresh rate takes about 20 minutes,it is very slow….  At present our solution: use a computer to do the monitoring, using VMware made 4 XP virtual machine, a virtual machine a network monitoring. 253 machine default 300 seconds to refresh once, one second countdown began refresh mining machine working condition, this process takes four minutes to complete, after which the software restore 300 seconds countdown. We hope that the software refresh rate can be faster, and VLAN support multi-segment search. I'm working on recoding the refresh algorithm to be multi-threaded. That should speed it up quite a bit. I'll also work on revising the search routine to see if it can help you. Another registry problems, such as adding a 1000 mining machine, then after I deleted 750 mining machine.but monitoring page still shows 1000, Delete is displayed as “? ? ?”. I must remove HKEY_CURRENT_USER \ software \ mantmonitor in the registry, and then re-add the IP. A little painful.  Removing the machines from the config doesn't currently remove them from the output grid. I'll add that to the todo list. Someone also suggested having a way of removing/disabling from the output grid. I'll be adding that as well, it should make it easier to remove/disable Ants from the output. After the restart monitoring software MAntMonitor this IP order is chaos, can we order like 192.168.1.2 - 253? I see what you mean about the sorting. I'll have to think about that. Right now it's a string value, and .6 comes before .61 in strings. Thank you for your support, I'll be getting these changes out as soon as I can. It may take a few days. M I believe you Have a nice weekend! |
|
|
|
IT people want to see this network! Currently, we have 1,000 ants S3, core switches do VLAN (currently four network segments), each network segment 253 mining machine. |
|
|
|
1000? Okay, timing is everything, I was just told I might want to multithread it. Now it's obvious I do. If you can solve this problem, the boss is willing to donate. Your wallet address? 1PA1sji28iztspKxDquwFrNjp5SksjkCHE I'll see what I can do. You can only get 250 or so per subnet. How many subnets are you using?
Registry
Really a lot of trouble
Minerals can not be deleted after an error
Can you post a screenshot? A picture is worth 1000 words. M Hello, M M's Ant Monitor It’s very good software, for thanks your and support your hard working, my boss (Mr. Wu, P2POOL first count force 1PGwNprChx745u6XdbcHttf7Y2MAaqXhsF) has sent 1BTC to 1PA1sji28iztspKxDquwFrNjp5SksjkCHE, please check. Currently, we have 1,000 ants S3, core switches do VLAN (currently four network segments), each network segment 253 mining machine. Automatic search does not support multi-VLAN network segment, there is a little pain, can only add IP manually, if you add 1,000 mining machine, the software refresh rate takes about 20 minutes,it is very slow…. At present our solution: use a computer to do the monitoring, using VMware made 4 XP virtual machine, a virtual machine a network monitoring. 253 machine default 300 seconds to refresh once, one second countdown began refresh mining machine working condition, this process takes four minutes to complete, after which the software restore 300 seconds countdown. We hope that the software refresh rate can be faster, and VLAN support multi-segment search. Another registry problems, such as adding a 1000 mining machine, then after I deleted 750 mining machine.but monitoring page still shows 1000, Delete is displayed as “? ? ?”. I must remove HKEY_CURRENT_USER \ software \ mantmonitor in the registry, and then re-add the IP. A little painful. After the restart monitoring software MAntMonitor this IP order is chaos, can we order like 192.168.1.2 - 253?   |
|
|
|
Hello Mr. M May I ask how many support the mining machine? I tried a bit, P2POOL first operator force, 1000 mining machine,  OMG, the software is very slow reaction, there is no way to work properly. If you can solve this problem, the boss is willing to donate. Your wallet address? 1PA1sji28iztspKxDquwFrNjp5SksjkCHE Registry Really a lot of trouble Minerals can not be deleted after an error Sorry Google Translation |
|
|
|
   Eligius 9.5PH/S P2pool 2.40PH/S Very nice |
|
|
|
I also |
|
|
|
|
