EXEHDR then displays the header fields for the segmented executable file. In addition to the default fields described on topic , the verbose output includes many other fields.
A field called Operating system: follows the Description: field. This field tells the system under which the program is to run.
The following fields are then displayed:
Linker version:
32-bit Checksum:
Segment Table:
Resource Table:
Resident Names Table:
Module Reference Table:
Imported Names Table:
Entry Table:
Non-resident Names Table:
Movable entry points:
Segment sector size:
Heap allocation:
Application type:
Other module flags:
The meaning of each field is described in the following list:
Linker version:
Tells which version of LINK was used to create the segmented executable file.
32-bit Checksum:
Confirms for the loader that the file is a valid executable file. (See the Word checksum: field for DOS executable files.)
Segment Table: Resource Table: Resident Names Table: Module Reference Table: Imported Names Table: Entry Table: Non-resident Names Table:
Describe various tables in the segmented executable file. Each description gives the table name, its address within the file, and its length in hexadecimal and in decimal.
Movable entry points:
Gives the number of entries to segments that have the MOVABLE attribute. This field is used only by Windows.
Segment sector size:
Gives the alignment set by the /ALIGN option or the default of 512. This field equals the sector size on disk.
Heap allocation:
Gives the size of the heap. This field is displayed only if a HEAPSIZE statement appeared in the module-definition file.
Application type:
Gives the type as specified in the PMTYPE statement of the module-definition file used to create the file being examined, or as specified with LINK's /PM option, or assumed by default. For a DLL, a 0 is always displayed.
Other module flags:
Gives other attributes of the file; if none, this field is not displayed.
At the end of the list of fields, EXEHDR displays any module flags that were set for every segment in the module. For example, PROTMODE may appear.