Salem

Hi,
Salem stuck to me, already pulled the drivers, Java 6, I have no idea what else I can do?

  I have a WinXP system, 1.5 GB RAM, Intel Pentium Dual Intel Express Chipset Family 965th

Thanks for help

Well, after 'cleaning' Java appears to me this error:

java.io.FileNotFoundException: C:\Documents and Settings\Frytka\Dane aplikacji\Sun\Java\Deployment\cache\6.0\35\5192be3-25be2858 (Nie można odnaleźć określonego pliku)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(Unknown Source)
at java.io.FileInputStream.<init>(Unknown Source)
at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Looks like you have a driver issue. I understand that there are no drivers compatible with the version of OpenGL used for Salem available on WinXP for the Intel 965 graphics processor. Details can be found through this thread: viewtopic.php?f=10&t=96

As far as why you're getting the "file not found" exception, make sure that Salem downloads again by running the salem.jnlp.

Now it work. Thanks. But it hangs sometimes and i don't know why.

If you get an error report, follow up here or post in Bugs & Technicalities.

Are you using Ender's client? Or some other custom one?

As for the hanging - you simply might have not enough RAM and java starts swapping, which may cause shorte freezes. Close other applications and try to free as much RAM as possible. Restarting client every now and then might help as well. Also, using this viewtopic.php?f=11&t=2696 might have positive effect

This game has a memory leak.

With 32 vista and 4GB ram I'm lucky if I don't crash every 1 hour.

Care to show screen of your task manager with salem eating all your ram?

The default client does not crash. Java does not leak memory. Only Ender's client is having issues with Out Of Memory crashes. From seeing a few of the reports, I'm inclined to think it's an OpenGL issue, but I'm not an experienced OpenGL developer (at best I can create a screen and get a few sprites to move around), so I could be completely off base. If it is a Java issue, then it's due to the client requesting resources and not releasing them for the garbage collector to free up the heap or potentially trying to make too large of a request at once. (Again, my lack of experience here leaves me open to being very wrong.)