Nice, Tom, you've found a bug. What's happening here is Zork III is
using a BIOS routine that waits until a key is pressed. With that
routine I neglected to implement IO byte checking (which is set by
STAT), so that's why you have to press something on the M100 keyboard.
I'll fix it in my next release.
Philip
On 18/11/2021 4:05 am, Stephen Adolph wrote:
ah! I understand now. that makes sense. if CP/M still thinks it
needs to throttle the screen then that stays in effect even when the
screen is redirected.
I guess ZorkIII is implementing its own check .. IE it is a problem
with Zork III not CP/M.
On Wed, Nov 17, 2021 at 9:50 AM tjhoppe <tjho...@gmail.com> wrote:
Well, good news. If you set M100 CPM to 'Sc S' and 'Cu S' it works
much better. I still found an issue playing Zork III where it says
"-----more-----" then stopped responding, requiring me to press
enter on the M100.
stat con:=uc1: <-- Redirect CP/M output to serial port
stat con:=tty: <-- Change it back to M100 native display (type
this from terminal program on PC)
I am using Minicom 2.7.1 on Linux (VT102 emulator with 19200 N81).
I left it on overnight and it is still working this morning.
Tom
On Tue, Nov 16, 2021 at 2:55 PM Tom Hoppe <tjho...@gmail.com> wrote:
Correct, VT100 emulation.
On Tue, Nov 16, 2021 at 2:15 PM Stephen Adolph
<twospru...@gmail.com> wrote:
there will be escape characters flowing over serial in
this case, so you need to ensure that does not mess with
things.
If I understand what is happening
M100 ----> PC (video terminal character flow)
M100 <---- PC (input keyboard strokes)
When you say the terminal works reliably using F3, you are
using the PC as a display for CP/M, right? And in this
case, you selected VT100 emulation?
On Tue, Nov 16, 2021 at 5:05 PM Tom Hoppe
<tjho...@gmail.com> wrote:
I left minicom set to 19200 8N1 and it worked (until
it didn't). The Sc L vs Sc S is a good point! I will
try changing this tonight and see if it helps. My
ultimate goal is to ssh into my home PC from work so I
can play with CP/M during lunch :).
Tom
On Tue, Nov 16, 2021 at 11:21 AM Jim Anderson
<jim.ander...@kpu.ca> wrote:
First thought that comes to mind: it may be
stopping because of the feature which pauses the
screen output after 8 lines of consecutive output
– try Label-F1-Label to toggle ‘Sc L’ to ‘Sc S’ to
disable this before redirecting the console?
I’m glad to see this post because I honestly had
been thinking a while back that “I wish there was
a way to use a ps/2 keyboard with my MVT100 board
as a full-blown terminal” but didn’t try anything
because I’m not familiar enough with CP/M to know
how to redirect the console like that. What baud
rate does it end up using when you do this?
jim
*From:* M100 <m100-boun...@lists.bitchin100.com>
*On Behalf Of *Tom Hoppe
*Sent:* Tuesday, November 16, 2021 10:50
*To:* m...@bitchin100.com
*Subject:* [M100] Re-directing CP/M console to
serial port in REXCPM
*CAUTION External Sender:*Do not click links or
open attachments unless you recognize the sender
and know the content is safe.
I am trying to re-direct the REXCPM console to the
M100 serial port but only having limited success.
I am using 'stat con:=uc1:' to do the re-direct.
It seems to work for a minute, then stops. I am
using minicom in Linux and it works reliably using
the REXCPM 'F3 toggle' feature to re-direct only
the screen output (19200 8N1). Has anyone else
tried doing this successfully?
Tom Hoppe
