w1k Posted April 17, 2012 Share Posted April 17, 2012 thank you Quote Link to comment Share on other sites More sharing options...
Fox-1 / mnx Posted April 17, 2012 Share Posted April 17, 2012 Ice-T XE 2.73 is hereby unleashed unto the unsuspecting public. Very appreciated. Gave it a quick go with an emulator and seems to work o.k. Need to install it on the real set-up to test some more as I usually don't do emulators. I noticed it's still showing the same strange behavior on some ANSI codes as the older versions did. My BBS supports ANSI emulation but when used with Ice-T the CLS command acts up. This, however, may be caused by some slight differences in the ANSI code implementation. All I know is that it looks o.k. when using HyperTerm on windows i.e. Nothing too serious. The text is still readable :-) Quote Link to comment Share on other sites More sharing options...
itaych Posted April 17, 2012 Author Share Posted April 17, 2012 I noticed it's still showing the same strange behavior on some ANSI codes as the older versions did. Of course it does. Look at the What's New list. There is no claim there about any changes made to the terminal emulation parser, and so it should be of no surprise that no change is observed. Regarding the CLS issue, I quote from icet.txt: Emulation: Choose VT-102 or ANSI-BBS. I only know of one difference between these two (ANSI homes the cursor when clearing the screen, VT-102 does not). If you haven't tried both settings of "Emulation", please do. If this still doesn't help you, and you have any further specifics about this problem, such as a way to reproduce it or information on the code that I may not have properly implemented, please fill me in. I wrote Ice-T based on specifications of the VT-100 standard, which is what is used by Unix based shells but not exactly the same as that used in BBS's - and I haven't found any documentation about the latter. Let me know if there's anything you know. Quote Link to comment Share on other sites More sharing options...
Fox-1 / mnx Posted April 17, 2012 Share Posted April 17, 2012 Of course it does. Look at the What's New list. There is no claim there about any changes made to the terminal emulation parser, and so it should be of no surprise that no change is observed. I didn't say I expected a change. Just a note. If you haven't tried both settings of "Emulation", please do. If this still doesn't help you, and you have any further specifics about this problem, such as a way to reproduce it or information on the code that I may not have properly implemented, please fill me in. I'm not sure you are the one who implemented it wrong. It could also be my BBS that implements some things different or wrong. It's not that CLS just doesn't wipe the screen but sometimes strange characters appear or disappear around a CLS instruction. A small example: [255D [0;1mTEXT &00 The "TEXT" part of this will be shown on the screen only when connected with Ice-T in both translations. When using HyperTerm the "TEXT" won't be shown, which is the way I intended. Quote Link to comment Share on other sites More sharing options...
itaych Posted April 17, 2012 Author Share Posted April 17, 2012 Esc[255D will send the cursor back (left) 255 positions, this is like a carriage return. Esc[0;1m will reset the text rendition, then switch to boldface. So, the TEXT will appear in bold at the left side of the screen. What's the &00 supposed to do? Quote Link to comment Share on other sites More sharing options...
Fox-1 / mnx Posted April 18, 2012 Share Posted April 18, 2012 (edited) Esc[255D will send the cursor back (left) 255 positions, this is like a carriage return. Esc[0;1m will reset the text rendition, then switch to boldface. So, the TEXT will appear in bold at the left side of the screen. That's exactly what it does with Ice-T. edit: TEXT shows up at the position where the cursor happens to be so it'll not move to the left. What's the &00 supposed to do? I tested some more and the &00 is a thing that's causing the difference. &00 Is the pro-BBS code that clears the screen. It'll internally be translated to the right CLS code for the current translation a user is logged in with (ATASCII/ASCII/ANSI/VT52-mono/VT52-color/IG/CGS). TEXT is a tag for internal usage by the BBS. It's used in some places as an identifier of what's coming next. Since the TEXT and &00 are very close together it's just not visible when a CLS has been executed. I captured some parts with Hyperterm and the TEXT shows up in there so it was transmitted, just not visible in the live terminal. To be short, it comes down to a skipped CLS after all. Edited April 18, 2012 by Fox-1 / mnx Quote Link to comment Share on other sites More sharing options...
itaych Posted April 18, 2012 Author Share Posted April 18, 2012 You got me there. When parsing Esc [ n ; n ; ... ; n cmd style sequences, I internally use the value 255 as a flag for an invalid value, because I needed one, and could not conceive of a situation where one would legitimately use 255. Therefore in your ESC [ 255 D the 255 is ignored and replaced with the default value of 1, and the cursor moves one position left. You could easily use any other value between 80 to 254 to accomplish the same purpose. Or you could use a Carriage Return. I should fix the vt100.txt documentation to reflect this. Quote Link to comment Share on other sites More sharing options...
Fox-1 / mnx Posted April 18, 2012 Share Posted April 18, 2012 Therefore in your ESC [ 255 D the 255 is ignored and replaced with the default value of 1, and the cursor moves one position left. You could easily use any other value between 80 to 254 to accomplish the same purpose. Good to know! Thanks for the quick response. It wasn't a big issue for me but now I know it can be solved I need to do some editing. This sounds easier as it is but I can't edit the ANSI screens on my 130XE (that is, with WYSIWYG) so need to do it on another system. Maybe I could try it with an ATASCII editor (like Panther). Don't know how that works out but I'll try :-) Unrelated: it would be nice if there was an ASCII/ATASCII supporting Ice-Term-like terminal. There are a few but none as fast and readable as Ice-Term. Quote Link to comment Share on other sites More sharing options...
Fox-1 / mnx Posted April 18, 2012 Share Posted April 18, 2012 Changed some "255" values to "254" and it seems to do the trick, partially. The "TEXT" is still visible simply because there is no CLS but it's cleaner this way. Also noticed that blinking text sometimes is "shifted". [5;33mATARI ATAR is blinking, the I doesn't. [5;33m8-Bit 8-Bit is blinking plus the previous character. (that weird character is an ASCII $1B) Quote Link to comment Share on other sites More sharing options...
itaych Posted April 18, 2012 Author Share Posted April 18, 2012 Also noticed that blinking text sometimes is "shifted". That's a design limitation. Read the section about bold and blink in the doc. Quote Link to comment Share on other sites More sharing options...
Fox-1 / mnx Posted April 18, 2012 Share Posted April 18, 2012 That's a design limitation. Read the section about bold and blink in the doc. I see now. Missed the "is internally identical to bold" part. Quote Link to comment Share on other sites More sharing options...
itaych Posted April 24, 2012 Author Share Posted April 24, 2012 I have a question for SpartaDOS users. Do you still need to type KEY OFF before running Ice-T? If so, can anyone offer me tips on fixing this annoyance? (A way to reproduce it on an emulator would be a great start.) Quote Link to comment Share on other sites More sharing options...
w1k Posted April 28, 2012 Share Posted April 28, 2012 testing on 800xe - 1mb, 800xe - 320kb ram, sio2pc - works superb i cant run ice-t with q-meg 4.4, intsdx.. no R:, only 48kb..? Quote Link to comment Share on other sites More sharing options...
itaych Posted April 28, 2012 Author Share Posted April 28, 2012 w1k, sorry but I don't understand anything. Do you have two computers, Ice-T works on one and not the other? Quote Link to comment Share on other sites More sharing options...
w1k Posted April 28, 2012 Share Posted April 28, 2012 its no works on atari (1mb) with internal sparta dos, or q-meg 4.4.. i dont know why Quote Link to comment Share on other sites More sharing options...
itaych Posted April 28, 2012 Author Share Posted April 28, 2012 what did you mean by "only 48kb"? Quote Link to comment Share on other sites More sharing options...
w1k Posted April 28, 2012 Share Posted April 28, 2012 atari have 1mb.. ice-t show message something about 48kb.. Quote Link to comment Share on other sites More sharing options...
itaych Posted April 28, 2012 Author Share Posted April 28, 2012 Well, how did you expect me to understand that from what you wrote? I still don't understand if this is a single computer with two use cases or two different machines. In any case there is some non-standard behavior preventing Ice-T from detecting banked memory. Is this a problem with the new version or was this always the case? Quote Link to comment Share on other sites More sharing options...
w1k Posted April 28, 2012 Share Posted April 28, 2012 1mb ram, q-meg 4.4: with disabled q-meg works fine very sorry for my english.. Quote Link to comment Share on other sites More sharing options...
itaych Posted April 28, 2012 Author Share Posted April 28, 2012 This means that memory at address $BFFF is not writable, therefore Ice-T thinks there is some cartridge taking up part of the base 48K. Quote Link to comment Share on other sites More sharing options...
w1k Posted April 28, 2012 Share Posted April 28, 2012 aha, i understand.. so i cant run ice-t on this 1mb 800xe with q-meg/intsdx? Quote Link to comment Share on other sites More sharing options...
itaych Posted April 28, 2012 Author Share Posted April 28, 2012 Not unless someone can explain why this upgrade is eating into memory that's supposed to be free. Quote Link to comment Share on other sites More sharing options...
w1k Posted April 30, 2012 Share Posted April 30, 2012 (edited) its possible connect with ice-t to ports 21, 25, 110? i try connect to my FTP, i connect, but thats all and when i chating.. irc.atarichat.net 400 and trying ctrl+cursor top (5x) and hit RETURN, cursor move up 5 lines.. Edited April 30, 2012 by w1k Quote Link to comment Share on other sites More sharing options...
itaych Posted April 30, 2012 Author Share Posted April 30, 2012 w1k, I'll tell you what. Open a command prompt on any Windows, Mac or Linux machine. Type 'telnet host port'. If there is anything you can do there but cannot do in Ice-T, please let me know. Telnet cannot act as an FTP client and neither can Ice-T. The arrow keys do not work on atarichat.net (but Ctrl-B, F, P, N for back, forward, previous, next -- do work). Neither of these are Ice-T's fault. Quote Link to comment Share on other sites More sharing options...
w1k Posted April 30, 2012 Share Posted April 30, 2012 (edited) when i was win95, 98, i normall using windows telnet to connect ftp, or mail.. u successfully connect to FTP and POP3 or SMTP via ice-t with small trick, i uploading video.. that arrow keys not work, but when i type RETURN, then cursor move 5 lines up http://www.youtube.com/watch?v=c8msQLXMxrE Edited April 30, 2012 by w1k 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.