Access violation at address in module 'NostaleClientX.exe'

09/22/2019 20:35 g3stapo#1
:rtfm:
Access violation at address 004D6E44 in module 'NostaleClientX.exe'.Write of address 004D6E44.
[Only registered and activated users can see links. Click Here To Register...]
What should I change in ollydbg so that the old packetlogger works?:mad:
09/23/2019 12:54 Modix#2
You have corrupted the .NOS
09/23/2019 13:37 g3stapo#3
Quote:
Originally Posted by Modix View Post
You have corrupted the .NOS
Shut your mouth if you don't understand
09/23/2019 13:39 Kravos#4
He is probably right.

No need to be inpolite Mr. GeStaPo ;)
09/23/2019 13:50 FI0w#5
Quote:
Originally Posted by Kravos View Post
He is probably right.

No need to be inpolite Mr. GeStaPo ;)
Actually yes, but no.

The problem is the outdated pattern inside of the packetlogger that throw this error.
09/23/2019 14:12 g3stapo#6
Quote:
Originally Posted by FI0w View Post
Actually yes, but no.

The problem is the outdated pattern inside of the packetlogger that throw this error.
even you don't know

09/23/2019 15:22 szymek111#7
Maybe you have DEP enabled in your OS ?
09/23/2019 15:40 Pumba98#8
Just use a maintained Packetlogger that works with the current client?
It's useless to try to fix old packetloggers
09/23/2019 15:51 g3stapo#9
Quote:
Originally Posted by Pumba98 View Post
Just use a maintained Packetlogger that works with the current client?
It's useless to try to fix old packetloggers
not suitable:rtfm:
09/23/2019 16:15 Pumba98#10
if you know everything better, why do you open a thread?
Should be easy for you :rolleyes:
09/23/2019 23:54 g3stapo#11
Quote:
Originally Posted by Pumba98 View Post
if you know everything better, why do you open a thread?
Should be easy for you :rolleyes:
I always want to fix it when new updates come out! i like old tools...
Not use new tools!
09/24/2019 08:43 FI0w#12
Quote:
Originally Posted by g3stapo View Post
even you don't know

[Only registered and activated users can see links. Click Here To Register...]
Idk if you are just stupid or if you just doing few jokes.

The problem is that the packetlogger is outdated by pattern so he dont get a Adress or the wrong Adress that he hook that's why this error appear. Do your own packetlogger or use the current working versions.