Fatal error l1101 invalid object module

Fatal error l1101 invalid object module

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Hi.
I have MS VS2005 Professional, which has Masm v.8 (OS MS Windows XP SP2)
I recently started learning assembly language. And I have no problems compiling 32-bit code.

There’s only something wrong while compiling asm code to produce COM files.

Here’s simple code sample:

CSEG segment
ORG 100h

mov ah,9
mov dx,offset Message
int 21h
int 20h
Message db ‘Hello, world!$’
CSEG ends
end Begin

I compile it in command line like this:
ml test.asm /AT
I use /AT to enable tiny model (COM files). But I get the following:
test.obj : fatal error LNK1190: invalid fix-up found, type 0x0001 .

Could anyone tell me if there is a way to compile the 16-bit assembly code using Masm v.8 to produce COM files? Or I need to install like Masm v.6.xx?

Would appreciate any help

Answers

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 «Begin» should have a leading underscore. what you have written will work for intel’s omf object files. try using this with v.8 : «ml.exe /omf filename.asm». As far as I remember MS assemblers used to generate omf by default which the linker used to consume. Looks like this has been changed.

I’m not sure you have to follow this way. to build COM components.

A COM component hosts one or multiple COM class or coclass with is represented, structurally, as a virtual C++ class.
So you should continue to learn ASM, but to build COM class, you will have to build C++ applications, it is easier.

Note:
In the case you cant to build every thing from scratch, I do’nt know asm samples, but there are some C samples.
In the early days of COM programming, in the Win16 land, there were C sample code, provided in the Platform SDK that shown how to build COM coclass (with registration and every thing needed) using C langage.
May be it was in the OLE samples.

Well, I write C++ code anyways ( I’m first-year Computer Science student). I would just like to know whether it’s technically possible to compile, for instance, the above mentioned simple16-bit code using Masm v.8 to produce a COM file. (It just writes a classical «Hello World!»). It’s not the program itself that interests me. It’s how to do it in assembly language. And to be exact, how to produce a COM file using Masm v.8.

Maybe someone knows.

P.S.Thanks anyway for the answer

OK, at last I compiled the above mentioned 16-bit code to produce working COM file, but only after installing MASM v6.xx and only using 16-bit linker. And after linking I get .EXE file, which I convert to COM using exe2bin.

Seems like MASM v.8 is not supposed to link 16-bit programs.

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 «Begin» should have a leading underscore. what you have written will work for intel’s omf object files. try using this with v.8 : «ml.exe /omf filename.asm». As far as I remember MS assemblers used to generate omf by default which the linker used to consume. Looks like this has been changed.

Wow, it worked. You’re right that by default it generates object files in coff format. Without specifying, that ml has to compile an object module format object file, even if I used 16-bit linker, it would give a fatal error:

TEST.OBJ : fatal error L1101: invalid object module

, which now makes sense. A couple of days ago I figured out on myself how to compile my example code using MASM v.6.xx and 16-bit link.exe. I thought that I definetely have to use not only 16-bit linker, but ml.exe version 6.xx. But at last I was able to compile using ml.exe v.8! But still you have to use 16-bit linker ( for instance Microsoft link.exe v.5.xx) to link 16-bit code. It will produce an .EXE file, which I easily convert to .COM using exe2bin.

And of course it’s easier to write a batch file for this to make the compilation faster:

Источник

I am trying to pick up some Win32asm. I am doing the «hello world» first program (plz don’t laugh 😉 ) from http://www.thomasbleeker.nl/exagone/WIN32ASM/tutor12.html
I have adjusted his code to reflect my ‘MASM’ directory rather than his ‘MASM32’ dir. I got the required .inc and .lib files from another PC which has MASM32 v6 SP2 installed, and added them to the appropriate MASM folders.

When I follow his instructions I get the following error:

«first.obj : fatal error L1101: invalid object module»

Could anybody please tell me what’s going wrong?

Thanks,
Bill Miller

Below are my program specs and complete console dump of command prompt error:

WinXP; MASM 6.15 and Link 5.63

My (User) Variables:
PATH=C:MASMBIN;C:MASMBINR;%PATH%
LIB=C:MASMLIB
INCLUDE=C:MASMINCLUDE
INIT=C:MASMINIT
HELPFILES=C:MASMHELP*.HLP
ASMEX=C:MASMSAMPLES

NOTE: I do *NOT* have MASM32 installed. I got the .lib and .inc files from another computer.

kernel32.lib, user32.lib, kernel32.inc, user32.inc (MASM32 v6SP2)
windows.inc v1.25

Here’s my cmd-prompt dump:
ps. when I leave out the ‘/subsystem:windows’ it won’t complain about that but the ‘invalid object module error’ remains.
C:MASMBIN>make
Microsoft (R) Macro Assembler Version 6.15.8803
Copyright (C) Microsoft Corp 1981-2000. All rights reserved.

Microsoft (R) Segmented Executable Linker Version 5.60.339 Dec 5 1994
Copyright (C) Microsoft Corp 1984-1993. All rights reserved.

Источник

Fatal error l1101 invalid object module

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

