Salem

Greetings all,

Does anyone know if you can run Salem on the 64bit version of Java? Trying to get it to work but it doesnt seem to want to do anything.


Thanks

Ummm nevermind, just got it working on 64bit Java!

daopa wrote:Ummm nevermind, just got it working on 64bit Java!

If you ran into issues, could you post how you fixed them? For future reference by other 64bit users.

I had both 32 bit / 64 bit java installed, I went to Program & Features for windows 8.1 in control panel and removed the 32 bit version.

I then deleted the both salem directories:

C:\Users\*****\.salem

C:\Users\*****\Salem

then clicked on the link for the custom client that I use: http://donnessime.github.io/Salem/updater.jar

and it worked!

daopa wrote:I had both 32 bit / 64 bit java installed, I went to Program & Features for windows 8.1 in control panel and removed the 32 bit version.

I then deleted the both salem directories:

C:\Users\*****\.salem

C:\Users\*****\Salem

then clicked on the link for the custom client that I use: http://donnessime.github.io/Salem/updater.jar

and it worked!

use the jnlp launcher That way, if I update the updater, you'll get those updates automatically.
That said, you really shouldn't have to uninstall the 32 bit version (in some scenarios, you do want both on your computer). For future reference, if you have a 64-bit operating system the updater will probably download the 64-bit libraries. In the case something goes wrong with 32-bit java version, right-click the jnlp or jar file you're using to launch the client, and open it with the correct java version (i.e. something like C:/Program Files/Java/jre7/bin/javaws.exe for the jnlp).

Also to note: if you have the 64-bit Java installed, you shouldn't need 32 bit installed other than for testing purposes if you're developing Java apps (in which case you're likely to have the SDK and know how to handle this kind of issue). However, there may always be certain compatibility bugs that haven't been squashed (and should be reported to Oracle by the app developers).

Just for the record, I've been using 64-bit Java forever when developing the client, so there are no intrinsic compatibility issues. There is also all the reason in the world to use 64-bit Java if possible in that it can optimize the code better given more registers and whatnot.

MagicManICT wrote:Also to note: if you have the 64-bit Java installed, you shouldn't need 32 bit installed other than for testing purposes

There is, if anything, reason to have 32-bit Java installed, if you need Java applets in a 32-bit browser. That has nothing with the client to do, however, since it isn't an applet.

loftar wrote:

MagicManICT wrote:Also to note: if you have the 64-bit Java installed, you shouldn't need 32 bit installed other than for testing purposes

There is, if anything, reason to have 32-bit Java installed, if you need Java applets in a 32-bit browser. That has nothing with the client to do, however, since it isn't an applet.

I can't really think of any good reason to allow Java in a browser.

loftar wrote:

MagicManICT wrote:Also to note: if you have the 64-bit Java installed, you shouldn't need 32 bit installed other than for testing purposes

There is, if anything, reason to have 32-bit Java installed, if you need Java applets in a 32-bit browser. That has nothing with the client to do, however, since it isn't an applet.

True, but if you're running a 64-bit OS, you shouldn't be using 32-bit browsers (other than the above mentioned software testing).

MagicManICT wrote:True, but if you're running a 64-bit OS, you shouldn't be using 32-bit browsers (other than the above mentioned software testing).

I'm not sure if this is true anymore, but Chrome, for instance, used to be available for Windows only in a 32-bit version.