Xref: news2.mv.net comp.os.msdos.djgpp:2568
From: Daniel Josef Dekok <080970 AT bud DOT cc DOT swin DOT edu DOT au>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Paths and .COM files
Date: Wed, 10 Apr 1996 01:39:55 +1000
Organization: Swinburne University of Technology	
Lines: 20
Message-ID: <Pine.OSF.3.91.960410013840.13528A-100000@bud.cc.swin.edu.au>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960409110439 DOT 24867X-100000 AT is> <4kdelk$hji AT freenet-news DOT carleton DOT ca>
NNTP-Posting-Host: bude.cc.swin.edu.au
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
In-Reply-To: <4kdelk$hji@freenet-news.carleton.ca>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On 9 Apr 1996, Paul Derbyshire wrote:

> 
> 
> This may be slowly heading off topic, but I'm curious: what IS the
> difference between a .COM and a .EXE, aside from the MZ ZM thing and the
> file extension?
> Is there a difference in the code, in its functioning, in how DOS
> allocates it memory?

Im pretty sure Com files don't have a stack, whereas EXE's can
and also something about some 64k limit in a com file

> 
> --
>     .*.  "Clouds are not spheres, mountains are not cones, coastlines are not
>  -()  <  circles, and bark is not smooth, nor does lightning travel in a
>     `*'  straight line."    ,------------------------------------------------
>          -- B. Mandelbrot  |  Paul Derbyshire (PGD) ao950 AT freenet DOT carleton DOT ca
>