> But you have to disable the "Function" key in the lower left of the
> keyboard (X-Acto). If not, you will curse every time you press it by
> mistake.

We used to put a paper clip through the stem of one of the keys on the
tvi925 for similar reasons. I think it may have been the Print key.
We figured that was a reversible hack.

De

To: Ahem A Rivet's Shot
-=> Ahem A Rivet's Shot wrote to alt.folklore.computers <=-

> My favorite remains the Wyse 50 with an amber phosphor tube. The green
> phosphor models can be found, but not the amber. I curse myself for
> leaving mine behind.

AAS> Have you ever tried to reproduce that amber on a colour
AAS> monitor ? I've never been able to get it right, I'm not convinced it's
AAS> possible.

Oh, thanks all for the memories. My first job was on a Microdata 9000 Pick
system, with Televideo and Wyse 50/60 terminals.

When it came to the Phosphor Wars of the '80s, I was in both camps.
Green/Hercules graphics on PCs, Amber on terminals.

kurt weiske | kweiske at realitycheckbbs dot org
| http://realitycheckbbs.org
| 1:218/700@fidonet

.... Overtly resist change
--- MultiMail/DOS v0.52
--- Synchronet 3.19c-Win32 NewsLink 1.113
* realitycheckBBS - Aptos, CA - telnet://realitycheckbbs.org

On Mon, 30 May 2022 08:14:00 -0700
"Kurt Weiske" <kurt.weiske@realitycheckbbs.org.remove-11c1-this> wrote:

> To: Ahem A Rivet's Shot
> -=> Ahem A Rivet's Shot wrote to alt.folklore.computers <=-
>
> > My favorite remains the Wyse 50 with an amber phosphor tube. The green
> > phosphor models can be found, but not the amber. I curse myself for
> > leaving mine behind.
>
> AAS> Have you ever tried to reproduce that amber on a colour
> AAS> monitor ? I've never been able to get it right, I'm not convinced
> AAS> it's possible.
>
>
> Oh, thanks all for the memories. My first job was on a Microdata 9000
> Pick system, with Televideo and Wyse 50/60 terminals.

Must have been about the same time I was using Televideo and Wyse
50 terminals on a Televideo MMMOST setup (hybrid MP/M CP/M with RS422
based star network).

I missed out on encountering Pick, it looked like an interesting
system.

> When it came to the Phosphor Wars of the '80s, I was in both camps.
> Green/Hercules graphics on PCs, Amber on terminals.

There was a cyan phosphor that was really nice but *very* rare I
think, at least I only saw it in one place (on *every* terminal), I don't
recall the make of terminal.

--
Steve O'Hara-Smith
Odds and Ends at http://www.sohara.org/

Ahem A Rivet's Shot <steveo@eircom.net> writes:
> There was a cyan phosphor that was really nice but *very* rare I
> think, at least I only saw it in one place (on *every* terminal), I don't
> recall the make of terminal.

A Friend-of-a-friend worked in an industry that required him to have a
close working relationship with CRT manufacturers. He was able to
finagle a common 12-inch monochrome CRT with the 'blue from RGB'
phosphor. I do not know if this was a catalog item for the manufacturer
in question (I *seem* to recall Ball Bros, but that's a very fuzzy
memory), or he was able to get them to make a one-off. The former seems
more likely, but the latter is certainly not impossible.

lawrenabe@abaluon.abaom (Lawrence Statton (NK1G)) writes:
>Ahem A Rivet's Shot <steveo@eircom.net> writes:
>> There was a cyan phosphor that was really nice but *very* rare I
>> think, at least I only saw it in one place (on *every* terminal), I don't
>> recall the make of terminal.
>
>A Friend-of-a-friend worked in an industry that required him to have a
>close working relationship with CRT manufacturers. He was able to
>finagle a common 12-inch monochrome CRT with the 'blue from RGB'
>phosphor. I do not know if this was a catalog item for the manufacturer
>in question (I *seem* to recall Ball Bros, but that's a very fuzzy
>memory), or he was able to get them to make a one-off. The former seems
>more likely, but the latter is certainly not impossible.
>