Hi.
I have MS VS2005 Professional, which has Masm v.8 (OS MS Windows XP SP2)
I recently started learning assembly language. And I have no problems compiling 32-bit code.

There’s only something wrong while compiling asm code to produce COM files.

Here’s simple code sample:

CSEG segment
ORG 100h

mov ah,9
mov dx,offset Message
int 21h
int 20h
Message db ‘Hello, world!$’
CSEG ends
end Begin

I compile it in command line like this:
ml test.asm /AT
I use /AT to enable tiny model (COM files). But I get the following:
test.obj : fatal error LNK1190: invalid fix-up found, type 0x0001 .

Could anyone tell me if there is a way to compile the 16-bit assembly code using Masm v.8 to produce COM files? Or I need to install like Masm v.6.xx?

Would appreciate any help

Answers

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 «Begin» should have a leading underscore. what you have written will work for intel’s omf object files. try using this with v.8 : «ml.exe /omf filename.asm». As far as I remember MS assemblers used to generate omf by default which the linker used to consume. Looks like this has been changed.

I’m not sure you have to follow this way. to build COM components.

A COM component hosts one or multiple COM class or coclass with is represented, structurally, as a virtual C++ class.
So you should continue to learn ASM, but to build COM class, you will have to build C++ applications, it is easier.

Note:
In the case you cant to build every thing from scratch, I do’nt know asm samples, but there are some C samples.
In the early days of COM programming, in the Win16 land, there were C sample code, provided in the Platform SDK that shown how to build COM coclass (with registration and every thing needed) using C langage.
May be it was in the OLE samples.

Well, I write C++ code anyways ( I’m first-year Computer Science student). I would just like to know whether it’s technically possible to compile, for instance, the above mentioned simple16-bit code using Masm v.8 to produce a COM file. (It just writes a classical «Hello World!»). It’s not the program itself that interests me. It’s how to do it in assembly language. And to be exact, how to produce a COM file using Masm v.8.

Maybe someone knows.

P.S.Thanks anyway for the answer

OK, at last I compiled the above mentioned 16-bit code to produce working COM file, but only after installing MASM v6.xx and only using 16-bit linker. And after linking I get .EXE file, which I convert to COM using exe2bin.

Seems like MASM v.8 is not supposed to link 16-bit programs.

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 «Begin» should have a leading underscore. what you have written will work for intel’s omf object files. try using this with v.8 : «ml.exe /omf filename.asm». As far as I remember MS assemblers used to generate omf by default which the linker used to consume. Looks like this has been changed.

Wow, it worked. You’re right that by default it generates object files in coff format. Without specifying, that ml has to compile an object module format object file, even if I used 16-bit linker, it would give a fatal error:

TEST.OBJ : fatal error L1101: invalid object module

, which now makes sense. A couple of days ago I figured out on myself how to compile my example code using MASM v.6.xx and 16-bit link.exe. I thought that I definetely have to use not only 16-bit linker, but ml.exe version 6.xx. But at last I was able to compile using ml.exe v.8! But still you have to use 16-bit linker ( for instance Microsoft link.exe v.5.xx) to link 16-bit code. It will produce an .EXE file, which I easily convert to .COM using exe2bin.

And of course it’s easier to write a batch file for this to make the compilation faster:

Источник

Microsoft KB Archive/95121

Contents

FIX: L1101 Error Linking MASM Object Module w/ Large Structure

Article ID: 95121

Article Last Modified on 10/20/2003

• Microsoft Macro Assembler 6.0 Standard Edition
• Microsoft Macro Assembler 6.0a
• Microsoft Macro Assembler 6.0b
• Microsoft Macro Assembler 6.1 Standard Edition
• Microsoft Macro Assembler 6.1a
• Microsoft Macro Assembler 6.11 Standard Edition

This article was previously published under Q95121

SYMPTOMS

An attempt to link an application assembled with the Microsoft Macro Assembler (MASM) fails and the Microsoft Link utility (LINK) generates the following message:

fatal error L1101: invalid object module

CAUSE

MASM generates an incorrect LIDATA record when the source code declares large data structures.

RESOLUTION

To work around this problem, organize structure initialization into a series of DUP directives, as shown below. If necessary, MASM processes the structure into several LIDATA records.

STATUS

Microsoft has confirmed this to be a problem in MASM versions 6.0, 6.0a, 6.0b, 6.1, and 6.1a. This problem was corrected in MASM for MS-DOS version 6.11.

MORE INFORMATION

The code example below demonstrates this problem. Even though MASM is designed to create multiple LIDATA records for a data structure larger than 512 bytes, the assembler creates one LIDATA record for the entire data structure. When this occurs, the L1101 error occurs as indicated above.

See «The MS-DOS Encyclopedia» (Microsoft Press) for more information on the LIDATA record or other aspects of the object module format.

Sample Code

Additional query words: 6.00 6.00a 6.00b 6.10 6.10a buglist6.00a buglist6.00b buglist6.10 buglist6.10a fixlist6.11

Keywords: kbfix KB95121

© Microsoft Corporation. All rights reserved.

Источник