China DOS Union

The following is quoted from tiannomad's post at 2004-4-2 22:35:28:
I'm using Waterloo TCP/IP for development on pc104. The client side is nt4.0, and the
problem is that there are network interruptions. The DOS server side has multiple serial ports (four 232 and one 422), and communication uses polling, while one parallel port uses interrupts. Experts, please point me in the right direction! Why?

jia

Expert, do you have any results now? I'm also interested in DOS-based industrial-control tpc/ip

Could you upload some useful stuff? I'm really frustrated too. How do you write this stuff?

tiannomad
Brother:
You really are an expert.
I'm using an Advantech industrial-control PC too, and also need to use tcp/ip to communicate with Windows.
I don't have the slightest clue!
Brother, please help!!
QQ: 810275

Has anyone used pc/tcp?

I want to learn this too
But I don't have much DOS foundation
Not sure whether I can join your discussion group

I'm using Waterloo TCP/IP for development, with a highly cost-effective DOS platform.

The reason for the network interruptions may be that when communicating with the serial port, you didn't add tcp_tick in the serial communication statements, so during that time the program can't process network information, causing the network interruption. The solution is to add tcp_tick inside the loop of the serial communication statements, or write a timer interrupt to generate tcp_tick at fixed intervals, giving the program a chance to process network information.

Could one of the experts write a dedicated tutorial? Otherwise there's really no way to get started!

I'm here too, everyone talk more, I'm a newbie!

My DOS can now run DSOCK TCP/IP applications on a desktop machine, I'm happy! (INTEL PIII ,REALTEK8139) These past few days have really worn me out.

For SQL DBLIB/c database access, I just want TCP/IP networking. Under DOS, what's a good way to use the least memory? Has anyone used ftp's pc tcp? For discussion contact: daysoft@szonline.net thanks.

Has the poster above implemented Waterloo TCP/IP on a DOS machine with dual NICs?

Looks like quite a few people have the same idea as me! I also want to do network development under DOS, but I don't have the hardware, only one computer. Right now I'm thinking of using VMWARE to emulate networking, and I'm testing it! Please give me some pointers! email:cqjjhsj@163.com

I've finally found the organization. I've been searching online for a long time, and only now found out there are so many people working on this stuff too. The PC104 I'm using is from SBS, and the development kit was provided by them too, but there is hardly any documentation, and there are tons of problems. Let's discuss it, I'm getting depressed to death over this

I'm engaged in TCP/IP design work under DOS (the client side is diskless)

I've been doing it for a while.

For easier management, the customer wants diskless DOS clients,

and then the clients use TCP/IP to communicate with the Windows2000 server side.

Right now I'm looking for materials related to 256-color programming under Dos

using TC3.0 and Svga.bgi.

I don't know who can help a little.

If anyone needs materials related to Tcp/ip under Dos, you can contact me.