Timeline for Comparison between orginal and modified DLL files with x64dbg
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9, 2018 at 16:33 | comment | added | pharaon | hundred lines of binaries and last line is FC: "c:\prxxx\yyy ddd" longer than "d:\xx xx xx\yyy yyy" | |
| Aug 9, 2018 at 10:18 | comment | added | blabb | quote your path like fc /b "c:\prxxx\yyy ddd" "d:\xx xx xx\yyy yyy" spaces are treated as delimiters for most of the console apps so it cant find your file that has a space in the path | |
| Aug 9, 2018 at 9:52 | comment | added | pharaon | always give me this error, FC: cannot open C:\PROGRAM - No such file or folder | |
| Aug 9, 2018 at 8:24 | comment | added | josh | The file compare gives you the file offsets of the differences in your binaries. From these you can easily get the opcode diffs in a debugger. Should be no problem at all. | |
| Aug 8, 2018 at 22:18 | comment | added | pharaon | i want to see the opcode different not the binarry | |
| Aug 8, 2018 at 12:15 | history | answered | josh | CC BY-SA 4.0 |