The LSI ADM-3A was available with a white phospher that had a blueish tint.

Ball Bros supplied their CRTs

scott@slp53.sl.home (Scott Lurndal) writes:

> lawrenabe@abaluon.abaom (Lawrence Statton (NK1G)) writes:
>>Ahem A Rivet's Shot <steveo@eircom.net> writes:
>>> There was a cyan phosphor that was really nice but *very* rare I
>>> think, at least I only saw it in one place (on *every* terminal), I don't
>>> recall the make of terminal.
>>
>>A Friend-of-a-friend worked in an industry that required him to have a
>>close working relationship with CRT manufacturers. He was able to
>>finagle a common 12-inch monochrome CRT with the 'blue from RGB'
>>phosphor. I do not know if this was a catalog item for the manufacturer
>>in question (I *seem* to recall Ball Bros, but that's a very fuzzy
>>memory), or he was able to get them to make a one-off. The former seems
>>more likely, but the latter is certainly not impossible.
>>
>
> The LSI ADM-3A was available with a white phospher that had a blueish tint.
>
> Ball Bros supplied their CRTs

I had *MANY* different ball monitors over the years, and I am fairly
certain that the ten-pin keyed-edge-connector interface was their
devising that took hold in other vendors'.

The CRT I'm referring to above was not a "blueish tint white" -- It was
brilliant blue.

On 31/05/2022 03:03, Lawrence Statton (NK1G) wrote:
> scott@slp53.sl.home (Scott Lurndal) writes:
>
>> lawrenabe@abaluon.abaom (Lawrence Statton (NK1G)) writes:
>>> Ahem A Rivet's Shot <steveo@eircom.net> writes:
>>>> There was a cyan phosphor that was really nice but *very* rare I
>>>> think, at least I only saw it in one place (on *every* terminal), I don't
>>>> recall the make of terminal.
>>>
>>> A Friend-of-a-friend worked in an industry that required him to have a
>>> close working relationship with CRT manufacturers. He was able to
>>> finagle a common 12-inch monochrome CRT with the 'blue from RGB'
>>> phosphor. I do not know if this was a catalog item for the manufacturer
>>> in question (I *seem* to recall Ball Bros, but that's a very fuzzy
>>> memory), or he was able to get them to make a one-off. The former seems
>>> more likely, but the latter is certainly not impossible.
>>>
>>
>> The LSI ADM-3A was available with a white phospher that had a blueish tint.
>>
>> Ball Bros supplied their CRTs
>
> I had *MANY* different ball monitors over the years, and I am fairly
> certain that the ten-pin keyed-edge-connector interface was their
> devising that took hold in other vendors'.
>
> The CRT I'm referring to above was not a "blueish tint white" -- It was
> brilliant blue.
>
Blue on its own is a really bad choice.

You know how human eyes are basically really rubbish? Very limited field
of view with any detail, poor colour detection, etc?

One of the "features" is that there are fewer blue sensors than the red,
green or grey. Which means we can't resolve blue so easily.

Andy

