| delorie.com/archives/browse.cgi | search |
| Xref: | news2.mv.net comp.os.msdos.djgpp:2557 |
| From: | ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: Paths and .COM files |
| Date: | 9 Apr 1996 10:37:40 GMT |
| Organization: | The National Capital FreeNet |
| Lines: | 13 |
| Sender: | ao950 AT freenet2 DOT carleton DOT ca (Paul Derbyshire) |
| Message-ID: | <4kdelk$hji@freenet-news.carleton.ca> |
| References: | <Pine DOT SUN DOT 3 DOT 91 DOT 960409110439 DOT 24867X-100000 AT is> |
| Reply-To: | ao950 AT FreeNet DOT Carleton DOT CA (Paul Derbyshire) |
| NNTP-Posting-Host: | freenet2.carleton.ca |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
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?
--
.*. "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
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |