Date:	Sun, 28 May 2000 11:01:01 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: MASM coff images
In-Reply-To:	<04039b30.28983095@usw-ex0101-008.remarq.com>
Message-ID:	<Pine.SUN.3.91.1000528110019.15881K-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, 27 May 2000, Dogansmoobs wrote:

> I have a lot of code written a while ago when I used MASM that I
> would not like to lose.

Unfortunately, you might need to lose it anyway, if it relies too much
on real-mode code.

> I am using MASM 6.11.

You should be prepared to deal with some trouble.  At least one person
reported here problems with COFF output by MASM (like addresses being
offset by some small amount of bytes).  This option is not used very
often, so the reports I have are inconclusive.

I suggest to review your code and decide whether you really need to
reuse it with DJGPP.  It's possible that large portions of your code
would not work in protected mode anyway, in which case it would be a
waste of effort on your part to tinker with MASM.

> I am getting the impression from the FAQ that this is not done
> all that often, but I would hate to convert all my code int AT&T
> syntax.

How about converting it to C?  See my other message in this thread.

- Raw text -