Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!snorkelwacker!apple!sun-barr!rutgers!mcnc!rti!bcw
From: bcw@rti.rti.org (Bruce Wright)
Newsgroups: comp.windows.ms
Subject: Re: Converting COM to EXE
Summary: .COM -> .EXE
Message-ID: <4067@rtifs1.UUCP>
Date: 12 Sep 90 17:08:25 GMT
References: <10446@pt.cs.cmu.edu> <1990Sep12.112646.16097@murdoch.acc.Virginia.EDU>
Organization: Research Triangle Institute, RTP, NC
Lines: 26

In article <1990Sep12.112646.16097@murdoch.acc.Virginia.EDU>, rb9a@watt.acc.Virginia.EDU (Raul Baragiola) writes:
> In article <10446@pt.cs.cmu.edu> climan@clamen.avalon.cs.cmu.edu (Dani Climan) writes:
> >Is there a utility that will convert COM files to EXE so that they
> >can run based on their input files extension.  For example, I would
> >like to run a PAGE.COM when I click on a .txt file.  Any suggestions
> >would be appreciated.
> 
> The utility is copy: copy filename.com filename.exe. This should work
> if I understood you correctly.

Since DOS can tell from the file contents whether the file is
organized as a .COM or a .EXE file, Raul is correct that this 
should work for the problem in Windows.

But if (as sounds possible) Raul is claiming that this will
convert the .COM to a real .EXE file, that just isn't true:
the .EXE file has additional information that is missing from
the .COM file and a simple copy won't hack it.

It shouldn't be difficult to convert a .COM to a .EXE, though
apart from this problem with Windows I'm not exactly sure why
you'd want to;  there are no big advantages that you gain 
since you still wouldn't have the program running in anything 
more than 64K or able to run in protected memory.

					Bruce C. Wright