Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!bloom-beacon!eru!luth!sunic!dkuug!iesd!kjeld
From: kjeld@iesd.auc.dk (Kjeld Flarup)
Newsgroups: comp.sys.ibm.pc
Subject: Re: .COM and .EXE files
Message-ID: <1989Oct23.153433.7451@iesd.auc.dk>
Date: 23 Oct 89 15:34:33 GMT
References: <00092@citasim.UUCP> <253B310B.23002@maccs.dcss.mcmaster.ca>
Reply-To: kjeld@iesd.auc.dk (Kjeld Flarup)
Organization: Mathematics & Computer Science, University of Aalborg
Lines: 13

In article <253B310B.23002@maccs.dcss.mcmaster.ca> cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) writes:
>   Alternatively, you can write your own COMMAND.COM replacement, complete
>with a new loader that recognizes more than just .COM and .EXE ... but that
>will take time on the order of man-months.

I wrote a small and primitive one this weekend. he spawn command in
MicroSoft C uses the DOS exec call and will load any file. 
Anyhow look at the two first bytes in a .exe file, they are always the
same and they will not appear first in a .com file because they make
very little meaning to execute.
-- 
*     I am several thousand pages behind my reading schedule.    *
Kjeld Flarup Christensen                         kjeld@iesd.auc.dk