now there is 4 detection points .
some reason when i change P to p or < to . , the exe dosent run
is there anyway to get around this problem , ive spent 2 days finding these 4 points
|
Full Version: Hexing Problem
ive found the detection points by hexing and nulling then scanning , over and over
now there is 4 detection points . some reason when i change P to p or < to . , the exe dosent run is there anyway to get around this problem , ive spent 2 days finding these 4 points
what do you mean with detection points? and what are you going to detect? and what an error message does the program give? because some programs stop working when they are changed, to prevent virus infections. ASProtect does it for example. Is that what you mean?
is the file size changed?
and with which Hex program u use?
first of all, if u used a packed exe, probably ur must do it again with an unpacked exe. If its not the case then u must test the 4 points u found till u get a working exe. for example if u get a point in which u found that the bytes tagged are F4 try changing them from 00 to FF and some of them will do the job. U can also use hex view if u can read asm or ollydbg. If u get hex view and put the asm instructions here im sure some of us will be able to modify it without (filtered) the exe.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
|
|