[derk]

Failed to bind to virtual machine because of a Exception
java.lang.Exception: Failed to bind to the virtual machine.
    at nul.IIIiIIiiIIiI.this(kbc:269)
    at nul.iiiiiIiIiiiI.run(ghc:96)
Caused by: java.rmi.ConnectException: Connection refused to host: 192.168.2.3; nested exception is:
    java.net.ConnectException: Connection refused: connect
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
    at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
    at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
    at nul.iIiiIIiIiIII.this(vic:258)
    at nul.IIIiIIiiIIiI.this(kbc:207)
    ... 1 more
Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.DualStackPlainSocketImpl.connect0(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:589)
    at java.net.Socket.connect(Socket.java:538)
    at java.net.Socket.<init>(Socket.java:434)
    at java.net.Socket.<init>(Socket.java:211)
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
    ... 7 more

Might be related to another thing:

That happens in the client. Consistently.

 

[qosmiof2]

Failed to bind to virtual machine because of a Exception
java.lang.Exception: Failed to bind to the virtual machine.
    at nul.IIIiIIiiIIiI.this(kbc:269)
    at nul.iiiiiIiIiiiI.run(ghc:96)
Caused by: java.rmi.ConnectException: Connection refused to host: 192.168.2.3; nested exception is:
    java.net.ConnectException: Connection refused: connect
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:619)
    at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)
    at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)
    at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:342)
    at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
    at nul.iIiiIIiIiIII.this(vic:258)
    at nul.IIIiIIiiIIiI.this(kbc:207)
    ... 1 more
Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.DualStackPlainSocketImpl.connect0(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:79)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:589)
    at java.net.Socket.connect(Socket.java:538)
    at java.net.Socket.<init>(Socket.java:434)
    at java.net.Socket.<init>(Socket.java:211)
    at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
    at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
    at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
    ... 7 more

Might be related to another thing:

That happens in the client. Consistently.

WEllll yall voted NO to advertising so it makes sense XD

 

[cloud]

Stop trying to run the game with a 64 bit JRE, jagexappletviewer.jar doesn't like that on windows.

 

[aidden]

Stop trying to run the game with a 64 bit JRE, jagexappletviewer.jar doesn't like that on windows.

Adding to that, spectre needs to run in 32bit as well because it won't be able to attach to the game client if it's in 64bit.

 

[savior]

@Cloud how do you plan to handle this for end users?

 

[arbiter]

@Cloud how do you plan to handle this for end users?

Official client's embedded JRE is 32bit. On our end we will either figure out a way to support 64bit or force 32bit.

 

[cloud]

@Cloud how do you plan to handle this for end users?

Most likely by forcing the user to use a compatible JRE when Spectre is ran.

 

[arbiter]

Resolving due to thread age. Please re-post if the bug still exists.