*32

[Fidgety]

Hi all,

On occasion, I am getting crashed to desktop due to out of memory errors. I am playing Salem on a Dell laptop that is 3 or so years old. Its onboard graphic ram is nothing special.
I am not sure if it is a graphic ram problem or a general system ram problem. The system has 4gb.
I have noticed that the client was built in *32.
Are there any modded clients that can use *64 and use +3gb of system memory?

I really can't understand how this game doesn't run smoother than it does for me. Granted, my laptop is starting to age and wasn't really designed for gaming, but, I have played other mmos with much nicer 3d graphics with no problems. The last MMO I flirted with was Unchartered Waters Online, it ran on full settings with aa on. I cant even turn the shadows and lighting on in this game despite the game not even having a proper day/night cycle programmed in.
I'm not trying to pull the devs down or anything, the game is great. Just trying to see if there's anything I can do without having to rebuild my gaming rig. Pennies are low at the moment and fixing the result of a poorly overclocked machine isn't that cheap.

[Sipo]

I would say to check if you have java for 32 or 64 if that is your question.

[Fidgety]

I would say to check if you have java for 32 or 64 if that is your question.

I was asking if there were clients that ran in x64.
I know I can download java x 64 despite it being a security risk. I assumed the game client was built for x32. Are you saying downloading Java in x64 architecture will do the job? I do have java x32 installed for the aforementioned security issues.

[Sipo]

Are you saying downloading Java in x64 architecture will do the job?

Yes

[Kandarim]

why would 64 bit java be any less secure?
Also, because you ask the question i'm pretty sure you do not know how Java works: java is not 'compiled' for any specific OS or memory bit-depth. FYI, I compile my custom client on a 64 bit linux box, and it doesn't stop people on 32 bit windows to run it.

Your issue is probably the on-board graphics card. You might want to have a look at UserNM's 1x1 tiles or Judaism's Miny pack. They worked wonders on my old laptop.

[Fidgety]

why would 64 bit java be any less secure?
Also, because you ask the question i'm pretty sure you do not know how Java works: java is not 'compiled' for any specific OS or memory bit-depth. FYI, I compile my custom client on a 64 bit linux box, and it doesn't stop people on 32 bit windows to run it.

Your issue is probably the on-board graphics card. You might want to have a look at UserNM's 1x1 tiles or Judaism's Miny pack. They worked wonders on my old laptop.

http://security.stackexchange.com/questions/57646/why-do-i-hear-about-so-many-java-insecurities-are-other-languages-more-secure

That was near the top of a quick search. You will find much more if you are interested.
The last time I went to get java when a program had a dependancy for it, albeit, it was a good time ago, the java website itself warned me of security risks involved with x64 and asked me to consider choosing x32. Maybe it has changed since, I don't know.

Even firefox is warning me...

So, back to what I was saying . . .

Because java.exe is running in x32 process it will not have access to any ram over 3gb, is it possible that that is causing the out of memory errors?

[Kandarim]

it will not have access to RAM over 4G*.
All of the things you stated point towards java vulnerabilities in general rather than only for 64 bit, which I agree with. However for something like a game client I also agree that it is a very solid choice.

on-topic: no, it won't help. Both custom clients limit the memory available to 1.5G anyway, as does the default client IIRC (although its limit might be different, 1G or 2G, but I doubt it's over 4G).

[Fidgety]

it will not have access to RAM over 4G*.
All of the things you stated point towards java vulnerabilities in general rather than only for 64 bit, which I agree with. However for something like a game client I also agree that it is a very solid choice.

on-topic: no, it won't help. Both custom clients limit the memory available to 1.5G anyway, as does the default client IIRC (although its limit might be different, 1G or 2G, but I doubt it's over 4G).

Ok then thanks.