means you did not link the needed libraries

thanks, i'll doublechek it. but if lnk file is created succesfully isn't it means that libs are linked? here is content of lnk file:

1NAME mdc
2DEBUG all
3LIBPath .\vgatst\lib
4LIBPath ..\3dfx\lib
5LIBPath ..\lua\lib
6LIBPath .\gplay
7FILE main.obj
8FILE errrpt.obj
9FILE pcibrd.obj
10FILE banshee.obj
11FILE init.obj
12FILE mdclua.obj
13FILE misc.obj
14FILE memerr.obj
15FILE memtst.obj
16FILE pcitst.obj
17FILE builtin.obj
18FILE version.obj
19FILE crc.obj
20FILE lm_bios.obj
21FILE lm_ban.obj
22FILE lm_glde.obj
23FILE vgacore.obj
24library fxpci.lib
25library llua.lib
26library luaaux.lib
27library h3cinit.lib
28library minihwc.lib
29library glide2x.lib
30library fxmisc.lib
31library vgacore.lib
32library ediag.lib
33library ediag1.lib
34library vgadata.lib
35library elib.lib
36library repdev.lib
37library gplay.lib

anthony wrote:

if lnk file is created succesfully isn't it means that libs are linked?

i don't know watcom, but my experience with other tools tells me that it is only the linker who says if all symbols are there or not; and being there does not mean being in the right folder, you usually have to inform the linker of the binaries to be linked;

quite strange behaviour of linker. he throws an error "undefined symbol" in obj file on function that existed in lib file. i'm looking in filemon access to this lib, it's accessed and readed successfully. if i renaming this lib file, he throws this error anyway and filemon show that this lib is not found. looks like linker can't find function name in lib, but why? function is there

watcom has two kinds of libraries, register based libs and stack based (for calling convention). cant help without knowing the real error your getting. my guess is your tring to link against the wrong kinds of libraries. but, again, you need to paste the real output from wlink or wcl.

here is wlink message:

1Warning(1028): pciGetVendorName is an undefined reference
2Warning(1028): h3InitPlls is an undefined reference
3Warning(1028): _grSplashCb@24 is an undefined reference
4Warning(1028): guColorCombineFunction is an undefined reference
5Warning(1028): _printf is an undefined reference
6Warning(1028): _sprintf is an undefined reference
7Warning(1028): _malloc is an undefined reference
8Warning(1028): _free is an undefined reference
9Warning(1028): __imp__GetVersionExA@4 is an undefined reference
10Warning(1028): __imp__CreateFileA@28 is an undefined reference
11Warning(1028): __imp__CloseHandle@4 is an undefined reference
12Warning(1028): _getenv is an undefined reference
13Warning(1028): __imp__DeviceIoControl@32 is an undefined reference
14Warning(1028): __imp__OutputDebugStringA@4 is an undefined reference
15file pcibrd.obj(D:\3DFX\H5\DIAGS\MFTG\CORE\pcibrd.c): undefined symbol PCI_AGP_C
16MD
17Error(3137): too many errors encountered
18Error(E42): Last command making (mdc.exe) returned a bad status
19Error(E02): Make execution terminated

pcibrd.c has #include "fxpci.h"
and fxpci.h has
extern const PciRegister PCI_AGP_CMD;

that _printf is missing says your not linking in the base libraries. is your watcom environment strings setup correctly?

ohh also, your compiling windows source, __imp__GetVersionExA, is a win32 call. I guess I assumed you were doing DOS, but its win32. do you have all the win32 libraries installed and headers etc?

that PCI_AGP_CMD is inside a header but not being seen, its probably IFDEF'd out through another mechanism.

Can you compile a simple Hello world program that uses printf()?

I'm trying to compile program from old 3dfx sources.

Is it supposed to be DOS or Windows program? Are you building for the right target?
DOS binaries that default to DOS targeting are in BINW directory.

thank you guys for your attention. i'm using all files without changing em. all are original from 3dfx. looks like it's quite complicated programm that uses dos and windows modules.

may be you can take a look at this code mess: http://naviburg.ru/tmp/MFTG.rar
i run it by build.bat or wmake /f wmake.mak in core dir

compiling is not a problem, i think. obj files and lib files are compiled from c successfully. errors are from linker

I took a quick look, I cant build it because I dont have a windows install. It wants to run under nt/98 which none of my systems that have watcom on it are.

