See, that is what I have been saying: if Virtual T does not behave like a real one, it is not doing its job.
On Mon, 21 Dec 2020 at 04:07, Stephen Adolph <twospru...@gmail.com> wrote: > Ok thanks for the info. I did it quickly, assuming that what was working > in virtualt would also work in reality. > > Not always the case. > > I noticed that last night that the VT100 driver embedded in rex# also has > a bug. > > I'll take it down. I'm sure when I find the issue on REX# it will be > apparent for both. > > > > On Monday, December 21, 2020, Jim Anderson <jim.ander...@kpu.ca> wrote: > >> > -----Original Message----- >> > >> > Updated to build 21, with a bug fixed. >> > Please report any issues, thanks! >> >> I tried this out tonight after I finished restoring everything to my >> other REX... >> >> I didn't have much success with it - it does initialize, but after going >> into BASIC and issuing either SCREEN 1 or SCREEN 2, if I exit back to the >> menu I can't launch TEXT or even go back into BASIC anymore - have to use >> the Reset button to recover. (Also, whether I try to select a .BA or .DO >> file, or even select BASIC or TEXT, I get the same menu corruption as >> before. No matter what item I select, it just beeps and displays the >> corrupt menu screen.) >> >> >> >> >> >> >> >> jim >> >>
