COM: Difference between revisions
| [unchecked revision] | [unchecked revision] |
(basic description) |
(added loading and see also sections) |
||
| Line 1: | Line 1: | ||
'''This is about the executable format, not Microsoft's [[Component Object Model]]''' |
|||
{{Stub}} |
{{Stub}} |
||
{{File formats}} |
{{File formats}} |
||
==COM Files== |
|||
===Introduction=== |
|||
COM files are extremely simple, making them useful if you want to load programs but you don't want to worry about relocating symbols, reading file headers, and other complications. However, their simplicity makes their usefulness limited, so you'll definitely want to support something more complex but useful, once your OS is advanced. |
COM files are extremely simple, making them useful if you want to load programs but you don't want to worry about relocating symbols, reading file headers, and other complications. However, their simplicity makes their usefulness limited, so you'll definitely want to support something more complex but useful, once your OS is advanced. |
||
| Line 9: | Line 11: | ||
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). |
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). |
||
===Loading=== |
|||
To load a COM file you need to load it to a low memory location, set ds and es to be pointing to the start of the file with an 0x100 org, and jump to the start, with offset 0x100. |
|||
==See also== |
|||
===Executables=== |
|||
====16 bit==== |
|||
*[[MZ]] |
|||
*[[NE]] |
|||
====32 bit==== |
|||
*[[PE]] |
|||
Revision as of 13:30, 2 March 2012
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, making them useful if you want to load programs but you don't want to worry about relocating symbols, reading file headers, and other complications. However, their simplicity makes their usefulness limited, so you'll definitely want to support something more complex but useful, once your OS is advanced.
COM files were used by MS-DOS. They are raw binaries--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. Unless you plan on supporting actual DOS programs, you don't need a PSP.
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).
Loading
To load a COM file you need to load it to a low memory location, set ds and es to be pointing to the start of the file with an 0x100 org, and jump to the start, with offset 0x100.