|
Post by RaymondDay on Nov 1, 2005 13:14:29 GMT -5
Wow I just tested logging off Q-Link it goes right to BASIC with F5 just like the old Q-Link did! That's nice. O this is using tcpser.
|
|
|
Post by RaymondDay on Nov 2, 2005 4:57:18 GMT -5
I wanted to test tcpser using two at the same time with 2 RS232 ports com 1 and com 2.
I did this command for com 2:
./tcpser -d /dev/ttyS1 -s 2400 -i"e0&k0&c0" -tsSiI -l 7 -n"5551212"=qlink.quantum-link.org:5190
But it will come back and say this:
2005-11-02 04:44:28:-1208674624:DEBUG:Binding server socket to port 6400 2005-11-02 04:44:28:-1208674624:FATAL:Server socket could not be bound to port (Address already in use)
Am I doing any thing wrong? This is 2400 baud because using Turbo232 for this 2nd one. This is all ready with the 1st one running too. I guess I should test with out the 1st one running.
I did test it out with out the 1st one running and it works. So I know I have both RS232's hooked up right. Whey would it say address already in use when I type /dev/ttyS0 and /dev/ttyS1 for the 2nd one?
Works real good at 2400 baud and Turbo 232 cart. Stall goes back to BAISC after you log off too. tcpser is the only one I found that lets you do that!
|
|
|
Post by RaymondDay on Nov 2, 2005 22:01:56 GMT -5
It works with 2 at the same time! Thanks to Jeff or "Jefferysto" on Q-Link reloaded. I was talking to him and he said use -p 6401 in the 2nd one. I did and I can get on with 2 commodores at the same time using both RS232 ports on the Fedora Linux and tcpser!
Here is the command I did for the tuber232 cart. at 2400 baud on the 2nd com port.
./tcpser -d /dev/ttyS1 -p 6401 -s 2400 -i"e0&k0&c0" -tsSiI -l 7 -n"5551212"=qlink.quantum-link.org:5190
I am on Q-link now with both of them at the same time using just one PC Linux and 2 RS232 ports on it. One 1200 baud and the other 2400 baud.
Thank you Jim for making tcpser. It works real good if you know how to install it and work it.
I love how it will let you go to basic, don't have to reset. It's good to how you don't have to restart tcpser after you get off and back on.
Now all I have to do it set up my Q-Link to auto dial 555-1212 and it should connect to Q-Link reloaded with out me typing any thing just like it auto connected on the old Q-Link.
It does auto connect just like it does on the old Q-Link! I just picked the 2nd modem at the bottom for "MODEM TYPES" the modem is "Hayes or Hayes-compatible" I just have to load Q-Link and it auto connects now using tcpser. The access number is 5551212 same as I put in the command to start up tcpser.
|
|
|
Post by RaymondDay on Nov 3, 2005 15:38:21 GMT -5
I moved tcpser over to my Fedora core 4 that I been running from core 3 I think. It's in the middle of my 2 commodore setups. So it's easy to run RS232 cords to it and have them out of the way. I did not use this at 1st because I had no RS232 on it. I had to make holes in the sheet metal in back to mount them. So before I did it I tested that I could get it working on a new load. On another system.
When I ran this on the Fedora I been running for more then a year it got a error on Com 1. I would get a error after a wile. I could not be on Q-Link for more then a hour. This is the error:
"FATAL:Could not obtain serial port status (Input/output error)"
I did not get this on the new Test load of Fedora.
I did use another ribbon cable to 9 pin D-Sub. I had another and switch it. But I got the same thing. I found out with webmin show running processes that there was something all ready using com port 1. It showed it like this:
"/sbin/mgetty -r -s 1200 ttyS0"
I found out mgetty is a fax program. I just could not stop it. I then edited inittab and put a # at the start of lines that had getty in them. 7 lines. I rebooted and then mgetty was not running any more.
I have been on Q-link reloaded using com port 1 now for over a hour and I have not got a error.
If any one does this use just com 2 or stop mgetty. There my be other ways to fix it besides just stopping it. Maybe when tcpser is running don't run it. I don't know.
I been on Q-Link with this tcpser for more then 8 hours now with both real commodores. It's working super good. I left my Turbo232 run all night. When I logged off this morning it said I was on more then 15 hours. It was still working only one other person was on Q-Link when I got off. Not Jim but JefferyAFK after his name saying he was Away From Keyboard.
With being on for over 15 hours I am sure tcpser is working very good.
|
|
|
Post by RaymondDay on Nov 4, 2005 19:26:09 GMT -5
Thanks to "Niedobry2" on Q-Link. He showed me what to do to get tcpser to start on boot. Here is what I did:
cd /etc/rc.d/rc3.d/ vi S99local
Then I just typed "a" in vi editor and I can type in like commodore basic. I can cut and paste too. Then when I am done I just do a ":sq" it saved the file then I did a reboot and got on Q-Link with my commodore so it worked. Here is the S99local file what it looks like now on my Fedora core 4 Linux. Starting at the #!/bin/sh
#!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff.
touch /var/lock/subsys/local /mystuff/commodore/Q-Link/tcpser-1.0rc10/tcpser -d /dev/ttyS0 -s 1200 -i"e0&k0&c0" -n"5551212"=qlink.quantum-link.org:5190& /mystuff/commodore/Q-Link/tcpser-1.0rc10/tcpser -d /dev/ttyS1 -p 6401 -s 2400 -i"e0&k0&c0" -n"5551212"=qlink.quantum-link.org:5190&
Thank you Brian or Niedobry2 on Q-Link.
|
|
|
Post by RaymondDay on Nov 5, 2005 7:57:11 GMT -5
If any one wants to know what I am running tcpser on it's the little blue box I brought to the Expo because it has a Web page and if we would not get on the Web I could use the Palm Ethernet Cradle to get to it's web page. I posted about this at: cmdrkey.com/forum/viewtopic.php?p=679#679It's a nice little Linux server to run tcpser on. You can see what it looks like in this photo here. It's next to my 128. Here is a new photo of it. The back side were I put the 2 RS232 ports. It's in a small baskit that hang on the buttum of a shelf I have about 7 feet up on the wall.
|
|
|
Post by RaymondDay on Nov 7, 2005 12:09:48 GMT -5
What would be the best smallest easiest Linux to just use tcpser on? I tested this with Trustix 3.0-mini. I had to do these things after it installed with in 5 min. The things are this: swup --install make swup --install gcc swup --install wget wget www.jbrain.com/pub/linux/serial/tcpser-1.0rc10.tar.gzgzip -d tcpser-1.0rc10.tar.gz tar -xvf tcpser-1.0rc10.tar cd tcpser-1.0rc10 make But it came up with lots of errors. I guess it still needs something else installed. It did not even make the tcpser file so I could run it. It may be good if some one could just make a boot Linux CD with tcpser all ready on it that done not install on a hard drive.
|
|
|
Post by RaymondDay on Nov 15, 2005 4:55:04 GMT -5
You can have tcpser work with a USB to RS232 adapter. In my Fedora Linux were I have tcpser running I did this command to find out what port the adapter is on.
dmesg
Looking at the text I seen this:
usb 2-2: PL-2303 converter now attached to ttyUSB0
I replace the start line /dev/ttyS0 with /dev/ttyUSB0 and it works.
It was hard to find if it even know the USB was there and if so what dev it would be. the dmesg told me all that. I looked on google for about 2 hours to find how you find a USB to RS232 adapter. I did not even find it that way.
That's why I wanted to post it here to help others not go though this to find it.
I can be on at the same time using 3 real commodore setups.
I guess if you wanted a BBS using tcpser you could even add a USB hub to get more with a RS232 adapter. I think some BBS's were set up to use more then one phone line back then.
|
|
|
Post by Jeff Ledger on Nov 15, 2005 10:45:51 GMT -5
Thats cool!
Thanks for posting that!
Looks like the only limitation to the number of serial ports is the limit of usb plugs to plug into.
Anyone got any sources for cheap USB<-->Serial converters?
Jeff
|
|
|
Post by RaymondDay on Nov 15, 2005 15:43:44 GMT -5
|
|