Vir Campestris <vir.campestris@invalid.invalid> writes:
>On 31/05/2022 03:03, Lawrence Statton (NK1G) wrote:
>> scott@slp53.sl.home (Scott Lurndal) writes:
>>
>>> lawrenabe@abaluon.abaom (Lawrence Statton (NK1G)) writes:
>>>> Ahem A Rivet's Shot <steveo@eircom.net> writes:
>>>>> There was a cyan phosphor that was really nice but *very* rare I
>>>>> think, at least I only saw it in one place (on *every* terminal), I don't
>>>>> recall the make of terminal.
>>>>
>>>> A Friend-of-a-friend worked in an industry that required him to have a
>>>> close working relationship with CRT manufacturers. He was able to
>>>> finagle a common 12-inch monochrome CRT with the 'blue from RGB'
>>>> phosphor. I do not know if this was a catalog item for the manufacturer
>>>> in question (I *seem* to recall Ball Bros, but that's a very fuzzy
>>>> memory), or he was able to get them to make a one-off. The former seems
>>>> more likely, but the latter is certainly not impossible.
>>>>
>>>
>>> The LSI ADM-3A was available with a white phospher that had a blueish tint.
>>>
>>> Ball Bros supplied their CRTs
>>
>> I had *MANY* different ball monitors over the years, and I am fairly
>> certain that the ten-pin keyed-edge-connector interface was their
>> devising that took hold in other vendors'.
>>
>> The CRT I'm referring to above was not a "blueish tint white" -- It was
>> brilliant blue.
>>
>Blue on its own is a really bad choice.
>
>You know how human eyes are basically really rubbish? Very limited field
>of view with any detail, poor colour detection, etc?
>
>One of the "features" is that there are fewer blue sensors than the red,
>green or grey. Which means we can't resolve blue so easily.

Back when I was designing theatrical lighting for shows, one of the first
things I was taught when working with the set/costume designers on the lighting
color schemes was to avoid pure blue scenes for the reasons you state
(even though they can be evocative for storm scenes).

The rule of thumb was to light one side warm and one side cool when
using the traditional area lighting plan.

I wish modern cinematographers would have learned that lesson about
avoiding blues - so many films/TV today are way too dark for old eyes :-)

On 2022-05-31, Scott Lurndal <scott@slp53.sl.home> wrote:

> Vir Campestris <vir.campestris@invalid.invalid> writes:
>
>> On 31/05/2022 03:03, Lawrence Statton (NK1G) wrote:
>>
>>> The CRT I'm referring to above was not a "blueish tint white" -- It was
>>> brilliant blue.
>>
>> Blue on its own is a really bad choice.
>>
>> You know how human eyes are basically really rubbish? Very limited field
>> of view with any detail, poor colour detection, etc?
>>
>> One of the "features" is that there are fewer blue sensors than the red,
>> green or grey. Which means we can't resolve blue so easily.
>
> Back when I was designing theatrical lighting for shows, one of the first
> things I was taught when working with the set/costume designers on the
> lighting color schemes was to avoid pure blue scenes for the reasons you
> state (even though they can be evocative for storm scenes).
>
> The rule of thumb was to light one side warm and one side cool when
> using the traditional area lighting plan.
>
> I wish modern cinematographers would have learned that lesson about
> avoiding blues - so many films/TV today are way too dark for old eyes :-)

Try blue - it's the new red!
-- Wall-E

I'm tired of this blue fad, and wish we could move on - especially from
our obsession with bright blue LEDs.

Even back in my teens, before those newfangled LEDs were invented,
my eyes couldn't focus on blue (e.g. Christmas lights) - even some
green lights gave them trouble.

Speaking of theatre, one time I was doing sound in a darkened
auditorium, and the blue LED pilot light on the sound board
was so bright that I had to cover it with three layers of
masking tape before I could see anything else.

Who comes up with this stuff?

--
/~\ Charlie Gibbs | Microsoft is a dictatorship.
\ / <cgibbs@kltpzyxm.invalid> | Apple is a cult.
X I'm really at ac.dekanfrus | Linux is anarchy.
/ \ if you read it the right way. | Pick your poison.

Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:

> Try blue - it's the new red!
> -- Wall-E

()()()()()()

--
Mike Spencer Nova Scotia, Canada

On Tue, 31 May 2022 21:30:14 GMT
scott@slp53.sl.home (Scott Lurndal) wrote:

