[comp.sys.ibm.pc.misc] 80x86/88 TASM/MASM object files, Intel compatible?

josephc@nntp-server.caltech.edu (Joseph I. Chiu) (01/22/91)

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

rcollins@altos86.Altos.COM (Robert Collins) (01/24/91)

In article <1991Jan22.115739.7859@nntp-server.caltech.edu> josephc@nntp-server.caltech.edu (Joseph I. Chiu) writes:
>
>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)
>
Yes there is:  "Link & Locate ++" by Systems & Software Inc.  They are
located in Costa Mesa, CA (714) 833-1700.  At the time I bought the product,
they didn't support any CPU above '186 -- they only supported 8086/80186.


-- 
"Worship the Lord your God, and serve him only."  Mat. 4:10
Robert Collins                 UUCP:  ...!sun!altos86!rcollins
HOME:  (408) 225-8002
WORK:  (408) 432-6200 x4356