COM: Difference between revisions
| [unchecked revision] | [unchecked revision] |
(added loading and see also sections) |
m (Added a small amount of information and made nicer to read.) |
||
| Line 4: | Line 4: | ||
==COM Files== |
==COM Files== |
||
===Introduction=== |
===Introduction=== |
||
COM files are extremely simple |
COM files are extremely simple executable files. They are useful for loading programs without complications like relocating symbols, reading file headers, etc. However, their simplicity can make their usefulness limited, so you may want to support something more complex but useful, like [[ELF]], once your OS is advanced. |
||
COM files were used by MS-DOS. They are raw binaries |
COM files were used by MS-DOS. They are raw binaries, meaning there is no header data. Also, COM files are restricted to the size of one segment (a real-address mode segment, 64kb), minus 256 bytes. When a COM file is loaded, it is assumed that all code and data fits in one segment, and it is loaded to offset 0x100. |
||
MS-DOS creates and stores an info structure starting at offset 0 and ending just before 0x100, called the Program Segment Prefix (PSP). The PSP is made just before starting the COM program. More info about the PSP can be found [http://heim.ifi.uio.no/~stanisls/helppc/program_segment_prefix.html here]. |
MS-DOS creates and stores an info structure starting at offset 0 and ending just before 0x100, called the Program Segment Prefix (PSP). The PSP is made just before starting the COM program. More info about the PSP can be found [http://heim.ifi.uio.no/~stanisls/helppc/program_segment_prefix.html here]. PSP is only required for running DOS programs. |
||
| ⚫ | |||
| ⚫ | |||
===Loading=== |
===Loading=== |
||
To load a COM file you need to load it to a low memory location, |
To load a COM file you need to load it to a low memory location, point ds and es to the start of the file with an 0x100 org, and jump to the start, with offset 0x100. |
||
==See also== |
==See also== |
||
===Executables=== |
===Executables=== |
||
Revision as of 17:31, 7 May 2019
This is about the executable format, not Microsoft's Component Object Model
| Executable Formats |
|---|
| Microsoft |
| *nix |
| Apple |
COM Files
Introduction
COM files are extremely simple executable files. They are useful for loading programs without complications like relocating symbols, reading file headers, etc. However, their simplicity can make their usefulness limited, so you may want to support something more complex but useful, like ELF, once your OS is advanced.
COM files were used by MS-DOS. They are raw binaries, meaning there is no header data. Also, COM files are restricted to the size of one segment (a real-address mode segment, 64kb), minus 256 bytes. When a COM file is loaded, it is assumed that all code and data fits in one segment, and it is loaded to offset 0x100.
MS-DOS creates and stores an info structure starting at offset 0 and ending just before 0x100, called the Program Segment Prefix (PSP). The PSP is made just before starting the COM program. More info about the PSP can be found here. PSP is only required for running DOS programs.
COM files usually terminate with a RET instruction. The operating system starts the COM program using a CALL instruction, so RET returns to the OS, allowing any cleanup (like restarting the command prompt) to be handled by the OS.
Loading
To load a COM file you need to load it to a low memory location, point ds and es to the start of the file with an 0x100 org, and jump to the start, with offset 0x100.