Thanks - I'll add some additional logging to this that should sort out what is causing the problem. cgminer or bfgminer doesn't like the arguments being passed to it is my guess.

Thanks! Brain fart because I do this too! 

I'm sorry I cannot say at this point. I'm going to add some code that will log what MultiMiner is launching and with what arguments.

Basically, cgminer or bfgminer (whichever you are using) is launching and then closing a few seconds later for some reason. I usually see this when I stop & start cgminer when using a USB device and cgminer hasn't completely released the USB device. That's actually why that "retry" code was put in there specifically.

I'll try to get you something you can use soon that logs the processes and arguments that MultiMiner is using.

Do you have the mobile development skills to make a mobile app that can communicate with this app on the same subnet to get stats and perform basic management?

...would be epic :-)

I would just love the ability to monitor my rigs remotely some how.  Just basics like temps, accepted, rejected and what pool they are currently mining on I could care less if I have any remote control over my rigs.  Anything like that would be amazing.


EDIT:  I downloaded the unofficial version and checked out those eater eggs under settings.  I am very very excited to see where that's going.  If it is going in the direction I think it is it will be epic nwolls.  Thanks again for this amazing tool

Hi there,

Thank you for your work. I found the error. I had the second pool with zero arguments in name settings. Now it works.

Nice - glad you got it sorted and thanks for leaving the solution here so others may find it. I've noted your issue and will see if it's something I can handle more gracefully in the future.

I was thinking like different columns that can be selected.  For example, Icarus devices have no intensity, so being able to remove that column and use the screen estate for whatever pool you're using, etc.

Hey nwolls a few issues for me here,

I have noticed that over the last week or so every few days a new error pops up and I lose all mining until you release a new version and after completely removing the old version and reinstalling the new I finally can get back to mining.


This is the newest error:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.InvalidCastException: Null object cannot be converted to a value type.
   at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
   at Newtonsoft.Json.Linq.Extensions.Convert[T,U](T token)
   at MultiMiner.Coinchoose.Api.CoinInformation.PopulateFromJson(JToken jToken) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Coinchoose.Api\CoinInformation.cs:line 42
   at MultiMiner.Coinchoose.Api.ApiContext.GetCoinInformation(String userAgent) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Coinchoose.Api\ApiContext.cs:line 23
   at MultiMiner.Win.MainForm.RefreshCoinStats() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 839
   at MultiMiner.Win.MainForm.MainForm_Load(Object sender, EventArgs e) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 53
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I absolutely love the program but sadly it seems to be getting less and less stable as it progresses but it could also be due to where it gathers info from.  Any ideas on this new error I got?  Or is this one due to coinchoose and not with multiminer at all?  It wouldn't surprise me if these latest errors are due to it as the site has been dropping coins left and right over the last week.

Thanks for the report. This one is fixed for the next drop which should be soon. This was due to Bytecoin coming over with a blank value for Minimum Block Time.

Also, if you are on that unofficial build up above it's definitely less stable. I should be releasing something soon with a nice round of fixes and improvements.