Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!nntp-server.caltech.edu!josephc
From: josephc@nntp-server.caltech.edu (Joseph I. Chiu)
Newsgroups: comp.sys.ibm.pc.misc
Subject: 80x86/88 TASM/MASM object files, Intel compatible?
Summary: Are TASM/MASM object files compatible with Intel development products?
Keywords: Intel 8086 8088 80x86 80x88 Object .obj asm binary code emulation
Message-ID: <1991Jan22.115739.7859@nntp-server.caltech.edu>
Date: 22 Jan 91 11:57:39 GMT
Organization: California Institute of Technology, Pasadena
Lines: 25

I am currently developing a project using the Intel 80188 development kit
(i.e., the 186 ICE, and the ASM386 assembler) and I am extremely frustrated
with the aaggoonniizziinngg, slow compile time of their product.

In comparison, Turbo assembler zips along compiling the 80188 code, and will
produce a .obj file much much faster than Intel's ASM.

Problem: Apparently, the TASM (and thus MASM, err, vice-versa) .obj file is
not compatible with the Intel ASM's .obj file.  Is there a way around that?
(Like a format converter, if such a beast exist)

And if not, is there a way to take TASM's .obj output and convert it into a
pure binary code devoid of the debug/label/relocation information?  (By the
way, I will ORG the code at a specified memory location)

At worst, I may just decide to download the test program in 'shadow ram' by
overlapping my Boot ROM with some static RAM.  >sigh<

Thanks in advance to everyone.

-Joseph

-- 
--
josephc@coil.caltech.edu               ...Just another lost soul in the universe