Re: [M100] VT100 Emulation and DVi

2023-11-26 Thread John R. Hogerhuis
Seems like there are a lot of tough ones... Word wrap, relative position / simple windowing taking significant work. M100 is simpler than vt100. So it seems trivial to map m100 escapes to vt100. But mapping vt100 back to m100 would only be easy for a subset of vt100 escapes. But that "might*

Re: [M100] VT100 Emulation and DVi

2023-11-26 Thread Stephen Adolph
There are a couple of hard ones John. Didn't we go through them and conclude certain m100 sequences could not be done on VT100? Having said that I don't recall which ones for sure. On Sunday, November 26, 2023, John R. Hogerhuis wrote: > How different is vt100 from the m100's native terminal

Re: [M100] VT100 Emulation and DVi

2023-11-26 Thread John R. Hogerhuis
How different is vt100 from the m100's native terminal emulation (mostly vt52). What's missing that you need... I could map necessary codes in HTERM. It already does a lot of processing to map utf8 characters and xterm escapes. In fact that's most of what HTERM does aside fromn hardware flow

Re: [M100] VT100 Emulation and DVi

2023-11-26 Thread Peter Vollan
In 1991 I used to call text only BBSs all the time and even go on the internet a bit with my Model 100 at 300 baud. On Sun, 26 Nov 2023 at 12:51, grima...@gmail.com wrote: > Hi all, > > I recently decided to take my main battle-station (apple iie) out of > service, so I can dedicate more space

[M100] VT100 Emulation and DVi

2023-11-26 Thread grima...@gmail.com
Hi all, I recently decided to take my main battle-station (apple iie) out of service, so I can dedicate more space to my Tandy 102. What I have found though, is that the Model 100 isn’t quite ideal for BBSing, even with the DVI. A lot of systems assume VT100 emulation, which Apple did have. I