> Vir Campestris <vir.campestris@invalid.invalid> writes:
[]
> >One of the "features" is that there are fewer blue sensors than the red,
> >green or grey. Which means we can't resolve blue so easily.
>
> Back when I was designing theatrical lighting for shows, one of the first
> things I was taught when working with the set/costume designers on the lighting
> color schemes was to avoid pure blue scenes for the reasons you state
> (even though they can be evocative for storm scenes).
>
> The rule of thumb was to light one side warm and one side cool when
> using the traditional area lighting plan.
>
> I wish modern cinematographers would have learned that lesson about
> avoiding blues - so many films/TV today are way too dark for old eyes :-)

Orange & Teal - urgh.

--
Bah, and indeed Humbug.

On Tue, 31 May 2022 22:15:01 GMT, Charlie Gibbs
<cgibbs@kltpzyxm.invalid> wrote:
>On 2022-05-31, Scott Lurndal <scott@slp53.sl.home> wrote:
>
>> Vir Campestris <vir.campestris@invalid.invalid> writes:
>>
>>> On 31/05/2022 03:03, Lawrence Statton (NK1G) wrote:
>>>
>>>> The CRT I'm referring to above was not a "blueish tint white" -- It was
>>>> brilliant blue.
>>>
>>> Blue on its own is a really bad choice.
>>>
>>> You know how human eyes are basically really rubbish? Very limited field
>>> of view with any detail, poor colour detection, etc?
>>>
>>> One of the "features" is that there are fewer blue sensors than the red,
>>> green or grey. Which means we can't resolve blue so easily.
>>
>> Back when I was designing theatrical lighting for shows, one of the first
>> things I was taught when working with the set/costume designers on the
>> lighting color schemes was to avoid pure blue scenes for the reasons you
>> state (even though they can be evocative for storm scenes).
>>
>> The rule of thumb was to light one side warm and one side cool when
>> using the traditional area lighting plan.
>>
>> I wish modern cinematographers would have learned that lesson about
>> avoiding blues - so many films/TV today are way too dark for old eyes :-)
>
> Try blue - it's the new red!
> -- Wall-E
>
>I'm tired of this blue fad, and wish we could move on - especially from
>our obsession with bright blue LEDs.
>
>Even back in my teens, before those newfangled LEDs were invented,
>my eyes couldn't focus on blue (e.g. Christmas lights) - even some
>green lights gave them trouble.
>
>Speaking of theatre, one time I was doing sound in a darkened
>auditorium, and the blue LED pilot light on the sound board
>was so bright that I had to cover it with three layers of
>masking tape before I could see anything else.
>
>Who comes up with this stuff?

Most likely by people who don't have to use it.
--
Jim

Vir Campestris <vir.campestris@invalid.invalid> writes:
> Blue on its own is a really bad choice.

De gustibus non est disputandum.

I probably would not have chosen it for serious work, but it was not my
decision to make.

On 2022-05-17, Jason Evans <jsevans@mailfence.com> wrote:
> I'm going to be moving soon and after I get settled in, I would like to find an
> dumb terminal that I can use with a serial connection to a raspberry pi. I'd
> like any suggestions you might have for such a machine.

I'm fond of the DEC vt510. Unlike many dumb terminals, it accepts a standard PC
PS/2 keyboard and also supports key remapping, so you can finally get Ctrl where
it should be - left of A.

The downside is that it uses DTR/DTS instead of CTR/CTS for hardware flow
control, which isn't supported on Linux. So, you can either wire your own
serial cable or use software flow control. Somewhat to my surprise, I've found
that these old dumb terminals can't keep up with line rate very well. I run my
vt510 at 57600bps but definitely need the flow control for things with heavy
escape sequences.

- John

On 2022-05-19, Chris Adams <cmadams@cmadams.net> wrote:
> One additional thought: using a traditional hardware terminal for
> something modern like a Pi could be problematic - newer stuff like that
> pretty much assumes full ANSI plus Unicode. ANSI is (more or less) a
> superset of VT102/VT220, so most escape sequences will work on a classic
> terminal, but Unicode definitely won't.

GNU screen can do this kind of conversion. I use it with my vt510 and it works
perfectly. My .screenrc:

