[POSSIBLE SOLUTION] Poseidon x WIN7

[joamil1]

Hello everyone,

This is probably not the correct section, but I would like to pass out to the dev team that a simple solution to the conflict between poseidon and win7 was found. It was tested under 32bit and 64bit OS, home premium and ultimate, with 2.0.7 openkore version, and worked fine.

Credits for the method are from user AX-278 from braziliam forum JOL. Method worked for brazilian official server, bRO.

- Run startRO.exe as administrator. Do not log in.

- Run start-poseidon as administrator. If you use more than one openkore directory, you may need to run each start-poseidon inside each directory, but ONLY one poseidon client.

- Get back do poseidon client and log (insert login and username as usual), but do not select any of the characters. STAY in the character selection screen.

- Run start.exe, start.pl or wxstart. Openkore will load and enter the server.

Until now, some reports suggests that opening a normal server client would crash the poseidon client due to that [] message. Some users were able to use an open poseidon client at the same time of a regular client (with no hexeds at all).

Any other information you devs may need and if there is interest, we'll provide, of course.

[midnytblu]

hi joamil1,

didn't the latest GameGuard update makes Poseidon *unusable* since GameGuard always reports an error (such as error 150) everytime you run the batch file?

thanks.

[joamil1]

midntyblue,

Hi there. The reported method isnt 100%. Sometimes gameguard shows that message after 10min, but in some tests it was running up to 2hours (openkore running fine, bots taking DCs and getting back normally). Users under XP or Vista were still able to use with no error message ([] or 150) - win7 is a better OS worth of these tests and reports.

Notice that we normally open start-poseidon before startRO.

This could be a good point of start ou hint/tip for whoever working on this issue.

[midnytblu]

hi joamil1,

thanks. i actually have bRO installed and just tried running Poseidon and indeed there was no error on GameGuard. i have yet to try the W7 workaround though.

[joamil1]

I understand midnytblue,

Poseidon client under XP/Vista wasn't giving that error msg upon opening openkore, as far I know. The biggest issue was under win7: poseidon gets closed as soon as you opened an openkore, due to detection of XSTools.dll or other crappy messages.

Since win7 is way better than XP and Vista in memory handling and processing at general, runing kores on it seemed very interesting. This minor "workaround" proved that running our bots in win7 should be considered a priority to the dev team. Of couse we can setup a poseidon client on a XP machine and run the openkore in other machine with win7, setup a remote and go on. But not everyone has 2 pcs at hand for that.

I Suggest you instaling an win7 ultimate on a new partition or even hard drive and check out.

It may sound a newbie question, but renaming XSTools.dll both on the dll and in everywhere it is needed (poseidon code,kore code) may be worth of trying?

[kali]

AFAIK the detection is by signature, not by filename so renaming won't help.

The basic strategy from what you posted means that the client needs to run before OpenKore does. That means detection only activates during client startup, not while the client is running. Interesting.

[joamil1]

kali,

The main reason why I decided to bring this from our forum was that. This workaround is far from being fully operational, but it gives us at least a few minutes of working poseidon (sufficient for starting 10 or more bots) and with some luck and not touching anything on the PC, a few hours. With more luck, you can even start a regular RO client. So how the gameguard is exactly locating this dll is somewhat confuse.

Comparing with the normal procedure of starting the start-poseidon first and then the poseidon client - through this I only sucedeed in starting ONE kore, must be really quick - it is indeed a development.

And here in Brazil, Win7, since its official release, is the OS present in most new PCs - and everyday users with XP and Vista are updating. Kore shouldn't be obsolete whitin this new system. I guess that, along with Kore 2.1.0, Elecom and Gamefort shields, this should be one of our priorities.

Thanks for the reply considering the renaming of the .dll.

Best regards for all the team,

[kali]

Thanks

I merely distilled the essence of the technique so that others can follow up on it. I'm not saying if it's correct or not

Good work!

[joamil1]

Is there a "Win7 Poseidon Project" somewhere?

I believe that we should start updating kore core files, like those .dlls, as the server shields creators does do to their files, to make botting detection harder. At least for the official ones with gameguard.