-
Content Count
210 -
Joined
-
Last visited
Content Type
Profiles
Member Map
Forums
Blogs
Gallery
Calendar
Store
Everything posted by itaych
-
What about SpartaDOS 3.2g? It keeps putting an annoying status bar at the top of the screen, ruining the display. Is there anything I can do to make it stop?
-
Thanks, that works. Is there anything I could do to prevent the need for "X ICET"? Failing that, is there an easy way to detect SDX so I can put an informative message telling the user to use "X"?
-
I've downloaded the latest version of SDX from the SpartaDOS Upgrade Project website. I mounted the cartridge image named SDX445_sdx128.car in Altirra, then tried to load Ice-T. What I can see is that the cartridge occupies memory in the low 48K range. Ice-T needs this range free and so can't work with it at all, and neither would any older version. Did I miss something?
-
In that case you need to post a detailed, step by step list of instructions to reproduce the problems you see. Your messages are far too short for me to be able to reproduce these problems myself. I highly prefer that you reproduce under Altirra as right now my real Atari is not set up.
-
1. Your "small trick" involves using a BBS. 2. Do the arrows work properly with telnet?
-
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.
-
Not unless someone can explain why this upgrade is eating into memory that's supposed to be free.
-
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.
-
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?
-
what did you mean by "only 48kb"?
-
w1k, sorry but I don't understand anything. Do you have two computers, Ice-T works on one and not the other?
-
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.)
-
That's a design limitation. Read the section about bold and blink in the doc.
-
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.
-
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?
-
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.
-
ATDI host port !!!!
-
The full command is ATDI.
-
If that URL doesn't work try: http://wiki.strotmann.de/wiki/Wiki.jsp?page=Cartridges#section-Cartridges-TheRTime8
-
BillC, thanks for the clarification. I added support for the R-Time 8 because it seemed to be an option in all the emulators, and it was easy enough given the instructions at http://atariwiki.str...idges-TheRTime8 . I access the hardware directly, as shown there, and not via a device driver - and so the other RTC you mention is not supported.
-
Stephen: I don't have a real cartridge to test with, I was relying on Altirra. If you're willing to assist me in solving this problem (either with technical knowledge or simply being willing to run some tests on your hardware) please email me.
-
w1k: in the dialing menu instead of the number enter 'I host port'. Read the manual. Stephen: I don't understand, does the clock in the upper right corner reflect the current time as stored in the cartridge? That's all I implemented; you're not supposed to be able to set the hardware clock from within Ice-T.
-
While working with Altirra I noticed that Telnet connections were running much more slowly than I expected; I thought that this was some complicated performance issue, but I now realize that this is simply because Altirra throttles the incoming data to the baud rate requested by the application, and Ice-T is set to 2400 baud by default! I should probably change this, but in the meantime I recommend either changing this setting to 19.2k, or more simply, disabling the serial port rate throttling in Altirra's options.
-
w1k: You've shown this to me in the past. There's no reason it would be fixed in this version because I haven't touched the terminal emulation code. However, I don't think this is a problem with Ice-T but more like some setting in the IRC implementation or the Linux shell you are using. In any case I as well as several others are able to IRC just fine with the new version as well as previous versions. If you are using ircII or Irssi you may want to try typing the following in your shell before running IRC: export TERM=vt100 or set TERM=vt100
-
Ice-T XE 2.73 is hereby unleashed unto the unsuspecting public. Here's what's new: A bug in the way I called the OS keyboard handler in order to generate keyclicks caused an endless stream of 'j' characters to appear when "standard" keyclick was enabled, under certain circumstances. Thanks to Avery Lee (author of the Altirra emulator) for pinpointing the cause of this bug. R-Time 8 cartridge supported for clock that is displayed in the menu. Even without R-Time 8, clock and online timer are now far more accurate, particularly on PAL machines (on which they were never even remotely accurate). The 'break' key may now be used (in addition to ^Esc) to send a break. Arrow keys in the menus may now be used with or without holding down Ctrl. Some fixes made to way I access the serial port device (R:). Dial string changed from ATDT to ATD. Dialer will now hang up before dialing, if you were already online. Fixed potential crash when quitting the program. Removed registration nag messages. Many of these changes are geared towards convenience for those using Ice-T under an emulator, particularly Altirra with its excellent support for outbound serial connections. It is now possible to create dialing entries in the Dialing menu which are actually Telnet destinations. See the documentation for more on how to do this. All feedback is appreciated. If it works for you on your particular platform and setup, please let me know. If this new version breaks anything that used to work, please let me know that too. Enjoy, -itay Ice-T_XE_2.73.zip