defflow on
defencoding UTF-8
vbell off
termcapinfo * XC=B%,‐-,

# From https://unix.stackexchange.com/questions/8439/gnu-screen-makes-vim-esc-key-slow
# Could also try maptimeout 0
maptimeout 5

# https://stackoverflow.com/questions/4548106/screen-somehow-unmaps-my-arrow-keys-in-emacs-after-a-z
# to try to resolve arrow key issues in less and others
bindkey -k ku stuff ^[OA
bindkey -k kd stuff ^[OB
bindkey -k kr stuff ^[OC
bindkey -k kl stuff ^[OD

To: Ahem A Rivet's Shot
-=> Ahem A Rivet's Shot wrote to alt.folklore.computers <=-

AAS> Must have been about the same time I was using Televideo and
AAS> Wyse 50 terminals on a Televideo MMMOST setup (hybrid MP/M CP/M with
AAS> RS422 based star network).

AAS> I missed out on encountering Pick, it looked like an
AAS> interesting system.

It was - the file system was a data dictionary, and access was through a
version of BASIC or a relational DB language called REALITY that was pretty
close to structured SQL.

That was a fun gig - working at a university bookstore, writing full-screen
inventory query tools, a rudimentary email system, a chat system and
tweaking all sorts of "glue" apps to connect the POS system with accounting
and inventory, writing systems to translate book orders into EDI format, and
more - all in BASIC and SQL as a 22 year-old student.

kurt weiske | kweiske at realitycheckbbs dot org
| http://realitycheckbbs.org
| 1:218/700@fidonet

.... Make a blank valuable by putting it in an exquisite frame
--- MultiMail/DOS v0.52
--- Synchronet 3.19c-Win32 NewsLink 1.113
* realitycheckBBS - Aptos, CA - telnet://realitycheckbbs.org

For a generic terminal to use with pretty much anything, it's hard to go
wrong with an HP 700/96 or 700/98. They have great DEC emulation, full
HP blockmode/forms support (required if you ever want to connect it to
an ancient HP system running a non-UNIX operating system), and unlike
DEC terminals—which are all seen as "desirable"—the "modern" HP
terminals are on the inexpensive side.

The downside is that, unlike the very last models of DEC terminal
(VT510/VT520/VT525), they still use a custom keyboard, but there are
both PC-101 and HP-ITF layouts and the keyboards aren't that "desirable"
so, again, they tend to be inexpensive. And personally I like the HP-ITF
layout if I ever need to use vi since the escape key is in a pretty
convenient place.

The more important thing is to set up a decent RS-232 port on the
Raspberry Pi (or whatever else you use it with). Three-wire serial
(transmit/receive/ground) will work just fine with XON/XOFF in-band flow
control as long as you adjust the levels between TTL and RS-232, such as
with an MC1488/MC1489 pair or something like that, but to really fly
you'll want full hardware flow control at proper RS-232 voltage levels.
(The latter is something I've heard some USB-serial adapters fail at.)
This guide has a lot of good and detailed information:
<http://www.deater.net/weave/vmwprod/hardware/pi-rts/>

-- Chris

On 5/31/2022 5:15 PM, Charlie Gibbs wrote:
> On 2022-05-31, Scott Lurndal <scott@slp53.sl.home> wrote:
>
>
]... snip ...] ]... snip ...] ]... snip ...]
>
> Speaking of theatre, one time I was doing sound in a darkened
> auditorium, and the blue LED pilot light on the sound board
> was so bright that I had to cover it with three layers of
> masking tape before I could see anything else.
>
> Who comes up with this stuff?
>

"I used to criticize bad decisions... until I realized that someone was
making money from doing it this way."

-- Paraphrased from Charlie Gibbs

--

Charles Richmond

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Charles Richmond <codescott@aquaporin4.com> writes:

