China DOS Union

Dear masters, I want to use Borland C 3.1 to implement TCP/IP communication under DOS, but why can't I connect? The error message is prompted: Linker error: Bad Object File Record in module? Thanks~

Yeah, yeah,

I also use BC3.1 and WATTCP, but just can't connect.

Don't know how to set it up? Don't know what your path is, upstairs? How to set it? Also, does your WATTCP have a connection library? Mine doesn't seem to have a connection library.

In a hurry~ Contact more frequently~

It's like this whether using the command line or connecting in the established project. Connecting other *lib works, but connecting wattcphg.lib doesn't (huge mode). It's very strange~~

Hope everyone comes to speak

1, In WATTCP\apps\ping.c, I use BC31 to build a project.
2, Compilation passed
3, Linking error. The prompt information is as follows:
Linke Error:Under find symbol _chk_ping in module......
There are 11 such Messages in total.

Please, moderator, help me. What should I do?
I have unhesitatingly copied all 3.libs in WATTCP\lib\ to BORLANDC\lib. Copied all necessary header files in WATTCP\include to BORLANDC\include.

Please don't hold back on the technology, everyone carry forward the FreeSoft spirit.

Let's see if we can connect using DJGPP C/C++.

It seems that you need to use tlib to add *.lib to the library, right?

to－－》Wengier
I don't know anything about DJGPP C/C++. I'm not sure if it's possible. Have you tried it, moderator?
I still hope to use BC3.1. I hope there are other tips.
to－－》LanE,
I tried Tlib and it does run. I used tlib WATTCPSM.lib +, I don't know if this is correct? But it's still the same.

I don't know what to do next? So to speak. If this problem can't be solved in this forum, I think the DOS forum still doesn't have deep things. After all, writing network programs under DOS is a better choice for real-time control systems. And other things like drawing programs are all relatively simple programs, and currently have little practical value.

Please feel free to give suggestions...

This library should be compatible with Borland C 3.1. There are ASCII codes of Borland C and Turbo in its header. Although you don't need to create a project file to link after using tlib, the linking error still occurs: Linker error: Bad Object File Record in module. It seems that this library needs special handling? Pondering~~~

Indeed, it is as you said.

But now I have already connected. Still using the make program. But I need to modify the mkefile file to use the Large mode. Modify two lines in the makefile under \apps to:
DEBUG= D # set to D for disable, E for enable
MODEL= L # set to L for large, S for small
In this way, the mode is Large.
And the Large library is obviously good. The connection passed. It shows that there is a problem with the Small library. I don't know if the WATTCP moderator did it on purpose or by accident.

1. Now the question is how to use the library in the BC3.1 project file?
2. Many TCPSOCK functions are completely different from WINSOCK functions. I don't know how to use them. I wonder if anyone has a function manual? It's very strange that I have also seen the WATTCP program before, and the usage of the library functions is the same as that of WINSOCK.

It should mean that changing MODEL=L to MODEL=S can use the small library. There are three files in the LIB directory, which should be the lib files of the small, lager, and huger modes...

是的，the 3 files under the lib correspond to these 3 modes. Now the problem is that it still fails to link when adding any WATTCPLG.LIB to the PRJ project file.

1. Where is the make syntax manual?
2. Who has the manual of the WATTCP function library? It costs $50 on www.wattcp.com. I can spend 100 yuan. Once I receive the function library manual, I will pay immediately.

The following is the statement quoted from The Horse with Glasses on 2003-7-2 16:32:41:
Indeed, it is as you said.

make really works , and I tested the huge mode again and it passed, proving that at least lage and huge are definitely usable
Establishing the project file and adding other link libraries can pass, indicating that the connection method should be no problem. The error when adding wattcp may be due to an improper debug option in the makefile
But the error was not eliminated after disabling the debug setting in the option. Hope everyone can give some guidance

Take a look at the syntax of makefile here:
http://www2.zzu.edu.cn/ie/newdos/dispbbs.asp?boardID=6&ID=4258

to->>Qiuchan
Yeah, adding the library to the project file just doesn't work, I don't know why? If you've succeeded, could you please write the steps here?

to->>Wengier
Thank you, but this Make manual seems a bit too complicated. And it doesn't match the makefile of WATTCP.

Ladies and gentlemen:
1, Who has used the functions of WATTCP, what are the steps? For WINSOCK, you create a SOCKET, CONNECT, and then you can SEND. But how about WATTCP?

tlib should add .obj files to the library.
tlib ww.lib +a.obj