failed to determine binary type: 193

[vaderdog]

I get the above error when I try to run any of the SkyProc patchers through MO.  I have researched and posted this on several sites looking for answers and have come up dry.

 

I have updated my Java. i have followed the STEP WIKI on setting up the patchers.

 

What happens when I click run on SUM (or any other SkyProc patcher) is the following:

      MO locks, per usual.  Then after a few seconds, it unlocks and refreshes with the light bulb followed            by "failed to determine binary type: 193"

 

Thanks for reading.

[GSDFan]

Pardon my butting in here, have you tried to double click a jar file outside of MO to see what happens?

[Tannin]

Not sure what's wrong in detail, but as others have pointed out the error means: What you have entered in the "Binary" field is not an executable (.exe).

It doesn't matter what's in your "Starts in" or "Arguments" field, that won't cause this error, only the "Binary" field is relevant.

You can only have 32-bit .exe files in that field, not .jar, not .bat not .cmd or .py or ...

[vaderdog]

I am getting "error code: 1603" now when I install Java.  I know that computers are not out to get me.  But it feels like they are. I really hate the thought of playing Skyrim without ASIS, DSR, etc...

[Nozzer66]

1603 usually means something's either missing, or there's old Java files still hanging around that are causing issues.

 

My Google-fu finds this page here: https://social.technet.microsoft.com/Forums/windows/en-US/78ac199b-316b-4fbc-8b2b-2c90e5425ff0/java-install-errors

 

It mentions both running the java uninstall tool to clean up old java installations, and also that there's possibly a windows update that may be causing issues.

Edited November 16, 2014 by Nozzer66

[vaderdog]

Tried the solutions on that page.  The Java uninstall tool won't work.  Since this is most definitely out of my realm of expertise, is there a company that I could hire and someone would recommend to fix my issues? Remotely would be my preference.  This is day three of my head scratching and at this point, I feel like I have probably done more to worsen my issues than rectify them.

[hishutup]

hmmm, did you redownload the archives and then reinstall them.

Delete and re-add them to the executable list in MO

try it

 

Do you do anything to the .jar files after downloading them?

[vaderdog]

I did a system restore to 10 days ago.  Reinstalled java...  Wala (sp?) It appears to be working...  Ask Talos for my forgiveness! Thanks for all the support!

[Nozzer66]

Voila, actually. ;)

 

So it would seem something between 10 days ago and now screwed you over.

 

Strange. Keep an eye on Windows updates and virus checker updates. If it happened once, it may well do so again. :)

[vaderdog]

Really, thanks a lot for the input.  You have no idea how excited I am to see AV, ASIS, DSR, and the all new Patchus Maximus working. 

[GrantSP]

Ahh, Windows. Driving people insane since 1985.

[Nozzer66]

Glad to at least try and help, Vaderdog. And Grant, you get a plus for that, as well. I needed a good chuckle after today.

[Leerox]

Everyone! I am ALSO having this issue, and ALL I have done is download and try to install Perkus Maximus and SkyRe to make them compatible. ONE DAY, when I try to run ANY SkyProc Patchers, NONE OF THEM WORKED! I was so infuriated, I tried editing all their directories and NONE of what I have tried is working. My directories are setup, and a WINDOWS Restore is OUT OF QUESTION because I cannot risk losing my sensitive files. Even if all Windows Restore does is change windows files.

 

Help!

[Nozzer66]

If you're using the Version 16 build of Mod Organizer, that's why the Skyprocs aren't working. It's mentioned elsewhere on the forum. Go back to version 14 of Mod Organizer for now.

[Leerox]

If you're using the Version 16 build of Mod Organizer, that's why the Skyprocs aren't working. It's mentioned elsewhere on the forum. Go back to version 14 of Mod Organizer for now.

Can I use Version 15?

[phazer11]

I do not believe so I think that it has the same issue. In fact .16 was released to fix another bug in .15 but did not address the SkyProc issue. Use .14