> On 5/31/2022 5:15 PM, Charlie Gibbs wrote:
>
>> On 2022-05-31, Scott Lurndal <scott@slp53.sl.home> wrote:
>>
>>
> ]... snip ...] ]... snip ...] ]... snip ...]
>>
>> Speaking of theatre, one time I was doing sound in a darkened
>> auditorium, and the blue LED pilot light on the sound board
>> was so bright that I had to cover it with three layers of
>> masking tape before I could see anything else.
>>
>> Who comes up with this stuff?
>
> "I used to criticize bad decisions... until I realized that someone was
> making money from doing it this way."
>
> -- Paraphrased from Charlie Gibbs

You have meddled with the primal forces of nature, Mr. Beale,
and I won't have it! Is that clear?....There are no
nations. There are no peoples. There are no Russians. There are
no Arabs. There are no third worlds. There is no West. There is
only one holistic system of systems, one vast and immane,
interwoven, interacting, multivariate, multinational dominion
of dollars.
-- Arthur Jensen, in _Network_

--
Mike Spencer Nova Scotia, Canada

Tue, 17 May 2022 12:57:02 +0200
Jason Evans <jsevans@mailfence.com> schrieb:
>Hi all,
>
>I'm going to be moving soon and after I get settled in, I would like to find an
>dumb terminal that I can use with a serial connection to a raspberry pi. I'd
>like any suggestions you might have for such a machine.
>
>The only thing that I ask is that it has a serial port that doesn't require a
>lot of modifications to get going, isn't too rare and therefore expensive, and
>I am partial to amber screens instead of green screens.
>
>Like I said, I'm not looking to buy anything yet but if you have any
>suggestions on what to keep an eye out for, please let me know.

Not a dumb terminal, I'm using a 386sx (MS-DOS 5.0) with Telix.
--
A tuna is a way of Liff

Jan v/d Broek
balglaas@xs4all.nl

On 2022-06-15, Jan van den Broek <fortytwo@xs4all.nl> wrote:
>>Like I said, I'm not looking to buy anything yet but if you have any
>>suggestions on what to keep an eye out for, please let me know.
>
> Not a dumb terminal, I'm using a 386sx (MS-DOS 5.0) with Telix.

How's its performance?

I've been somewhat astonished at how horribly slow the real dumb terminals are.

Even my vt510, which seems to be the fastest, has to use XOFF when I start emacs
because it can't keep up with the escape sequences at that point and drops them,
unless I set it all the way down to 9600bps (it will support line rates up to
115200bps). Something of an additional annoyance is that these real dumb
terminals support hardware flow control, but using the DTR pin, not RTS/CTS, and
that isn't supported on Linux (though it is on FreeBSD).

My Wyse WY-55 is worse than the vt510, and my IBM 3151 won't even support a line
rate above 19200.

John

In article <t5vv2a$8mf$1@dont-email.me>,
Jason Evans <jsevans@mailfence.com> wrote:
>Hi all,
>
>I'm going to be moving soon and after I get settled in, I would like to find an
>dumb terminal that I can use with a serial connection to a raspberry pi. I'd
>like any suggestions you might have for such a machine.
>
>The only thing that I ask is that it has a serial port that doesn't require a
>lot of modifications to get going, isn't too rare and therefore expensive, and
>I am partial to amber screens instead of green screens.
>
>Like I said, I'm not looking to buy anything yet but if you have any
>suggestions on what to keep an eye out for, please let me know.

There is the VT-69:

http://violence.works/
https://hackaday.io/project/163829-vt-69-handheld-terminal

>Jason

// Christian

On 2022-06-15, John Goerzen <jgoerzen@complete.org> wrote:

> On 2022-06-15, Jan van den Broek <fortytwo@xs4all.nl> wrote:
>
>>> Like I said, I'm not looking to buy anything yet but if you have any
>>> suggestions on what to keep an eye out for, please let me know.
>>
>> Not a dumb terminal, I'm using a 386sx (MS-DOS 5.0) with Telix.
>
> How's its performance?
>
> I've been somewhat astonished at how horribly slow the real dumb
> terminals are.
>
> Even my vt510, which seems to be the fastest, has to use XOFF when I
> start emacs because it can't keep up with the escape sequences at that
> point and drops them, unless I set it all the way down to 9600bps (it
> will support line rates up to 115200bps).

