Topic: MultiMiner: Any Miner, Any Where, on Any Device (Free, Open Source, Cross Platform) - page 144. (Read 827334 times)

Also getting errors on .netframeworks

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

************** Exception Text **************
System.ArgumentException: Version string portion was too short or too long.
   at System.Version..ctor(String version)
   at MultiMiner.Win.MainForm.ThisVersionGreater(String thisVersion, String thatVersion) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 2452
   at MultiMiner.Win.MainForm.CheckForMinerUpdates(MinerBackend minerBackend) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 2475
   at MultiMiner.Win.MainForm.CheckForUpdates() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 2412
   at MultiMiner.Win.MainForm.MainForm_Load(Object sender, EventArgs e) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 149
   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)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5472 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MultiMiner.Win
    Assembly Version: 1.3.45.0
    Win32 Version: 1.3.45
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Win.exe
----------------------------------------
MultiMiner.Utility
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Utility.DLL
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MultiMiner.Engine
    Assembly Version: 1.3.45.0
    Win32 Version: 1.3.45
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Engine.DLL
----------------------------------------
MultiMiner.Xgminer
    Assembly Version: 1.3.45.0
    Win32 Version: 1.3.45
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Xgminer.DLL
----------------------------------------
MultiMiner.Coinchoose.Api
    Assembly Version: 1.3.45.0
    Win32 Version: 1.3.45
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/MultiMiner.Coinchoose.Api.DLL
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
    Assembly Version: 3.5.0.0
    Win32 Version: 3.5.30729.5420 built by: Win7SP1
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5476 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
d_uucw3d
    Assembly Version: 1.3.45.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
k2ntji2w
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
hwvhobdn
    Assembly Version: 1.3.45.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
sobiz9tf
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Newtonsoft.Json
    Assembly Version: 4.5.0.0
    Win32 Version: 5.0.6.16206
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/Newtonsoft.Json.DLL
----------------------------------------
ninh49ve
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
qnjpu4xv
    Assembly Version: 1.3.45.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
x-eip0qs
    Assembly Version: 1.3.45.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Interop.IWshRuntimeLibrary
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Users/Crazy/AppData/Local/MultiMiner/Interop.IWshRuntimeLibrary.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:


   


When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


ALso think this has cause one of my usb hubs to go caput too not 100% but testing.

I would say just go back to the last stable CGminer release that worked with it. Unless its not too hard to get it to work with the most resent CGMiner release, Then don't update anymore in the future. 

I use CGminer with Multiminer. What is the best way for me to not get these errors anymore? Will deleting CGminer from the Multimer directory break it if I use CGminer?

When I update to win8.1 I will try again.  My win8 x64 cannot even see the erupters or drivers.(It's the same pc hardware with 2 hard drives win7 & win8)

Ah gotcha - misunderstood your original question. No there are no x64 specific executables or installers. Let me know any specific errors or crash reports and I'll be happy to investigate. My mining rig is 64-bit Windows 7 and it hasn't caused me any issues that I know of.

I went back to my win7 x86 and it worked first time

Over the last 3 months win8 x64 has given me a lot of problems with compatibility.
so for now I will be continuing to run the 2 pc's (I try win 8 then (when/if) it screws up the win7 gets some more attention)

NWoolls-

Just catching up, I do use CGminer, and prefer using CGminer, but I understand that they keep changing things that are breaking this app.

Would it be better for me to revert back to a stable version of CGminer, and not update?

Maybe you downloaded the source instead of the app? Downloads are here:

http://releases.multiminerapp.com

Although for now please use this unofficial build as it works around an issue with changes to cgminer's downloads:

https://www.dropbox.com/s/q8iugo4vy2ubg3y/MultiMiner-1.3.45.zip

So if I remove cgminer from the miners directory, this error should disappear?

Getting the same error about version string too long/short as well

************** Exception Text **************
System.ArgumentException: Version string portion was too short or too long.
   at System.Version..ctor(String version)

I am starting to get .net errors on all my miners. Here is the beginning of the output:

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

************** Exception Text **************
System.ArgumentException: Version string portion was too short or too long.
   at System.Version..ctor(String version)
   at MultiMiner.Win.MainForm.ThisVersionGreater(String thisVersion, String thatVersion) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 2452
   at MultiMiner.Win.MainForm.CheckForMinerUpdates(MinerBackend minerBackend) in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 2475
   at MultiMiner.Win.MainForm.CheckForUpdates() in d:\Data\Visual Studio Projects\Personal\MultiMiner\MultiMiner.Win\MainForm.cs:line 2412
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.6407 (Win8RTMGDR.050727-6400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll

I have previously been able to run MultiMiner on Win 8.1 x64, but now I get this error:


Thx,

c32

Are there any problems installing MultiMiner on Win8 x64?

I cannot see an install file after I have the download.

Anyone being hit with an unhandled exception can download a fixed build here:

https://www.dropbox.com/s/q8iugo4vy2ubg3y/MultiMiner-1.3.45.zip

This is due to more changes to cgminer. At this point I am seriously considering dropping support for cgminer and making bfgminer the only supported engine for MultiMiner. Is there anyone currently using cgminer that cannot use bfgminer? Please let me know what sort of issues or considerations prevent you from using bfgminer if so.

bfgminer crashing again, using latest MultiMiner and latest bfgminer (3.4.0) have to downgrade to 3.2.1, as that is the only version that works on this rig(mixed scrypt and sha256)

Interesting - I'll take a look and see if any changes caused these notifications to stop working. Last I checked they were working but I only tried them with pooled mining.

Maybe my switch to make the configuration per-coin threw something off.

Edit: I'm definitely getting both share accepted and block found notifications with pooled mining. Do you get them with pooled mining but not solo?

I finally switched to solo again after the last difficulty change (about 30 hours ago), and while I've found 3 solo LTC blocks since then, the notification didn't appear to work. I have both check boxes in the coin config box checked, for notification on accepted shares, and blocks found.

No biggie at all, everything works so well, I just check on my central machine that has the wallet on it that the solo miners point to every few hours and see if I was lucky.

If you happen upon something that causes it please let me know. I've only seen it I think 4-5 times total (at least those that have been reported by users) so it seems fairly rare but something definitely causes it.

Ahh ok. Fair enough.

Ultimately yes, but I like to be able to reproduce and identify an issue before blindly handling it. Just as a matter of practice. I still haven't been able to identify why the file gets written with 0 bytes.