Hornpipe2 #1 Posted December 19, 2008 (edited) What are the ways to get the Atari online and talking to the Internet? I'd imagine that if you own one of the Atari modems, you could dial up an ISP with shell access, then from there use server-side apps to access the web (lynx, chat, etc). Is there a similar setup using an SIO2PC cable and a local machine? And, where can I find sample code on doing this kind of communication? Edited December 19, 2008 by Hornpipe2 Quote Share this post Link to post Share on other sites
charliecron #2 Posted December 19, 2008 You've pretty much got it. You can also just use a null modem with any of the various rs232 interfaces & a com program connected to local machine with a serial port running a getty or whatever, probably a linux box. Works well. I don't use it but I do believe you can use the sio2pc "ape telnet modem" to get out to the internet. Prob can telnet to a local machine as well? You'll also have to check out Fujichat, an Atari 8 bit irc client. Charlie Quote Share this post Link to post Share on other sites
Hornpipe2 #3 Posted December 19, 2008 Oh I see how that works - APE to emulate an 850 or 1030, where you put in your destination IP, and it bridges the Atari to IP for you. Quote Share this post Link to post Share on other sites
Marius #4 Posted December 19, 2008 And what about this one: Lantronix UDS-10 Quote Share this post Link to post Share on other sites
Hornpipe2 #5 Posted December 20, 2008 Any sample code to how SIO comms is done? BASIC preferred to assembler : ) Quote Share this post Link to post Share on other sites
Cybernoid #6 Posted December 20, 2008 check out: http://atari.hobby-site.com/ Quote Share this post Link to post Share on other sites
Hornpipe2 #7 Posted December 20, 2008 Thank you! One more question: is the modem or null-modem comms supported by the atari800 emulator for Linux? How about atari800win plus? Quote Share this post Link to post Share on other sites
Cybernoid #8 Posted December 20, 2008 (edited) Thank you! One more question: is the modem or null-modem comms supported by the atari800 emulator for Linux? How about atari800win plus? atari800win plus supports R: emulation, but the underlying code only supports accepting server socket connections. It is only really useful for BBS servers. However, on my site list above,you can make use of the sock_pipe.pl (in the zip file) perl script to create a socket pipe to "connect" the atari800win+ server to an "outgoing call". The atari800 emulator for Linux did at one point support R: emulation for both placing out going calls and accepting calls via socket, since I helped write that code way back in time, but I do not know if it is currently supplied with the source code. I just checked the atari800 2.0.3 release source code and it does contain the rdevice.[ch] files that I added and modified to the source tree. You may have to compile it yourself. I am not sure if the R: emulation is turned on be default in the executables. Edited December 20, 2008 by Cybernoid Quote Share this post Link to post Share on other sites
Hornpipe2 #9 Posted December 20, 2008 (edited) The atari800 emulator for Linux did at one point support R: emulation for both placing out going calls and accepting calls via socket, since I helped write that code way back in time, but I do not know if it is currently supplied with the source code. I just checked the atari800 2.0.3 release source code and it does contain the rdevice.[ch] files that I added and modified to the source tree. You may have to compile it yourself. I am not sure if the R: emulation is turned on be default in the executables. I downloaded the source and built an SDL version with --enable-riodevice. No luck in calling out though, it seems to wait on the "Dialing... [esc to stop]" status forever. Here's my Ice-T dialing screen - maybe the handler I have loaded is not the right one? Edited December 20, 2008 by Hornpipe2 Quote Share this post Link to post Share on other sites
Cybernoid #10 Posted December 20, 2008 Try with bobterm, too and see if it works... Quote Share this post Link to post Share on other sites
dwhyte #11 Posted December 20, 2008 I just checked the atari800 2.0.3 release source code and it does contain the rdevice.[ch] files that I added and modified to the source tree. You may have to compile it yourself. I am not sure if the R: emulation is turned on be default in the executables. It's turned off by default. You need to ./configure with the --enable-riodevice option. Quote Share this post Link to post Share on other sites
Hornpipe2 #12 Posted December 20, 2008 (edited) Getting closer: * configure with --enable-riodevice * go into the Emulator Config page and turn on r: emulation. Now I am getting modem debug on stdout. Unfortunately now Ice-T takes a long time to open (some kind of "gethostbyname" timeout). Then when I try to use ATDI to dial out to my target URL it immediately disconnects with "Write: Broken Pipe". It seems to restart in listen mode on port 9000 - sock_pipe.pl finds the emulator on port 9000 and takes the output, but I can't seem to link the output to another socket on the Web. R*: XIO 34 R*: XIO 38 R*: No ATASCII/ASCII TRANSLATION R*: XIO 36 R*: Open for Reading... R*: Open for Writing... R*: Socket mode. gethostbyname: Connection timed out connect: Operation now in progress R*: Connecting to k: R*: Negotiating Terminal Options... R*: XIO 40 R*: Entering concurrent IO mode... R*: Disconnected.... write: Broken pipe R*: ERROR on write. R1: Listening on port 9000... Edited December 20, 2008 by Hornpipe2 Quote Share this post Link to post Share on other sites
Hornpipe2 #13 Posted December 20, 2008 (edited) A quick printf addition to r_device.c shows that initial gethostbyname as attempting to connect to address "k:" at port 0. Huh? EDIT: BobTerm not working either. Each attempt at a Manual Dial just adds this to the log every few seconds: R*: XIO 36 R*: XIO 38 R*: No ATASCII/ASCII TRANSLATION R*: Open for Reading... R*: Open for Writing... R*: Socket mode. R*: Not in concurrent mode.... R*: XIO 34 R*: XIO 40 R*: Entering concurrent IO mode... Edited December 20, 2008 by Hornpipe2 Quote Share this post Link to post Share on other sites
danwinslow #14 Posted December 20, 2008 I wrote a library on the atari side in C that did IO across SIO and talked to a custom program on the PC side. The PC would do all the socket handling, and the packet data would go back and forth across SIO. It worked, but its pretty impractical at SIO speeds for what I wanted to do. Quote Share this post Link to post Share on other sites
Cybernoid #15 Posted December 20, 2008 Getting closer:* configure with --enable-riodevice * go into the Emulator Config page and turn on r: emulation. Now I am getting modem debug on stdout. Unfortunately now Ice-T takes a long time to open (some kind of "gethostbyname" timeout). Then when I try to use ATDI to dial out to my target URL it immediately disconnects with "Write: Broken Pipe". It seems to restart in listen mode on port 9000 - sock_pipe.pl finds the emulator on port 9000 and takes the output, but I can't seem to link the output to another socket on the Web. R*: XIO 34 R*: XIO 38 R*: No ATASCII/ASCII TRANSLATION R*: XIO 36 R*: Open for Reading... R*: Open for Writing... R*: Socket mode. gethostbyname: Connection timed out connect: Operation now in progress R*: Connecting to k: R*: Negotiating Terminal Options... R*: XIO 40 R*: Entering concurrent IO mode... R*: Disconnected.... write: Broken pipe R*: ERROR on write. R1: Listening on port 9000... Try doing what you did here to get to R1: Listening on port 9000. Then, on the local machine, do this command: "telnet localhost 9000". Then type CTRL-] and type "mode char" (for linux). Let me know what you get. I will get the latest sources and compile and try locally, but it will be a few days before I can debug... Quote Share this post Link to post Share on other sites
Hornpipe2 #16 Posted December 21, 2008 (edited) [email protected]:~/src/atari800-2.0.3/src$ telnet localhost 9000 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Connection closed by foreign host. I tried this several times. Finally it managed to connect. R1: Listening on port 9000... R1: Serving Connection from localhost. R*: Negotiating Terminal Options... Entering 'mode char' I think caused Ice-T to change from "Dialing..." to "_CONNECT 2400". Now I can pop back over to the Terminal window and send messages back and forth between telnet and Ice-T. Neat! I suppose I can fix up sock_pipe.pl to link port 9000 with the IGS web address and go from there. Edited December 21, 2008 by Hornpipe2 Quote Share this post Link to post Share on other sites
Cybernoid #17 Posted December 21, 2008 That is interesting that you need the sock_pipe.pl script. I tried this, albeit back in 2003, and ICE-T could make out going calls to IP addresses. Did you put the port number on the address like this: "ATDI some.ip.com 23"? Quote Share this post Link to post Share on other sites