[Tool] PEChecksum v1.4 - modifype replacement
[Tool] PEChecksum v1.4 - modifype replacement
ModifyPE doesn't seem to work on Vista, so I made one that does. It also supports fixing checksums on x64 executables (don't know if modifype supported that or not).
Source + Binary (in "release" folder):
Download from SkyDrive
MD5: 4A0DFAD754F21466038C4C7BBD25D41B
Exit Code (errorlevel):
2 - Usage error
1 - Failed due to an error (error message written to console)
0 - Success
* Changelog:
v1.4
- Small bug fix, now returns a proper error message instead of "[6] handle is invalid."
v1.3
- Recompiled application as unicode.
v1.2:
- File modified time is now no longer changed when fixing its checksum (but last access time is not preserved).
- Fixed a compiler warning.
v1.1:
- Checksum printed on screen in hexadecimal instead of decimal
- Improved check for non-PE files.
v1.0:
- Initial release
Source + Binary (in "release" folder):
Download from SkyDrive
MD5: 4A0DFAD754F21466038C4C7BBD25D41B
Exit Code (errorlevel):
2 - Usage error
1 - Failed due to an error (error message written to console)
0 - Success
* Changelog:
v1.4
- Small bug fix, now returns a proper error message instead of "[6] handle is invalid."
v1.3
- Recompiled application as unicode.
v1.2:
- File modified time is now no longer changed when fixing its checksum (but last access time is not preserved).
- Fixed a compiler warning.
v1.1:
- Checksum printed on screen in hexadecimal instead of decimal
- Improved check for non-PE files.
v1.0:
- Initial release
Last edited by n7Epsilon on Wed Dec 02, 2009 8:33 am, edited 12 times in total.
[Tool] PEChecksum v1.2 - modifype replacement
n7Epsilon, just tried your new tool PEChecksum.exe, sounds interesting (you might want to create a new discussion thread about it)
the major problem with modifyPE is that you can't specify input file path, you have to run modifype from folder where input file is.
however, using these 2 tools, the displayed checksum isn't the same... can you explain me why? ex:
modifype notepad.exe -c -v reports me "checksum is 000147F7"
pechecksum -p notepad.exe reports me "checksum is 85887"
the major problem with modifyPE is that you can't specify input file path, you have to run modifype from folder where input file is.
however, using these 2 tools, the displayed checksum isn't the same... can you explain me why? ex:
modifype notepad.exe -c -v reports me "checksum is 000147F7"
pechecksum -p notepad.exe reports me "checksum is 85887"
(slap myself
) just checked, that's right, thanks for the quick reply... it was too easy to find... re-slap myself... 
however, as this tool intends to be a modifyPE replacement/successor, you might display checksum by default in hex format (as modifyPE does), and add a command-line option (for example "-d") to display checksum in decimal format


however, as this tool intends to be a modifyPE replacement/successor, you might display checksum by default in hex format (as modifyPE does), and add a command-line option (for example "-d") to display checksum in decimal format

- Kelsenellenelvian
- Moderator
- Posts: 4383
- Joined: Tue Nov 30, 2004 8:32 pm
- Location: Pocatello, ID
- Contact:
- Kelsenellenelvian
- Moderator
- Posts: 4383
- Joined: Tue Nov 30, 2004 8:32 pm
- Location: Pocatello, ID
- Contact:
Re: [Tool] PEChecksum v1.4 - modifype replacement
some China ISPs "provided" moooore restrictions than comcast, and the official explanation was "help prevent xx files, movies, pics being exchanged and spreaded". but in fact any one believes the true reason must be to reduce network usage.
gclub
gclub