Error launching osbot. boot options are not verify

[Aap]

Anyone now how to solve this error?

get it after launching a second client(.60)

 

[Solution]

Strange, I have never actually seen this error. Are you only getting the error on that version or have you experienced it in previous versions as well?

[Aap]

Strange, I have never actually seen this error. Are you only getting the error on that version or have you experienced it in previous versions as well?

 

first time i got this. can still open .59

[Solution]

first time i got this. can still open .59

Then I'm guessing it's an issue with .60, but since I don't know when the error is thrown I have no clue how to help. Suppose you'll have to wait for somebody that does (like @Alek)

[Aap]

also got it on my vps there i cant even open 1 client.

 

is it possible that the problem  is that you cant run more then dev client?

[Solution]

also got it on my vps there i cant even open 1 client.

 

is it possible that the problem  is that you cant run more then dev client?

Could be, unsure

[Alek]

Make sure you are on Java 8+

[Joster]

I ran into this issue too didnt post about it yet. I have Java 8+ fully updated.

Only on version .60 though.. I reverted back to .59 and it is fine... also this only happened when trying to start a second mirror client.

Edited May 26, 2016 by Joster

[Aap]

Make sure you are on Java 8+

 

got java 8 fully updated, also .59 is running normal. but on my server i cant even open 1 .60 client. and on my pc i can open 1 client and getting this error while opening a second one.

[Aap]

Make sure you are on Java 8+

 

Got a other idea what might be the problem?

[Joster]

Just tried v.61.... same error when trying to launch multiple mirror modes. v.59 does not have this issue.

 

Fully up-to-date Java x32 no issue with other Java applications or v.59, tbh this error must not be on the users end, can't show you how or why, but from what I can see it's not something I have control over, must be some sort of bug or glitch in the new version.

Edited May 28, 2016 by Joster

[Aap]

Anyone a solution?

 

or a confirm that its a bug in the client or that it user end?

[Aap]

@Alek so when .59 gets updated to .61. wo are not allowed to bot anyomore ?:P

Edited May 31, 2016 by jappa

[Saiyan]

Try using .59 for now until stable is updated to .6+ as Dev builds are not meant to be used 'entirely' as regular clients. That being said though, there is nothing wrong with using dev build lol. It's probably just to do with a dev build restriction don't worry alek wont screw us over

[Aap]

Try using .59 for now until stable is updated to .6+ as Dev builds are not meant to be used 'entirely' as regular clients. That being said though, there is nothing wrong with using dev build lol. It's probably just to do with a dev build restriction don't worry alek wont screw us over

 

Need .61 since .59 dont support all some of my private scripts. something with inoteroutefinder(i am not the scripter:P )

 and always runned multiple dev client before, and never have this problem before. i am 100% sure if .61 become the new stable version. i still cant use it.