Closed hp8wvvvgnj6asjm7 closed 1 week ago
lol, whose is it then?
lol, whose is it then?
unclear, some guy called afirenice who gave it to a friend, who gave it to a friend, who gave it to me.
lol, whose is it then?
unclear, some guy called afirenice who gave it to a friend, who gave it to a friend, who gave it to me.
LOL... you can create you're own dll and inject via dll-syringe again
lol, whose is it then?
unclear, some guy called afirenice who gave it to a friend, who gave it to a friend, who gave it to me.
LOL... you can create you're own dll and inject via dll-syringe again
yeah thats hard because I don't know how long the reverse engineering might take. It's many memory locations.
lol, whose is it then?
unclear, some guy called afirenice who gave it to a friend, who gave it to a friend, who gave it to me.
LOL... you can create you're own dll and inject via dll-syringe again
yeah thats hard because I don't know how long the reverse engineering might take. It's many memory locations.
okay...
lol, whose is it then?
unclear, some guy called afirenice who gave it to a friend, who gave it to a friend, who gave it to me.
LOL... you can create you're own dll and inject via dll-syringe again
yeah thats hard because I don't know how long the reverse engineering might take. It's many memory locations.
okay...
maybe delete the issue thx.
lol, whose is it then?
unclear, some guy called afirenice who gave it to a friend, who gave it to a friend, who gave it to me.
LOL... you can create you're own dll and inject via dll-syringe again
yeah thats hard because I don't know how long the reverse engineering might take. It's many memory locations.
okay...
maybe delete the issue thx.
you're welcome!!!
try install Windows 10, install VS 2022 Professional with All Packages and try compile dll again!!!
Originally posted by @RiritoXXL in https://github.com/OpenByteDev/dll-syringe/issues/31#issuecomment-2488421435
but it's not my dll I didn't compile it.