At the moment the best way to do this would be to set up the one miner that wants to be run at a lower clock in the BFG Miner window with the manual flag -S /dev/cu.pathtodevice and to start that window before start…
That looked normal a few hours ago - to be honest you're better off at a more traditional pool at that speed, try http://FabulousPanda.triplemining.com/
Thanks for your report, can you please open the Console app in Utilities folder and let me know whether there are a bunch of errors from MacMiner in there?
I have discovered a bug that causes MobileMiner to fail if your computer name has a dash in it and will fix this for 1.5.10 - sorry to everyone experiencing this issue!
Thanks for the report, I'm planning to put the actions that go on then on to another thread so it should at least not crash the whole app. Is this 1.5.8 that's caused the problem for you? I'll put in an easier path to reset too.
ah. message me the contents of your bitcoin.conf if you don't mind and I'll make sure that's all good - I've got to get some sleep though it's 5:20am here :S I'll get back to you soon though!
did you remove the pools from the conf file or the manual flags? I'd keep them in the conf file. Personally I'd have all of it in the conf file so you can just leave manual flags blank. What you're describing may well be working, I'm actually not su…
Are you mining at the command line or in MacMiner? I assume MacMiner as you're not linking the conf file. First off either way you shouldn't be escaping new lines with \ with your manual flags - just one long string of commands separated by a space …
can you post your bfgminer.conf with any sensitive information blanked out please? unexpected new line means the file isn't strictly conforming to JSON and it can't parse it, and the unexpected command line arguments is usually something in the manu…