No luck trying to update 2050

[SolarWind]

  Trying to update the latest firmware - 2050 and all I'm getting on my trusty laptop running XP that I have used for years to do this is "not a valid win 32 application". Have deleted the software, downloaded a clean copy and tried again but same error over and over. I can't update the Classic 150.

To compound the problem when it was working earlier I inadvertently updated the 150 with the 200 code which has incapacitated the Classic 150, won't work, just says wrong code. But I can't run the updater to install the right code. And it's not because of the wrong code in the Classic because the Classic isn't even plugged in to the laptop when I get the "not a valid win 32 application" error.

Ideas? Thanks!

[SolarWind]

ANYBODY? Can't even get Midnite to respond by email except to say someone else will respond.

[Resthome]

ANYBODY? Can't even get Midnite to respond by email except to say someone else will respond.

I think Zoneblue posted else where he got this error with XP.  Maybe try rolling n
Back to previous firmware, just an idea. No longer running XP here..

[Halfcrazy]

Unfortunately I do not have XP here but they are telling me nothing really changed. boB suggested trying this update here as he made it use some different stuff in the GUI

http://fusion.midnitesolar.com/MidNiteSolarUpdate_2054_8-11-2015_v4.91.exe

I am going to pull 2050 until we sort this out and if this updater doesn't do it send me an email I will get you a new classic and a call tag.

Ryan

[zoneblue]

I got that exact same error on my old laptop, the one ive alwasy used to do classic firmwares. The one that never missed a beat. Except 2050 doesnt like it. YOu ought tobe able to overwrite the correct firmware but youll need another computer.

For most people, id say hold off on 2050 until the next one.

[Westbranch]

Anyone with success on W7?

[boB]

Please try this...

Explore over to the C:\Midnitesolar directory and run   GUI_VS6.exe

If you have extensions display turned off in your windows then it will show up
as just   GUI_VS6

The newest update software should have  GUI_VS6.exe   moved over to GUI.exe but maybe
your computer is running a semi-newer version that "may" be 32 bit....  But I thought it was
compiled for 32 bit.  the VS6 one is definitely a valid  32 bit program.


BTW, there are a few .exe files that could be generating this error.  PLEASE give us the file or
program that is giving you the error.  I can't troubleshoot this without all of the information or
what exactly is the problem.

I was assuming that it was the GUI.exe program but now I am not sure which one it is.

Please report back on this ASAP if you can.
Thanks
boB

[Resthome]

Please try this...

Explore over to the C:\Midnitesolar directory and run   GUI_VS6.exe

If you have extensions display turned off in your windows then it will show up
as just   GUI_VS6

The newest update software should have  GUI_VS6.exe   moved over to GUI.exe but maybe
your computer is running a semi-newer version that "may" be 32 bit....  But I thought it was
compiled for 32 bit.  the VS6 one is definitely a valid  32 bit program.

Please report back on this ASAP if you can.
Thanks
boB

I show GUI.EXE, GUI_VS6.EXE and GUI_Older.EXE and under Win10 64bit they all execute and run.

This is the 2050 download.

[boB]

Please try this...

Explore over to the C:\Midnitesolar directory and run   GUI_VS6.exe

If you have extensions display turned off in your windows then it will show up
as just   GUI_VS6

The newest update software should have  GUI_VS6.exe   moved over to GUI.exe but maybe
your computer is running a semi-newer version that "may" be 32 bit....  But I thought it was
compiled for 32 bit.  the VS6 one is definitely a valid  32 bit program.

Please report back on this ASAP if you can.
Thanks
boB

I show GUI.EXE, GUI_VS6.EXE and GUI_Older.EXE and under Win10 64bit they all execute and run.

This is the 2050 download.

OK, I just checked....  Turns out that I I made two (2) different versions that day.

One was the regular one with a semi-new  GUI.exe which is EVIDENTLY made for 64  bit.

Then I made up another installation .exe  that instead uses the original 32 bit GUI.exe and it was called...

MidNiteSolar_DIR_2050_8-5-2015_MM1_GUI-VS6

VS6 is Visual Studio 6 and this was made before 64 bit software was common place.

Now, the newer  2054  installation  .exe  file  also has the 32 bit GUI.exe in there.
I kept both GUI exe files in there just in case something like this came  up !

Anyhow, the one you guys must have downloaded was most likely the one with the 64 bit
gui.exe  program.  That makes the most sense.

The 64 bit version of GUI.exe   is  around 100 K bytes and the regular old VS6  32 bit version of GUI.exe is twice that
or around 208 K bytes in size.

So, there you go !

I would just go with the 2054 version that Ryan posted the link to a little while ago.
It has a couple of other discrepancies resolved also.

boB

[SolarWind]

Sorry, been on the job, no time to play with this. I did get the system to operate after rolling back to 1933/23 version that I had on my computer. For now I'll stay with that until I can spend the time trying the 2054 version. Thanks for everyone's comments and effort!