[junaid]

Speaking to someone on chat, it seems it may be a connection issue? However I have no idea, here is the log when I try to run a script:

[Debug] Java Home: c:\program files (x86)\runemate\jre
[Debug] Java Version: 8u121 x86 (Oracle Corporation)
[Debug] Maximum Heap Size: 743MB
[Debug] RuneMate Version: 2.84.6
[Debug] Operating System: Windows 10 x64
java.lang.InternalError: instrument library is missing in target VM
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(jga:80)
at nul.iIiIiIiiiiiiI.this(muc:123)
at nul.IIIiIIiiiIIii.run(ixc:189)
Caused by: com.sun.tools.attach.AgentLoadException: Failed to load agent library
at sun.tools.attach.WindowsVirtualMachine.execute(oca:114)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(jga:10)
at sun.tools.attach.HotSpotVirtualMachine.loadAgentLibrary(jga:115)
at sun.tools.attach.HotSpotVirtualMachine.loadAgent(jga:54)
... 2 more

 

[blisterz]

It can't find your java library.

"java.lang.InternalError: instrument library is missing in target VM"

Make sure you have the correct java installed.

 

[junaid]

It can't find your java library.

"java.lang.InternalError: instrument library is missing in target VM"

Make sure you have the correct java installed.

Best bet to uninstall java and let runemate installer install it?

 

[blisterz]

Best bet to uninstall java and let runemate installer install it?

I did not know it would do that. If it does, then yes. Otherwise try to install both the 32 and 64 bit versions of java.

Possible try to uninstall runemate and reinstall it.

 

[junaid]

I did not know it would do that. If it does, then yes. Otherwise try to install both the 32 and 64 bit versions of java.

Possible try to uninstall runemate and reinstall it.

Done both, still have the same problem

 

[jojo]

if you're on java 10 switch to java 8

 

[junaid]

if you're on java 10 switch to java 8

On java 8 too :\
 
@Negrita (please say what you did here)

So negrita did some stuff, and then I did some stuff

What I did was find the OSRS launcher, which was in my E drive, copy all the runescape related files and folders to the exact same location but in the C drive, and then edited the target and start in location of the launcher via right click properties.

 

[negrita]

Went on TV on his computer

• Removed all instances (RM, Runescape, Java)
• Installed Java (SDK) to C-drive
• Installed the Java Runescape (defaulted to E-drive, no option to change it)
• We logged in both to OSRS and RS3 to ensure all cache files were downloaded
• Installed Runemate (C:\...\Program files (x86)\RuneMate)
• Verified paths: noticed that RS installed to E-drive. I couldn't find how to make it install to C-drive without f****ing too much with his settings. So I just copy and pasted the jagex launcher files (E:\users\myUser\jagexcache to C:\...)
• Started a RS3 client instance from C-drive jagexlauncher (via command line) (not sure how to start OSRS via cmd)
• RuneMate still couldn't bind to that RS3 instance from C-drive
• As last resort, turned off Firewall, ran everything as Admin but that didn't change anything.

Only difference between my personal setup and his is the E-drive. So I'm thinking that's the issue, but didn't know how to change it. Looking at the forum history on this error, multiple people have/had it. But I couldn't find a solution posted anywhere. Might be worth for someone more experienced to look into ( @American Express ). I looked for quite a bit and saw nothing wrong with his setup.

 

[junaid]

Went on TV on his computer

• Removed all instances (RM, Runescape, Java)
• Installed Java (SDK) to C-drive
• Installed the Java Runescape (defaulted to E-drive, no option to change it)
• We logged in both to OSRS and RS3 to ensure all cache files were downloaded
• Installed Runemate (C:\...\Program files (x86)\RuneMate)
• Verified paths: noticed that RS installed to E-drive. I couldn't find how to make it install to C-drive without f****ing too much with his settings. So I just copy and pasted the jagex launcher files (E:\users\myUser\jagexcache to C:\...)
• Started a RS3 client instance from C-drive jagexlauncher (via command line) (not sure how to start OSRS via cmd)
• RuneMate still couldn't bind to that RS3 instance from C-drive
• As last resort, turned off Firewall, ran everything as Admin but that didn't change anything.

Only difference between my personal setup and his is the E-drive. So I'm thinking that's the issue, but didn't know how to change it. Looking at the forum history on this error, multiple people have/had it. But I couldn't find a solution posted anywhere. Might be worth for someone more experienced to look into ( @American Express ). I looked for quite a bit and saw nothing wrong with his setup.

Its fixed now, what I did was find the OSRS launcher, which was in my E drive, copy all the runescape related files and folders to the exact same location but in the C drive, and then edited the target and start in location of the launcher via right click properties

 

[negrita]

Check if C:\users\<myuser>\jagexcache exists, if not try Request - Look into this error

 

[junaid]

Check if C:\users\<myuser>\jagexcache exists, if not try Request - Look into this error

I created it (by copying over from E drive)

 

[cloud]

It's now resolved properly