C'mon, 9600 bps was blazingly fast in those days. That's as fast as my
Heath 19 would go prior to the Super 19 upgrade - and even then it would
struggle at 19200.

> Something of an additional annoyance is that these real dumb terminals
> support hardware flow control, but using the DTR pin, not RTS/CTS, and
> that isn't supported on Linux (though it is on FreeBSD).

Looks like it's time to wire up a custom RS-232 cable crossing DTR and
RTS...

> My Wyse WY-55 is worse than the vt510, and my IBM 3151 won't even
> support a line rate above 19200.

The Univac 90/30s I worked on in the late '70s offered an async option
if you really wanted it, although the standard was synchronous at up
to 9600 bps. (With modems costing about a dollar per bps, 9600 was
reserved to cable runs within the building unless you had _really_
deep pockets.) The async port wouldn't go any faster than 2400 bps -
async is a low-speed protocol, doncha know. :-)

--
/~\ Charlie Gibbs | Microsoft is a dictatorship.
\ / <cgibbs@kltpzyxm.invalid> | Apple is a cult.
X I'm really at ac.dekanfrus | Linux is anarchy.
/ \ if you read it the right way. | Pick your poison.

On 2022-06-15, Christian Brunschen <cb@elaine.df.lth.se> wrote:

> In article <t5vv2a$8mf$1@dont-email.me>,
> Jason Evans <jsevans@mailfence.com> wrote:
>
>> Hi all,
>>
>> I'm going to be moving soon and after I get settled in, I would like
>> to find an dumb terminal that I can use with a serial connection to
>> a raspberry pi. I'd like any suggestions you might have for such a
>> machine.
>>
>> The only thing that I ask is that it has a serial port that doesn't
>> require a lot of modifications to get going, isn't too rare and
>> therefore expensive, and I am partial to amber screens instead of
>> green screens.
>>
>> Like I said, I'm not looking to buy anything yet but if you have any
>> suggestions on what to keep an eye out for, please let me know.
>
> There is the VT-69:
>
> http://violence.works/
> https://hackaday.io/project/163829-vt-69-handheld-terminal

How delightfully perverse! I'm gratified to see that they spelled
"DE-9" correctly. I'm tired of correcting all the people who insist
on calling it "DB-9".

https://en.wikipedia.org/wiki/D-subminiature

--
/~\ Charlie Gibbs | Microsoft is a dictatorship.
\ / <cgibbs@kltpzyxm.invalid> | Apple is a cult.
X I'm really at ac.dekanfrus | Linux is anarchy.
/ \ if you read it the right way. | Pick your poison.

On 6/15/2022 3:55 PM, John Goerzen wrote:
> On 2022-06-15, Jan van den Broek <fortytwo@xs4all.nl> wrote:
>>> Like I said, I'm not looking to buy anything yet but if you have any
>>> suggestions on what to keep an eye out for, please let me know.
>>
>> Not a dumb terminal, I'm using a 386sx (MS-DOS 5.0) with Telix.
>
> How's its performance?
>
[... snip ...] [... snip ...] [... snip ...]

>
> My Wyse WY-55 is worse than the vt510, and my IBM 3151 won't even support a line
> rate above 19200.
>

At a PPOE, I used a Digital Equipment VT-220 which was attached via a
termserver to an ethernet network to rlogin to one of the workstations.
This terminal could keep up with listing out a file at 19200 baud...
as long as all the lines had only 40 characters or less. If the file
had a grouping of lines with 70 or 80 characters, the speed of the
display would bog down...

I did *not* like the 220 for many reasons... not the least being that
the escape key was badly placed. We were running SVR4 Unix. But the
terminal had a monochrome amber display.

--

Charles Richmond

--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus