COM: Difference between revisions

Jump to navigation Jump to search
301 bytes removed ,  4 years ago
COM files are able to do their own memory organisation on the 8086 - the 64kB limit only applies to code that can't or doesn't make use of segmentation.
[unchecked revision][unchecked revision]
m (Added a small amount of information and made nicer to read.)
(COM files are able to do their own memory organisation on the 8086 - the 64kB limit only applies to code that can't or doesn't make use of segmentation.)
Line 6:
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 [http://heim.ifi.uio.no/~stanisls/helppc/program_segment_prefix.html here]. PSP is only required for running DOS programs.
 
COM files usually terminate with a RET instruction. On The operating system startsDOS, the COMRET program usingpops a CALLempty instruction,word sofrom RETthe returnsstack, towhich theresults OS,in allowinga anyinterrupt cleanup0x20 (likeDOS restartingAPI the command promptExit) to be handled by thebeing OScalled.
 
===Loading===
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu