Skip to main content
15 events
when toggle format what by license comment
Feb 3, 2018 at 20:54 comment added Lance McCarthy To address the issue where one copy of the DLL works, but another doesn't. This is likely because it was downloaded, but not "unblocked" before unzipping the folder. Windows protects itself by blocking assemblies (and other executables) that were downloaded from the internet but not signed. FIX: Before unzipping, right click on ZIP folder, select "Properties" and then click "Unblock". Now you can unzip and use the assemblies successfully.
Jan 1, 2018 at 22:31 comment added Manesc Good night, I have the same problem, did you manage to solve PIARAS or did you migrate to Claymore? Thank you!!!
Jun 28, 2017 at 8:20 comment added Nicolas Massart for Windows users perhaps, but this is probably not the majority of miners.
Jun 28, 2017 at 2:15 comment added Piaras OK - thanks to those for the attention to edit and improve the question posed and content on this matter. Yes I will try the Claymore miner - although it does seem a defeatist path given that others with a similar problem will have no choice but to abandoned ethminer?
Jun 27, 2017 at 16:28 comment added Nicolas Massart It seems that people having this problem switched to Claymore miner and fixed it.
Jun 27, 2017 at 15:08 comment added Piaras Following on from the same Q&A at ethereum.stackexchange.com/questions/18615/… "... The OS thought the Miner was a Virus and blocked it, something wrong with the compilation of the Library .dll (and copying one from elsewhere worked), to change your Mining Software" There is no indication from Norton 360 that ethminer.exe has been blocked (unless there is something I am missing?) - no error message regarding dll and I have reloaded the Mist software - any assistance from the 'been there and done that' would be much appreciated?
Jun 27, 2017 at 14:55 comment added Piaras Thanks for getting back on this matter Nicolas - I have taken a second look at one of the Q&A's namely at : ethereum.stackexchange.com/questions/18615/… Although the hardware is different to mine the resulting software issue is very similar: miner 15:47:47|main Getting work package... miner 15:47:47|main Grabbing DAG for #129656acΓǪ You will notice that the last characters of the DAG file name are corrupted - perhaps this is worthy of attention (it does not appear to have been resolved)
S Jun 27, 2017 at 14:44 history suggested Tesa CC BY-SA 3.0
corrected spelling and re-organized the post for clarity + added tags
Jun 27, 2017 at 13:31 review Suggested edits
S Jun 27, 2017 at 14:44
Jun 27, 2017 at 8:13 comment added Nicolas Massart I'm sorry, I never tried to mine with windows, but I not sure the dag name corrupted chars are saying anything about your problem, this could simply be a display problem, windows shell is not known to be the best one, especialy for special characters...
Jun 27, 2017 at 1:31 comment added Piaras OK - I can't find the original post? Can you assist with this? Or maybe peruse the above content and refer me to a site that specifically deals with this kind of issue (I am close to abandoning the whole idea of eth mining).
Jun 26, 2017 at 9:54 review Close votes
Jun 28, 2017 at 0:57
Jun 26, 2017 at 9:33 comment added Nicolas Massart Hi. Thanks for requesting an answer from me and other better qualified people thanks me. This site is managed by community, so you can't request answers from specific people. Also, if you posted this question and it was put on hold, there's no use to create it again. Simply modify your initial question and we will evaluate if it should be reopened. So I will vote for closing this question and I highly impel you to go back to the original post and edit it. Thanks.
Jun 26, 2017 at 3:02 review First posts
Jun 26, 2017 at 9:39
Jun 17, 2017 at 9:37 history asked Piaras CC BY-SA 3.0