Xref:	news2.mv.net comp.os.msdos.djgpp:2660
From:	beppu AT arcturus DOT oac DOT uci DOT edu (John Beppu)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Paths and .COM files
Date:	11 Apr 1996 14:26:09 GMT
Organization:	University of California, Irvine
Lines:	16
Message-ID:	<4kj4q1$g35@news.service.uci.edu>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 960409110439 DOT 24867X-100000 AT is> <4kdelk$hji AT freenet-news DOT carleton DOT ca> <Pine DOT OSF DOT 3 DOT 91 DOT 960410013840 DOT 13528A-100000 AT bud DOT cc DOT swin DOT edu DOT au>
NNTP-Posting-Host:	arcturus.oac.uci.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

   This is how I understand the difference between .COM files
   and .EXE files.

   .COM files are dumped into memory at CS:0100h and are allocated
   all available low memory.  The PSP is located at CS:0000h..CS:00FFh.
   Finally, at startup, CS, DS, and SS all equal eachother.  If the
   stack grows too large, code and/or data may be overwritten.

   .EXE files have that 'MZ' signature at front in addition to a header
   with information about the prog such as the entry point, relocation
   information, and probably more.


--
   beppu AT ea DOT oac DOT uci DOT edu

- Raw text -