Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!apple!bloom-beacon!bu-cs!madd
From: madd@bu-cs.BU.EDU (Jim Frost)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Execution Order
Message-ID: <28322@bu-cs.BU.EDU>
Date: 26 Feb 89 21:04:28 GMT
References: <992@expya.cs.exeter.ac.uk> <22@dbase.UUCP> <7237@killer.DALLAS.TX.US>
Reply-To: madd@buitc.bu.edu (Jim Frost)
Followup-To: comp.sys.ibm.pc
Organization: Boston University Distributed Systems Group
Lines: 12

In article <7237@killer.DALLAS.TX.US> jls@killer.DALLAS.TX.US (Jerome Schneider) writes:
|As a side note, the EXE extension on a file is not really used by the
|loader -- a magic number in the first two bytes identifies a relocatable
|module, even if it is called foo.bar.  However, this trick is probably
|valid only from a spawn() call that bypasses COMMAND.COM.

In fact, many commercial packages take advantage of this to make
independent modules which are not user-runnable.  DisplayWrite III is
such a program, using the extension .PRG for each of the modules.

jim frost
madd@bu-it.bu.edu