Peter Fitzsimmons wrote in a message to Paul Edwards:

PF> What happens if you replace tasm with masm?

 PE> If I change to masm 5.1, and change the ".model flat" to
 PE> ".model small", then I get the same problem, a trap-5.

 PF> Then don't change ".model flat"!  I don't think 5.1 actually
 PF> supports the .flat instruction.   Look on the ddk cdrom for
 PF> megabytes of *.asm samples that all assemble with masm 5.1.

Flat and small model are the same thing when "use32" segments are
in play, as happens by default once the ".386p" directive is
issued, but MASM 5.1 does not understand the keyword "flat."

 PF> I've got a tiny one here I wrote for a no-CRT dll init:

 PF>      .386p

 PF>  _TEXT segment dword public use32 'CODE'
 PF>      assume  cs:_TEXT

 PF>  extrn DllInit:PROC

 PF>  Init proc near
 PF>      jmp DllInit
 PF>  Init endp

 PF>  _TEXT ends

 PF>  end Init

In this code, the label "DllInit" defaults to type "extrn
near use32," as it should in flat model.  MASM 5.1 just does not allow
calling it "flat" model.

 PE> The "-oi" option to tasm is meant to produce "intel
standard"
 PE> object code.

 PF> I think that means the file format -- not the names of the
 PF> segments, or their alignments.

The "-oi" switch produces IBM-format OBJ files.  Intel-format
OBJs are the "standard" format selected by the "-os"
switch.  Similarly, "-op" selects Phar Lap format, while
"-o" selects standard format with overlay-safe linkage.
 
-- Mike


---