Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Home » Archive » net.micro.pc » RE: OBJ/COM formats
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
RE: OBJ/COM formats [message #74433] Sun, 26 May 2013 21:03 Go to next message
Anonymous
Karma:
Originally posted by: markz@microsoft.UUCP (Mark Zbikowski)
Message-ID: <8707@microsoft.UUCP>
Date: Mon, 13-Aug-84 18:28:33 EDT
Article-I.D.: microsoft.8707
Posted: Mon Aug 13 18:28:33 1984
Date-Received: Wed, 15-Aug-84 01:39:38 EDT
Organization: Microsoft Corporation
Lines: 37


	"... I am not including this statement because with it exe2bin would not
	convert the file..."

EXE2BIN will convert an EXE file to a COM-format file under the following
circumstances:

o   Entry point is 0:100h
o   No Stack segment is present
o   Image size is < 65536-100h-2
o   There are NO relocatable long references.

I strongly suspect that there is something else at work here.

	"... I suspect that it is something to do with having data segments
	separate from the code segment..."

You have probably just hit the nail on the head.  If you are using the macro
assembler from IBM, you'll find that it will emit segment definitions in
alphabetic order rather than in declaration order.  This *may* be causing
your data segment to precede your code segment which might violate the first
condition above.

I really question your need of COM files in the first place.  The *only*
place that they might be useful is in device drivers.  Outside of these,
MSDOS is quite capable of performing all relocation for you.  I strongly
urge anyone who is thinking of using COM files to stick with the EXE format.
Reasons:

o   No need for EXE2BIN.
o   Full use of instruction set (you can't effectively use the long call
	instruction, for example) by being relocatable.
o   Has extensible header should any changes to the format be needed.
o   EXE files don't have 64K-100h-2 size restriction.
o   Full control of stack placement.  COM files have no guarantee on minimal
	size of stack.  I have seen a great numbers of COM files that fail on
	small-memory machines or on reading large data over where their stack
	was.
Re: RE: OBJ/COM formats [message #74452 is a reply to message #74433] Sun, 26 May 2013 21:03 Go to previous message
dob is currently offline  dob
Messages: 16
Registered: May 2013
Karma: 0
Junior Member
Message-ID: <656@ihuxj.UUCP>
Date: Wed, 15-Aug-84 16:40:28 EDT
Article-I.D.: ihuxj.656
Posted: Wed Aug 15 16:40:28 1984
Date-Received: Thu, 16-Aug-84 03:17:23 EDT
References: <8707@microsoft.UUCP>
Organization: AT&T Bell Labs, Naperville, IL
Lines: 15

As you point out in great detail, .EXE files offer plenty
of features, but one pays the price for them: slower load
time, and bigger image on disk (and there ain't much room on
those thar floppies!).


-- 
		
			Daniel M. O'Brien
			AT&T Bell Laboratories
			IH 4A-258
			Naperville, IL 60566
		
			....!ihuxj!dob
		
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Intuit Integrated Software
Next Topic: MS FORTRAN / LINK with Libraries Problem
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 01 22:46:08 EDT 2022

Total time taken to generate the page: 0.02037 seconds