dzienny wrote:So, this error pops up right after you start xwom.exe?
matelot2 wrote:27 oct 2200 london time. is wom still down and even with the xwom fix is everybody getting
'you failed to connect to server. its probably down!'
I have been getting this for a few days now trying various ways to connect without success.
Thanks,
Bob.
$ ./wom.bat
./wom.bat: line 1: @echo: command not found
start: invalid option: -j
Try `start --help' for more information.
$ java -version
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-0ubuntu1~12.04.1)
OpenJDK Client VM (build 20.0-b12, mixed mode, sharing)
$ chmod 755 jre-6u37-linux-i586.bin
$ sudo ./jre-6u37-linux-i586.bin
@echo off
start javaw -cp /home/alden/jre1.6.0_37 -jar -Dsun.java2d.noddraw=true -Dsun.awt.noerasebackground=true -Dsun.java2d.d3d=false -Dsun.java2d.opengl=false -Dsun.java2d.pmoffscreen=false lib/Starter.jar
$ ./wom.bat
./wom.bat: line 1: @echo: command not found
start: invalid option: -c
Try `start --help' for more information.
DaimyoKirby wrote:And this was the result:
- Code: Select all
$ ./wom.bat
./wom.bat: line 1: @echo: command not found
start: invalid option: -c
Try `start --help' for more information.
So my question is this: Is there a way to actually get this XWoM fix to work on Linux, or has classic reached the end of the line for Linux users?
Users browsing this forum: No registered users and 17 guests