Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site randvax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!oliveb!hplabs!sdcrdcf!randvax!jim
From: jim@randvax.UUCP (Jim Gillogly)
Newsgroups: net.micro.pc
Subject: Re: Com vs. Exe files
Message-ID: <2608@randvax.UUCP>
Date: Wed, 24-Jul-85 12:16:56 EDT
Article-I.D.: randvax.2608
Posted: Wed Jul 24 12:16:56 1985
Date-Received: Wed, 31-Jul-85 02:22:03 EDT
References: <1932@sunybcs.UUCP> <512@wdl1.UUCP>
Reply-To: jim@rand-unix.UUCP (Jim Gillogly)
Distribution: net
Organization: Banzai Institute
Lines: 14
Keywords: Lattice .COM files

People have been complaining that Lattice C can't produce .COM files.
That's wrong - I use it for .COM files constantly, and have been
for a couple of years.  Simply link the program with CC.OBJ instead of
C.OBJ and ignore the "Missing stack segment" error message from LINK.
It will produce a .EXE file which can then be run through EXE2BIN to
convert it into a .COM file.  No problem.

This is documented in the current version (2.15) of the manual on page 4-15.
I don't know whether it was in earlier versions.  As another correspondent
mentioned, the code+data must be less than 64K together (super-small model?).
-- 
	Jim Gillogly
	{decvax, vortex}!randvax!jim
	jim@rand-unix.arpa