Jump to content
  • 0

failed to determine binary type: 193


Question

Posted

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.

  • Answers 33
  • Created
  • Last Reply

Top Posters For This Question

Recommended Posts

  • 0
Posted

If you have configured the SkyProc jar to be run via the 'Gears' icon I would guess you may have left off the arguments to call the correct Java executable.

 

Easiest way to fix that is to delete that executable from the drop down list and then open the 'Data' tab on the right-hand pane.

Navigate to the folder that contains the SkyProc jar and right-click and select "Add as executable". That will fill out the details correctly.

 

These are the details from my setup.

 

Binary:

C:\Program Files (x86)\Java\jre7\bin\javaw.exe

Start in:

C:\Program Files (x86)\Mod Organizer\mods\ReProccer - Automated SkyRe patch generator\SkyProc Patchers\T3nd0_ReProccer

Arguments:

-jar "C:\Program Files (x86)\Mod Organizer\mods\ReProccer - Automated SkyRe patch generator\SkyProc Patchers\T3nd0_ReProccer\ReProccer.jar" -noboss

Take note the Java version called here is version 7 and is 32bit. Any version of Java may be called, ie. jre6, jre7 or jre8. As long as they are 32bit.

  • 0
Posted

Are you 100% certain you are running a 32bit version of Java and you are not experiencing any Windows UAC difficulties.

 

As far as I can determine "error 193" can be read as saying "I don't know what to do with this type of file. Help."

That means your Java setup isn't running *.jar files correctly or Windows is incorrectly trying to do something else with those filetypes. Either way the fault is due to an incorrect setup outside of MO.

 

Try and run that file from outside MO and see what the result is. All the MO executables dialog does is parse the commands in the same manner as you would from explorer.

Double-clicking on any *.jar file on your system should envoke the Java runtime if it is correctly installed.

  • 0
Posted

Windows places restrictions on certain folders that it has control over. Ostensibly it was to "protect" users from placing rogue programs on their computers that might stuff them up. So folders like 'Program Files' 'Windows' etc. are protected and when you try to run executables, such as Java, on files that are under that 'protection' Windows doesn't allow it and throws errors at you.

That's why you will often see recommendations to install games and game tools outside of those folders.

  • 0
Posted

Yes. I updated several mods.  I DL'd PerMa.  That is all.  I was running the patcher for Perma just fine.  After updating the mods, I tried to re-run the patches for PerMa, ASIS, AV, and DSR.  Now, when I click run, it locks, then unlocks, refreshes and gives be the error stated above.  


Every other program run from MO, ie FNIS, Wrye Bash, TESVEdit, LOOT, all work fine.  I can run Skyrim skse loader fine.  ENB works just fine.  The only thing that isn't working is the SkyProc patchers.  This leads me to believe that I have done something detrimental with JAVA.  The problem is, I can not figure out what.  

 

TBH, I'm no computer expert.  Everything I have learned, I have learned from countless readme's and youtube videos, google searches and boards like this.  This just has me very frustrated and confused because there are not many resources, other than friendly posters like yourself, that are able to help me solve my problem.

 

I really do appreciate the feedback.

  • 0
Posted

Okay. Software just doesn't stop working for no reason so there must be a reason for this behaviour.

All those mods simply contain jar files that don't, in themselves do anything. ie. they are simply scripts that need the Java executable to run.

 

Your OP says you updated your Java. Why? Did your previous version not work with PerMa?

If not, why not? Were you instructed in the documentation to use a specific version? T3nd0 does make mention of a batch file he has prepared that runs PerMa with a greater heapspace. Have you tried to run that bat?

 

If ALL your other 'proccer' type mods are no longer working then it is most likely an error in your latest Java update.

 

You said you're only 99% sure the version you have now is 32bit. It only needs that 1% to show you have 64bit to completely screw with your mind.  :O_o:

 

Regardless of which version you installed/updated there can be both 32 and 64bit versions installed on the same machine. This should mean ALL the existing links to the other 'proccer' mods are still looking at the correct version. Assuming you have actually run these mods before.

When you look in 'Control Panel - Uninstall', the names of your Java installations will say if any are 64bit. If there is no mention then thety are 32bit.

 

If you do a system wide search for "javaw.exe" you should see all the versions installed. Make sure your MO paths are pointing to the correct one.

 

Lastly, it wouldn't hurt if you do a hard reset shutdown of your computer. It might (though I doubt it) be a case of Java still having something in memory and it won't look at anything else until the previous instance is cleared.

 

Just keep telling yourself: "computers are not conspiring against me, I will find the answer."

  • 0
Posted

LOL, I turned it off and back on.  I appreciate the brevity.  I completely understand that this is (as it always is) a case of user error.  I am certainly no stranger to it...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.