Okay, i solved it.

WLINK.EXE does need different parameter options:

In this example it works with the following command line:

1wlink name test.exe format dos file one.obj , two.obj

The "name" options followed by a file name defines how the resulting executable should be called.
TEST.EXE can be changed to whatever you want to use and is the resulting executable name.

The "format" option followed by "DOS" defines, that this is an executable for DOS.

The "file" option followed by an object file, that was created with JWASMR defines what obj files to use.
Each object file must be separated with a comma.

The linker seems to not be able to use *.asm code files and pass them to jwasmr automatically.

Try this:

1wlink name final.exe file one.obj,two.obj

Note the comma between the object files.

Edit: You beat me to it. 😀

pan069 wrote on 2022-08-21, 09:45:

Try this: […]
Show full quote

Try this:

Copy code to clipboard

1wlink name final.exe file one.obj,two.obj

Note the comma between the object files.

Edit: You beat me to it. 😀

😀

I also found out, that it is not required to add the file extension.

This:

1wlink name final file one,two

will work too. At least in DOS, it might be different on other systems but i need wlink only for DOS.

The file extension is automatically determined.

Why do you create a FAR proc when using model SMALL?

Ringding wrote on 2022-08-21, 12:50:

Why do you create a FAR proc when using model SMALL?

Because it's in another object file and thus very likely another segment.

Exploit wrote on 2022-08-21, 12:55:

Ringding wrote on 2022-08-21, 12:50:

Why do you create a FAR proc when using model SMALL?

Because it's in another object file and thus very likely another segment.

The idea of MODEL SMALL is that the code segments of all source files gets combined by the linker into a single 64K code segments, so all CALLs and function pointers can be near. If you want different code segments for different object files, you should use MODEL MEDIUM (near data pointers) or MODEL LARGE (far data pointers). Even in MODEL LARGE, all data segments from the object files get combined into a single data segment, and DS is intended to point to this "primary data segment". Standard data pointers are allowed to point anywhere, even outside of the primary data segment. (e.g. segments allocated from DOS using INT 21h/AH=48h, video memory or the EMS page frame).

mkarcher wrote on 2022-08-21, 13:39:

Exploit wrote on 2022-08-21, 12:55:

Ringding wrote on 2022-08-21, 12:50:

Why do you create a FAR proc when using model SMALL?

Because it's in another object file and thus very likely another segment.

The idea of MODEL SMALL is that the code segments of all source files gets combined by the linker into a single 64K code segments, so all CALLs and function pointers can be near.

Well, I was just repeating what's in the book. And it seems to make sense for library purposes.

Exploit wrote on 2022-08-21, 09:04:

But WLINK.EXE can't link them: […]
Show full quote

But WLINK.EXE can't link them:

Copy code to clipboard

1C:\>wlink one.asm two.asm 
2Open Watcom Linker Version 1.9
3Portions Copyright (c) 1985-2002 Sybase, Inc. All Rights Reserved.
4Source code is available under the Sybase Open Watcom Public License.
5See http://www.openwatcom.org/ for details.
6Error! E3033: directive error near 'one.asm'
7C:\>

well, you cant link assembler files before assembling them... and as you noted, wlink has a formatted command line. easier to just wcl/wcl386 if you want one step compile+link.

BloodyCactus wrote on 2022-08-21, 14:58:

well, you cant link assembler files before assembling them...

That was not the point. I also said, i used wlink *.obj ... etc.

And ml.exe can do exactly that. It assembles and links in one go.
Also you're too late, the problem is already solved.