PEKS Gives you the checksum of file, and the one got from the PE header structure
Download

PEKS Ranking & Summary

PEKS Tags

header View Header checksum CRC file structure download header Wav File header CLIPINF Header file header GOP header sequence header encrypt PE-file PE-file Insert Header modify header File Checksum W3SVC header PE header conversion PE structure PE File Detector PE file inspection PE file inspector inspect PE file PE Header Structure Checksum Checker PE Header create Checksum file verify Checksum file Header set expand header file header file expander specific header Win32 Pe file Patch File Header File Header Patcher make unexecutable PE file header scroll erase PE header Verify Header File to Header add file header pe-file information create file structure create header file modify PE file access PE file source file header update header PE file Info generate header header file guard C++ header header converter create header Header Editor image header PE Editor view fits file header fits file header editor display fits file header PE Rebuilder Rsponse Header File Checksum Calculator protect PE file secure PE file PE file encryption check checksum file checksum file tester molecular structure file web header encrypte pe file file structure grabber copy file structure Pure Header Manipulation

PEKS Description

Some people really love debugging applications. Unfortunately sometimes you have to debug binary code, since you cannot find your original source code (remember: reverse engineering other people's code is not very polite). Well, you get the work done with your tools but there's a problem: you have just patched the binary file, but now it needs a new checksum. For ordinary PE files, this is not required, but NT family operating systems need that every kernel mode executable (like drivers) have its checksum verified, or they will stop with a blue dump. The PEKS application was designed to be a small command line tool that will give you the checksum of file, and the one got from the PE header structure. If you need to change it, just start peks filename new_checksum and it will set the new checksum into the PE structure. Remember to use the exadecimal format for the new checksum. Remember you have to check it another time to view the change! Examples: peks c:winnt otepad.exe (shows current notepad.exe status) peks c:winntsystem32driversafd.sys 12abc34 (sets the checksum to 0x12abc34) for %f in (*.bin) do peks %f 0 (sets to 0 the checksum of *.bin files in current dir) Attention! DO NOT change the checksum of a device driver if you don't know exactly what you're doing. This may render your system unbootable!

PEKS Related Software