akiko Posted January 17, 2006 Posted January 17, 2006 So whats new with e-global? What does the new l2launcher.exe do? Walker wont work! :( Does anyone have a clue about it? :cry: Quote
akiko Posted January 18, 2006 Author Posted January 18, 2006 U can find it here--->http://sourceforge.net/project/showfiles.php?group_id=156903 its called la2.gr-patch.10.rar Quote
theone Posted January 18, 2006 Posted January 18, 2006 it just check the files, and update it if necesary... it guess it also patch the memory to change the token (cuz engine.dll seems to be un-encrypted, i didn't looked at it, but the file size looks like the original) Reading the data with winhex, i got: - protocol is 530 - token is 5B3B272E5D36363131313D3D2D252640215E2B5D For in-game walker just hex-edit the original token at engine.dll with this token... i guess it should be enoght. PS: i'm too lazy to make an account :P, but it should connect with this token, and a walker that use C3 (530) data (i tested with 10.5.3, so 10.4.9 should works too) Quote
akiko Posted January 18, 2006 Author Posted January 18, 2006 I tried ur token with walker 10.4.9 and it works! Quote
Maxtor Posted January 19, 2006 Posted January 19, 2006 it just check the files' date=' and update it if necesary... it guess it also patch the memory to change the token (cuz engine.dll seems to be un-encrypted, i didn't looked at it, but the file size looks like the original) Reading the data with winhex, i got: - protocol is 530 - token is 5B3B272E5D36363131313D3D2D252640215E2B5D For in-game walker just hex-edit the original token at engine.dll with this token... i guess it should be enoght. PS: i'm too lazy to make an account :P, but it should connect with this token, and a walker that use C3 (530) data (i tested with 10.5.3, so 10.4.9 should works too)[/quote'] did you read with winhex L2Launch.exe? or engine.dll? Quote
theone Posted January 19, 2006 Posted January 19, 2006 I didn't bother opening engine.dll with hex editor, I just read the private memory of the engine.dll... just like the method you posted with hexprobe... nothing new... :P ... I guees that launcher modifies the token in memory, just like the old l2player.exe posted at post pacific a long time ago. Quote
Maxtor Posted January 19, 2006 Posted January 19, 2006 i was looking for beyond with same method without result. do you have any idea? Quote
theone Posted January 19, 2006 Posted January 19, 2006 I'll download beyond C3 patch tonight and see if i can find something, is this the right page? http://beyondc3.visiems.lt/ Quote
Maxtor Posted January 19, 2006 Posted January 19, 2006 I'll download beyond C3 patch tonight and see if i can find something' date=' is this the right page? http://beyondc3.visiems.lt/[/quote'] yes Quote
akiko Posted January 19, 2006 Author Posted January 19, 2006 Seems it was teh walker version that caused all the trouble! 10.6.0 wouldnt work instead 10.4.9 works fine! Quote
akiko Posted February 1, 2006 Author Posted February 1, 2006 It seems e-global must have changed ip! There wasnt a patch out but they asked to do a full check of client and some files got modified! L2.ini l2_bak.log Running.ini l2.txt Could someone help me out?How do I find the new ip? I attached virus free the files that changed Thanx for your help If the engine.dll and l2.exe were not modified seems that the token and protocol did not change! 188_.zip Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.