+Stephen Posted October 8, 2013 Share Posted October 8, 2013 You're on a roll! I'll give this a good testing this evening. Thanks for the continued updates. 1 Quote Link to comment Share on other sites More sharing options...
Lord Cygnus Posted October 10, 2013 Share Posted October 10, 2013 PRCONN.HND is similar (or perhaps identical?) to ATARI850.HND. It's a very small executable that contacts the PRC, downloads a handler that is stored on the PRC's internal ROM and installs that as an R: handler. After the PRC was released it was discovered to be incompatible with some misbehaving terminal program popular at the time (HomeTerm) and so a purely disk based handler, with some workaround built in, was released. It is named PRC.SYS on the disk that came with the PRC and named PRCONN2.HND here. You will notice that it's a much larger file than the PRCONN.HND. Since this file is a workaround for some problematic terminal program that does not interest us today, I am considering dropping this file from future Ice-T releases. Please try 2.75 with PRCONN.HND and let me know if it works so I can get rid of PRCONN2. Yes, Itay ("it tie"), you are right. PRCONN.HND works fine with ICE-T 2.75 in both SpartaDOS and RealDOS. You can get rid of PRCONN2.HND. I'm able to call Atari, TI99, Commodore, and PC boards in 40/80 columns ASCII/ANSI really well. I'm impressed. So, you suggest I move on to your latest release 2.76 now? -=[Lord Cygnus]=- 1 Quote Link to comment Share on other sites More sharing options...
Lord Cygnus Posted October 10, 2013 Share Posted October 10, 2013 Itay, do you call up any BBS'es through telnet? If so, which boards are you on and what is your username? -=[Lord Cygnus]=- Quote Link to comment Share on other sites More sharing options...
itaych Posted October 10, 2013 Author Share Posted October 10, 2013 Of course I want you to move on to 2.76. I post these new versions because they are (hopefully) better than the older versions and because I want to hear feedback from users before making an official release. Please do get the latest beta and let me know if it works for you and whether you notice any difference, for better or worse. And sorry, no, I've never been much of a BBS user myself. I started with a Unix shell account and later moved on to dial-up Internet. Quote Link to comment Share on other sites More sharing options...
David Baldwin Posted October 10, 2013 Share Posted October 10, 2013 I have used ICE-T 2.76 beta 3 with Altirra 2.30 ICE-T worked good did not fail I was dialing into the big synchronet bourds reading through the message's ICE-T handled it good I will keep testing. David Baldwin Quote Link to comment Share on other sites More sharing options...
Lord Cygnus Posted October 10, 2013 Share Posted October 10, 2013 Itay, I made a revised demo video of ICE-T 2.75 on my Atari 130XE system. I made my corrections Hopefully, I pronounced your name better this time! [media=420x315] [/media] -=[Lord Cygnus]=- I will download and install version 2.76 and post results soon... Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted October 10, 2013 Share Posted October 10, 2013 Itay, I made a revised demo video of ICE-T 2.75 on my Atari 130XE system. I made my corrections Hopefully, I pronounced your name better this time! Do you have a wiring plan for that Lantronix to DB9 serial cable in your video? I had about three goes at making one for my P:R: Connection and it never worked. Quote Link to comment Share on other sites More sharing options...
itaych Posted October 10, 2013 Author Share Posted October 10, 2013 Hopefully, I pronounced your name better this time! Haha, wrong again When I say "It-tie" think of the word "It" followed by the word "tie" (as in, tie a knot). "It, tie". Although the preferred version would be like saying the name of the letter E followed by the word "tie". I remember early versions of Linux tested the sound card by playing a clip saying "Hello, this is Linus Torvalds, and I pronounce Linux Linux". Maybe I should do that too Quote Link to comment Share on other sites More sharing options...
itaych Posted October 10, 2013 Author Share Posted October 10, 2013 (edited) Since I haven't received any complaints about the new beta, and as I am quite happy with it so far, it is now out as an official version here. Edited October 10, 2013 by itaych Quote Link to comment Share on other sites More sharing options...
Lord Cygnus Posted October 13, 2013 Share Posted October 13, 2013 Do you have a wiring plan for that Lantronix to DB9 serial cable in your video? I had about three goes at making one for my P:R: Connection and it never worked. Lantronix Device (DB25 connector) <> P:R:Connection (DB9 Connector) DB25 Pin #2 is Transmit connected to DB9 Pin #3 Transmit DB25 Pin #3 is Receive connected to DB9 Pin #4 Receive DB25 Pin #7 is Ground connected to DB9 Pin #5 Ground I went to Radio Shack and bought the DB25 connector (male) and the DB9 connector (male). I used a CAT5 network cable for the wire. Works great! -=[Lord Cygnus]=- 1 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted October 13, 2013 Share Posted October 13, 2013 Lantronix Device (DB25 connector) <> P:R:Connection (DB9 Connector) DB25 Pin #2 is Transmit connected to DB9 Pin #3 Transmit DB25 Pin #3 is Receive connected to DB9 Pin #4 Receive DB25 Pin #7 is Ground connected to DB9 Pin #5 Ground I went to Radio Shack and bought the DB25 connector (male) and the DB9 connector (male). I used a CAT5 network cable for the wire. Works great! -=[Lord Cygnus]=- Excellent - thanks! Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted October 20, 2013 Share Posted October 20, 2013 Although the printer works fine with my P:R: Connection, I still can't get ICE-T to work with it via the Lantronix MSS-100. Starting to think the PRC itself has an issue, then I discovered this review: http://www.page6.org/archive/issue_30/page_74.htm My PRC has a 4.000 MHz crystal. Could that perhaps be causing problems with RS232 (on PAL machines)? Quote Link to comment Share on other sites More sharing options...
Lord Cygnus Posted October 21, 2013 Share Posted October 21, 2013 (edited) Although the printer works fine with my P:R: Connection, I still can't get ICE-T to work with it via the Lantronix MSS-100. Starting to think the PRC itself has an issue, then I discovered this review: http://www.page6.org/archive/issue_30/page_74.htm My PRC has a 4.000 MHz crystal. Could that perhaps be causing problems with RS232 (on PAL machines)? The pinouts for the ICD P:R:Connection (R1:) on the DB9 connector are: Pin # 3 - Transmit (XMT) Pin # 4 - Receive (RCV) Pin # 1 - Data Terminal Ready (DTR) Pin # 2 - Signal (Carrier) Detect (CRX) Pin # 6 - Data Set Ready (DSR) Pin # 7 - Request to Send (RTS) Pin # 8 - Clear to Send (CTS) Pin # 5 - Signal Ground (GND) The usual RS232 pinouts on the DB25 side are: Pin # 8 - Data Carrier Detect (DCD) Pin # 3 - Receive Data (Rx) Pin # 2 - Transmit Data (Tx) Pin # 20 - Data Terminal Ready (DTR) Pin # 7 - Signal Ground (GND) Pin # 6 - Data Set Ready (DSR) Pin # 4 - Request to Send (RTS) Pin # 5 - Clear to Send (CTS) Pin # 22 - Ring Indicator (RI) -=[LC]=- Edited October 21, 2013 by Lord Cygnus 1 Quote Link to comment Share on other sites More sharing options...
flashjazzcat Posted October 21, 2013 Share Posted October 21, 2013 Thanks! I'm still a bit spooked about that 4MHz crystal / PAL issue mentioned in the review, but there's very little information on the PRC to be found. Quote Link to comment Share on other sites More sharing options...
freetz Posted June 1, 2014 Share Posted June 1, 2014 Hi Itay, first of all thanks for this great program! I have a little bit of a problem of getting it to work though: My setup: ATARI 800XL (PAL) with 512kB RAM -> P:R:-Connection Cable -> CX87 modem cable -> Lantronix UDS-10 -> Internet When I use Bobterm, this setup works and I can connect to a Telnet-based BBS using the ATDT commands of the Lantronix using the pre-defined 9600 Baud. However, I need to set translation to ASCII, ATASCII or VT52 won't work. In Ice-T, I only have the option of VT100 and ANSI-BBS (the latter one I'd really like to use), but then nothing is being echoed and no reaction can be seen. Once I managed to get at a stream of random characters to be dumped on the screen, but nothing else but garbage. The same result happens when I use my SIO2PC cable and connect it to the ATARI and then use SIO2OSX's 850 emulation: Again it works fine with Bobterm in ASCII mode, but not in any other mode and therefore not at all in Ice-T. Do you (or anyone else) have an idea how to address this issue? I'd love to be able to use the 80 column feature of your great little gem ! Thanks again for all your efforts, F. Quote Link to comment Share on other sites More sharing options...
Marius Posted June 1, 2014 Share Posted June 1, 2014 Hi F. Please note there is a newer beta of ICET-T somewhere here on the forum. It's in the 2.76 thread, and the beta is 2.80 IIRC. Then: could you investigate WHY it works in Bobterm. Is there a chance that you have exotic start/stop bits configured there? You should set it to 8N1. So baudrate, start/stopbits, parity etc. should match. What DOS are you using? Are you using your brand-new MyIDE 2 interface? ICE-T doesn't work under MyBIOS -Flash version (yet). I hacked ICET280 into something that works more-or-less with MyBIOS. The RE and R2 versions of MyBIOS are compatible with ICET though. Also runs ICET on SDX, and SDX can be run on MyIDE too, but then you have to use the APT feature and configure at least one APT partition with FJC's FDISK. Quote Link to comment Share on other sites More sharing options...
freetz Posted June 1, 2014 Share Posted June 1, 2014 Hi, thanks for the suggestions, I've used 8N1 in both configurations (as far as it's configurable) and I'm using ICE-T 2.76 XE from an ATR which comes with MyDOS. I do not use it in conjunction with my MyIDE-II cart. I'll give it a try with ICET280 once I'm back on my real ATARI (which will be on Wednesday), maybe that helps. But I still assume it's more of a translation thing, because also Bobterm doesn't work properly when not set to ASCII, and as ICE-T doesn't have ASCII as a translation option, I thought that could be the reason (although I can't explain to my self why this should make a difference). Best, F Quote Link to comment Share on other sites More sharing options...
itaych Posted June 1, 2014 Author Share Posted June 1, 2014 Scroll up. There are people discussing problems using the PRC with a PAL machine, perhaps that's your problem too? Other than that please try other terminal software (Flickerterm for example) - do they work? Please try the latest 2.8.0 alpha and take this to the 2.76 thread. I wish it was possible to lock old threads... Quote Link to comment Share on other sites More sharing options...
freetz Posted June 1, 2014 Share Posted June 1, 2014 Ok, sorry for spawning and thread. But as I've written up above, the assumed PAL-problem does not apply as the cable and everything work fine with Bobterm. I'll switch to the 2.76 thread once I've tested 2.8alpha. Quote Link to comment Share on other sites More sharing options...
itaych Posted June 1, 2014 Author Share Posted June 1, 2014 Actually I have a better idea for you. I'm attaching SPLAT.BAS. This was the very first proof of concept I did in 1992 or so before starting Ice-T - a dead simple Atari BASIC program that opened the serial port in 300 baud and let you communicate with whatever's on the serial port (modem in my case). What you can do with it is play freely with the XIO commands, twiddle the settings and figure out what's wrong with your setup. Open the PRC manual (it's on Atarimania if you don't have it), read about the XIOs to understand the port opening sequence, and try to figure out what's wrong. I believe I enabled ATASCII/ASCII translation here so I wouldn't need to code the translation in BASIC, so try disabling that and see what happens (you'll have to press ctrl-J or ctrl-M instead of Return to send an end of line, but it should still *work*). In Ice-T this is of course disabled. Also if you change the baud rate to 9600 you will lose data but you should at least see parts of valid text. Let me know what you discover. SPLAT.BAS 2 Quote Link to comment Share on other sites More sharing options...
freetz Posted June 1, 2014 Share Posted June 1, 2014 Ok, thanks, will do so on Wednesday when I'm back on my real ATARI ! Quote Link to comment Share on other sites More sharing options...
Marius Posted June 3, 2014 Share Posted June 3, 2014 I love the name SPLAT very much for a Terminal. 1 Quote Link to comment Share on other sites More sharing options...
freetz Posted June 5, 2014 Share Posted June 5, 2014 Hi again, ok, after adding a XIO 36,#2,14,0,0,"R:" in order to set the baud rate to 9600, Splat runs perfectly fine and I communicate without any problems with the Lantronix Device. When I set XIO 36's translation Aux1-byte to 16, I do not get line-feeds and with Aux1 set to 32, I need to press Ctrl+J/M, just as you mentioned above. At all times I do get an echo which I don't get with Ice-T. Since Splat uses ASCII/ATASCII translation (same as Bobterm which is working for me as well), I assume it's some problem of translation? Will try 2.8beta soon, didn't manage to find a floppy disk to copy it to because SIO2PC and PR-cable don't work together unfortunately... Frederik Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.