but, in the mftg directory run setenv.bat, then run clean.bat then build.bat

looks like you might need NMAKE from MSVC 4.2, as well as some other 3dfx sdk stuff. look in setenv.bat where its looking for headers and such.

i have calling setenv from autoexec. running clean.bat every time is not crucial, i presume, cause it removes obj and lib files, and on next run of build.bat it creates them again without any problems. nmake i have installed

i think openwatcom is able to assemble this exe file, but is has much more strict compiler. i've tryed it, but get too much errors

openwatcom doesnt ship with the win32 headers/libs etc unless something has changed. do you have your watcom environment setup? (LIB + INCLUDE environment vars)?

here is my setenv

1@echo off
2REM ------------------------------------------
3REM SetEnv.BAT SET UP 3DFX BUILD ENVIRONMENT
4REM for Voodoo4 Manufacturing Diags
5REM ------------------------------------------
6
7REM ------------------------------------------
8REM STORE THE PATH
9REM ------------------------------------------
10IF NOT "%OLDPATH%"=="" GOTO DONTSTORE
11SET OLDPATH=%PATH%
12:DONTSTORE
13
14
15REM ---------------------------------------------------------
16REM SET THE FOLLOWING VARIABLES (before attempting to compile
17REM ---------------------------------------------------------
18
19REM You must set NMAKE to the directory that contains nmake.exe
20REM from MSVC 4.2  (3Dfx always uses nmake for all builds.)
21set NMAKE=d:\msvc\bin
22
23REM You must set BUILD_DRIVE to the drive that you are building on ex:
24set BUILD_DRIVE=d:
25
26REM You must set BUILD_ROOT to the root of where you extracted your
27REM source kit to ex:
28set BUILD_ROOT=%BUILD_DRIVE%\3dfx
29
30REM You must set WATCOM to the location of your Watcom compiler files ex:
31set WATCOM=d:\watcom
32
33
34REM ------------------------------------------
35REM CHECK CRITICAL VARS
36REM ------------------------------------------
37IF NOT "%BUILD_DRIVE%"=="" GOTO DRIVEDEFD
38ECHO You must set the environment variable BUILD_DRIVE
39ECHO   to the driver letter of the source tree.
40ECHO eg. SET BUILD_DRIVE=d:
41GOTO END
42:DRIVEDEFD
43IF NOT "%BUILD_ROOT%"=="" GOTO ROOTDEFD
44ECHO You must set the environment variable BUILD_ROOT
45ECHO    to the root directory of the source tree.
46ECHO eg. SET BUILD_ROOT=\3dfx\devel 
47ECHO NOTE: BUILD_ROOT doesn't need a drive letter.
48GOTO END
49:ROOTDEFD
50IF NOT "%WATCOM%"=="" GOTO WATDEFD1
51ECHO You must set the environment variable WATCOM
52ECHO   to the install directory for Watcom
53ECHO   C/C++ 10.6 or greater
54ECHO eg. SET WATCOM=C:\devel\WATCOM
55GOTO END
56:WATDEFD1
57
58
59REM ------------------------------------------
60REM   SET COMMON VARS

61REM ------------------------------------------
62set MASM=d:\masm611
63SET BUILD_ROOT_H5=%BUILD_ROOT%\H5
64SET BUILD_ROOT_SWLIBS=%BUILD_ROOT%\swlibs
65
66SET PATH=%WATCOM%\bin95;%WATCOM%\binw;%OLDPATH%
67SET INCLUDE=%WATCOM%\H;%WATCOM%\H\NT;%INCLUDE%;%BUILD_ROOT%\H5\DIAGS\MFTG\3dfx\include
68REM SET INCLUDE=%INCLUDE%;%BUILD_ROOT_SWLIBS%\include\nmake;%MASM%\INCLUDE
69
70SET LIB=%WATCOM%\LIB386\DOS;%MASM%\lib;%INCLUDE%;%BUILD_ROOT%\H5\DIAGS\MFTG\3Dfx\lib
71
72SET FX_WATCOM_REG_CALL=
73set FX_GLIDE_HW=H5
74set FX_NO_GEN_BOF=1
75set GLIDE_INIT_HWC=1
76set FX_TARGET=DOS
77set FX_GLIDE_PACKET_FIFO=1
78set FX_INSTALL_DESTINATION=%STAGE_ROOT%\GLIDE\H5\DOS\DOSS\STATIC\ATRI\REL
79set FX_COMPILER=WATCOM
80set MKS_PATH=c:\DevTools\mks
81REM set PATH=%NMAKE%;%WATCOM%\BIN95;%WATCOM%\BINNT;%WATCOM%\BINW;%MASM%\BIN;%PATH%
82REM set INCLUDE=%WATCOM%\H;%WATCOM%\H\NT;%MASM%\INCLUDE;%INCLUDE%;%BUILD_ROOT%\3Dfx\include
83REM set LIB=%WATCOM%\LIB386\DOS;%MASM%\LIB;%LIB%;%BUILD_ROOT%\3Dfx\lib
84
85:END

and here is what watcom diag tool detects:

1Watcom                          Phone: (519) 884-0702
2415 Phillip St.                 Fax: (519) 747-4971
3Waterloo, Ontario
4CANADA    N2L 3X2
5
6------------------Watcom C Environment Variables ----------------
7WATCOM=<d:\watcom>
8EDPATH=<d:\watcom\EDDAT>
9INCLUDE=<d:\watcom\H;d:\watcom\H\NT;d:\watcom\H;d:\watcom\H\NT;d:\watcom\H\NT\DI
10RECTX;d:\watcom\H\NT\DDK;d:\3dfx\H5\DIAGS\MFTG\3dfx\include>
11LIB=<d:\watcom\LIB386\DOS;d:\masm611\lib;d:\watcom\H;d:\watcom\H\NT;d:\watcom\H;
12d:\watcom\H\NT;d:\watcom\H\NT\DIRECTX;d:\watcom\H\NT\DDK;d:\3dfx\H5\DIAGS\MFTG\3
13dfx\include;d:\3dfx\H5\DIAGS\MFTG\3Dfx\lib>
14PATH=<D:\WATCOM\BIN95;D:\WATCOM\BINW;C:\WIN_VIA;C:\WIN_VIA\COMMAND;C:\WINDOWS\CO
15MMAND;D:\WATCOM\BINNT;D:\WATCOM\BINW;C:\WIN12\COMMAND;C:\ULTRASND;C:\;C:\TBEACH\
16DOSAPPS;C:\DOS;C:\DISTRIB;C:\DN;C:\MSVC\BIN>
17TMP=<c:\temp>
18File 'd:\watcom\binp\ide.exe' has not been patched
19File 'd:\watcom\binw\ide.exe' has not been patched
20File 'd:\watcom\binnt\ide.exe' has not been patched
21File 'd:\watcom\binp\wbrw.exe' has not been patched
22File 'd:\watcom\binw\wbrw.exe' has not been patched
23File 'd:\watcom\binnt\wbrw.exe' has not been patched
24File 'd:\watcom\binp\wd.exe' has not been patched

just made test programm:

1#include <stdlib.h>
2#include <stdio.h>
3
4void main()
5{
6printf ("Hello World\n");
7exit(0);
8}

exe assembled without any problems

Which version of the Windows libraries are you using? Ones with Watcom, or a Windows SDK? If the latter, you may need to be careful about the version - old compilers need old SDK versions.

Looks like a library link issue, though, and make sure that all library types match i.e. trying to call a multithreaded library from a non multithreaded program.

libraries are from watcom cd. i'm agree that something strange with libraries. looks like linker don't see em. even warnings on printf

here is recommendations on buid.bat:

To compile you must:
- have watcom 10.4 - 10.6 installed and in your PATH
- be running under windows 95 or windows NT

and it's all

think i found a reason of this behaviour of linker. for example const PCI_AGP_CMD everywhere except lib file is written without underscore, but in lib file it with underscore _PCI_AGP_CMD. same for standart functions like printf. there are lots of this unmatched names of functions and variables. don't know how to normalize it without lots of manual editing

anthony wrote:

don't know how to normalize it without lots of manual editing

thats hardly the right way, you may, after an hour of editing, get into worse trouble;

i have to try it rather then keep looking on error messages

need an advice. have fuction calling grSplashCb in c file. in obj file it appears as _grSplashCb@24 and linker shows an error "undefined symbol _grSplashCb@24". in glide.h (https://sourcecodebrowser.com/glide/2002.04.1 … _8h_source.html 01127 line) i see this function declaration as grSplashCb. and no lib file with it. what should i do to avoid this error?