I am using Visual Studio and MASM32. I have been able to compile my .asm file. I used:

\masm32\bin\ml.exe /nologo /coff /Zf /c /Sa $(InputPath)

as a Custom Build command and:


as the output in Custom Build.

But I get the error:

Search.obj : fatal error LNK1190: invalid fixup found, type 0x0001
Error executing link.exe.

Prog006.exe - 1 error(s), 0 warning(s)

during the link process. How can I get my program to link?
Posted on 2001-11-14 11:07:15 by mplafleur@peoplepc.com
I assume "search.asm" is your assembler file. This is pretty weird,
because /coff should generate ms-coff files as required for the ms
win32 linker... which should, then, definitely not be bitching about
"invalid fixup type".

Attach your entire project and I'll have a look.
Posted on 2001-11-14 11:25:20 by f0dder
Here's my .asm file.

My next question will be. After I can compile. How do I generate debug code that I can step through using Visual Studio?

Posted on 2001-11-14 11:44:47 by mplafleur
Heh, your code is old 16bit dos crap :). Which means you should NOT
use /coff as a parameter to masm. And you also have to find an older
microsoft linker that's capable of producing 16bit .exe files. And
most likely you
will not be able to debug with the visual studio debugger. Time to
enter the 32bit world, my friend :).
Posted on 2001-11-14 11:57:01 by f0dder
Thanks for your time and effort. I was hoping to use the development tools I am used to using. This is for a micro class I am taking for my masters. So I'm stuck with 16-bit for now.:(

I guess I could get the 16bit linker. But how do I make studio use that version over the 32 bit? Then I could at least create an .exe.
Posted on 2001-11-14 12:33:21 by mplafleur
I have no idea, really :/. Visual studio is *very* targetted towards
32bit (windows) development. Sorry :(
Posted on 2001-11-14 12:38:39 by f0dder
Dont know how to link it in visual studio. But you can find 16 bit link.exe at Iczelions site:

Iczelions Site

Posted on 2001-11-14 15:32:02 by dxantos
to integrate your 16 bit linker into vc just enter a second custom build line with the link command, for example:

\vc16\bin\link fname <link options>,,,<libs>,<def file>

and change the output to
Posted on 2001-11-15 02:34:00 by japheth

My next question will be. After I can compile. How do I generate debug code that I can step through using Visual Studio?

If you set up your linker and successfully complete a build, you can step through the code in VS by just pressing F5 for 'start', or F10 for 'single step'. You can also use the watch window to watch your variables and/or registers, and the locals window works just like it does in C.
Posted on 2001-11-15 04:08:09 by sluggy
Yeah sluggy, you can do that for 32bit apps... but can the VS debugger
handle 16bit apps? I think not, but haven't tested.
Posted on 2001-11-15 07:45:18 by f0dder
I'll be trying later when we get our next program assignment. I'll let you all know if it is successful.

Posted on 2001-11-15 10:08:24 by mplafleur