   the portable executable (pe) format is a file format for executables, object code, dlls, fon font files,http://www.chiark.greenend.org.uk/~sgtatham/fonts/, last accessed 2012-10-31http://www.wotsit.org/download.asp?f=fonwin&sc=404999432, last accessed 2012-10-31 and others used in 32-bit and 64-bit versions of windows operating systems. the pe format is a data structure that encapsulates the information necessary for the windows os loader to manage the wrapped executable code. this includes dynamic library references for linking, api export and import tables, resource management data and thread-local storage (tls) data. on nt operating systems, the pe format is used for exe, dll, sys (device driver), and other file types. the extensible firmware interface (efi) specification states that pe is the standard executable format in efi environments., a note on p.18, states that "this image type is chosen to enable uefi images to contain thumb and thumb2 instructions while defining the efi interfaces themselves to be in arm mode." pe is a modified version of the unix coff (common object file format). pe/coff is an alternative term in windows development. on windows nt operating systems, pe currently supports the ia-32, ia-64, x86-64 (amd64/intel64), and arm instruction set architectures (isas). prior to windows 2000, windows nt (and thus pe) supported the mips, alpha, and powerpc isas. because pe is used on windows ce, it continues to support several variants of the mips, arm (including thumb), and superh isas. the main competitors to pe are elf (used in linux and most other versions of unix) and mach-o (used in mac os x). == history == microsoft migrated to the pe format with the introduction of the windows nt 3.1 operating system. all later versions of windows, including windows 95/98/me, support the file structure. the format has retained limited legacy support to bridge the gap between dos-based and nt systems. for example, pe/coff headers still include an [[dos mz e
Executable_file_formats Windows_administration