Post by discmaster1 on Sept 17, 2007 5:27:39 GMT -5
I wanted to ask if anyone here might be using or might have used TCPSER by Jim Brain? I'm trying to setup my 4 node PC DOS BBS and I'm doing so by having a high speed 4-port serial board in my Windows PC that connects over to a 4-port jigh speed serial board in my 486 (BBS) PC.
I've tried Leif's TellBBS program, and it worked fine until I tried uploading or downloading. For some reason none of the supported tranfer protocols worked. I don't know if it was the protocols that were the problem...actually it probably wasn't, but it appears a problem with the program handling file transfers. The transfers would get up to about 4% and then CRC errors would flood the transfer forcing the BBS to retry the transfer. I tried all speeds of connection from 2400-115000.
Anyhow, it was suggested that I try Jim Brain's TCPSER. The only problem is that there wasn't any documentation and it is command line based. I did try to have it setup, but I couldn't figure it out exactly. I wanted to ask if anyone here might have experience with it and if they could PM an example batch file to invoke TCPSER. I'd like to see how the batch file would call TCPSER and activate 2 - 4 nodes (serial ports). I did read on one of Jim's postings that to initialize TCPSER for more than one node does not require multiple instances of TCPSER. A single instance can handle all multiple connections. I hope someone here might be able to help me.
Post by Pinacolada on Apr 17, 2008 15:06:19 GMT -5
Still have trouble with tcpser?
I found out there's release candidate 12; so I upgraded from 10. There are virtual ports available now, no actual cable needed anymore - neat since I'm just attempting to connect to QLink and/or BBS's using VICE in Debian Linux.
However, I keep getting the following:
./tcpser -v 25232 2008-04-17 13:06:38:-1210378560:FATAL:Server socket could not be bound to port (Address already in use)
(This is without VICE running.)
I guess I'll email Anthony Tolle, who came up with the IP232 port option.
Last Edit: Apr 17, 2008 15:07:28 GMT -5 by Pinacolada
Post by Pinacolada on Apr 17, 2008 17:06:41 GMT -5
Well, fiddling around on my own, I discovered I need to be root (in Linux), make sure there are no other instances running, then it starts. Still no clue how to connect VICE and tcpser though... I know it's got to be somewhere in RS232 settings. In Windows you had the option to select the IP address and port; I don't see how to in Linux. :/
./tcpser -v 25232 -p 6400 -l4
Bit more informative!
./tcpser -v 25232 -p 6400 -l4 2008-04-17 15:00:40:-1209575744:INFO:Server socket bound to port 2008-04-17 15:00:40:-1209575744:INFO:Server socket listening for connections 2008-04-17 15:00:40:-1209575744:INFO:Opening ip232 device 2008-04-17 15:00:40:-1209575744:INFO:Server socket bound to port 2008-04-17 15:00:40:-1209575744:INFO:Server socket listening for connections 2008-04-17 15:00:40:-1209575744:INFO:ip232 device configured 2008-04-17 15:00:40:-1217967184:INFO:Control Lines: DSR:1 DCD:0 CTS:1 2008-04-17 15:00:40:-1217967184:INFO:Disconnecting modem 2008-04-17 15:00:40:-1217967184:INFO:Disconnecting 2008-04-17 15:00:40:-1217967184:INFO:Control Lines: DSR:1 DCD:0 CTS:1
Well, I just discovered from Jim that VICE takes domain names instead of IP addresses, which is (I believe) an undocumented feature. That is nice. I'll have to tinker with Windows VICE for a bit, since I'm stuck with that stupid broken pipe error in Linux.