assembly fatal error LNK1190: invalid fixup found, type 0x0001

问题

I want to write 16 bit 8086 assembly code in visual studio 2010 but gives me error: code:

.MODEL small
.STACK 100h
.data
message BYTE "Hello, world!","$"
.code
mov ah,9
mov dx,OFFSET message ; addr of buffer
int 21h
END

output gives me this error:

fm.obj : fatal error LNK1190: invalid fixup found, type 0x0001

I using masm32v11. What should I do?

回答1:

Where does the Assembler know where the starting address is? Using Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994 (16bit linker) and added start and end start the code Assembles and links just fine. MASM32 includes a 16bit linker in the bin directory. You must pass different command line parameters to ML to Assemble 16bit code correctly though.

.MODEL small
.STACK 100h
.data
message BYTE "Hello, world!","$"
.code
start:
mov ah,9
mov dx,OFFSET message ; addr of buffer
int 21h
END start

So to recap - your code needs a starting address and an end, You can use the current ML that comes with MASM32 to Assemble 16 bit and 32 bit code. To link 16 bit code you must use a 16 bit linker, to link 32 bit code, you must use a 32 bit linker.

From one of my 16 bit DOS apps:

ML.EXE /DMASM /DDOS /Zm /c /nologo /I"f:\masm32\Include" "dosdisplay.asm"
link16.exe /NOLOGO "dosdisplay.obj"

回答2:

Compile with these commands :

ml.exe /omf filename.asm

link16.exe filename.obj

Info:

when you invoke ml.exe without any specific parameters the type of object file that it generates will be in coff format. coff format name mangling requires that your code should have a "_start" and "end _start". what you have written will work for intel's omf object files.

来源：https://stackoverflow.com/questions/14692582/assembly-fatal-error-lnk1190-invalid-fixup-found-type-0x0001