Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > openwatcom.users.c_cpp > #3575
| From | Frank Beythien <fbeythien@gmx.de> |
|---|---|
| Newsgroups | openwatcom.users.c_cpp |
| Subject | Re: Generating CheckSum for AMD64 Executable |
| Date | 2019-05-01 17:10 +0200 |
| Organization | OpenWatcom |
| Message-ID | <qac9b7$9i5$1@www.openwatcom.org> (permalink) |
| References | <qac0fu$v31$1@www.openwatcom.org> |
Am 01.05.19 um 14:39 schrieb Paul McKneely: > Hi, > > I have written an assembler and library manager targeting AMD64 > using OpenWatcom 1.8. I am currently writing a Linker. Source > code is in C (not C++). Though the OW suite I am using is 32-bits, > I don't see any reason why it can't be used to write software that can > create 64-bit running target programs. > > The Optional Header of the AMD64 Exe has a field called CheckSum > at offset 64. The PE specification I am using says the following to > describe > the field that must be filled in within an EXE file: > > "The image file checksum. The algorithm for computing the checksum > is incorporated into IMAGHELP.DLL. The following are checked for > validation at load time: all drivers, any DLL loaded at boot time, and > any DLL that is loaded into a critical Windows process." > > Has anyone done this? Certainly the OW linker gets this field > completed for the 32-bit executables that it generates. Perhaps > the algorithm is the same. Is it possible to get the OW tool suite > that I am using to perform this action? > > Thanks. > Look at the OW Linker source at the website: openwatcom.org Direct jump to the source: http://perforce.openwatcom.org:4000/@md=d&cd=//depot/openwatcom/bld/wl/c/&c=lzi@//depot/openwatcom/bld/wl/c/loadpe.c?ac=22 Frank
Back to openwatcom.users.c_cpp | Previous | Next — Previous in thread | Find similar
Generating CheckSum for AMD64 Executable Paul McKneely <pkmckneely@sbcglobal.net> - 2019-05-01 07:39 -0500 Re: Generating CheckSum for AMD64 Executable Frank Beythien <fbeythien@gmx.de> - 2019-05-01 17:10 +0200
csiph-web