XP and tampering addresses

[rgerogerg]

you will get something like this:
Even I don't know what part of Visual Tool is that.

I'm sure that's what I would get.

140C25A00
14028DAC2
1440E98EA
141333004
141192650
140294882
14726C6D8
1402DD5E7
1402DD5D6
140292B20
140FB7DA8
14C93BB78
14A84EF18

In all honesty I do respect what you guys do for the community, my goal wasn't to try to "steal" an address from anyone, it was to help some people out that had a use for it. Calling me a "skid" for decompling your program to find something is a little ridiculous, especially since you just copy and pasted an address into a source somebody else posted on here.

There are lots of reasons you would decompile something, for example to make sure it isn't backdoored.

[rgerogerg]

the address from XP not afaik but this skid above use a decompiling program to extract that info from Sammy's cheat and tries to claim it as his own find...

The L at the back of the address is typical for reflector(decompiling a .net prog). and the guy's attitude is why most tend to obfuscate,pack their releases which can result in false positives and why most don't even bother anymore releasing or teaching stuff.

Obfuscation and packing will only do so much. Somebody that has the time and motivation can always unpack and deobfuscate your app.

[distiny]

But you clearly can't and they had to use a disassembler which is way above the skill level like kids as you.

Sammy's prog decompiled as you did:


Sammy's prog packed with my packer:


You'd never find it this way.
So please STAHP with the excuses you are making up right now.

[rgerogerg]

So please STAHP with the excuses you are making up right now.

What are my excuses? I haven't said anything that is even close to an excuse.

This thread can be closed anytime.

[akim14]

used addresses should be public.... and then give proper credits....

both parts are important!