Re: [M100] Serial over Console in CP/M

[Will Senn]

Here's where I'm at:

1. Fire up Minicom (19200, 8N1, no flow control)
2. Minicom is Offline
3. Fire up M100
4. CTL-C to enter CP/M
5. Label-F1-Label (Sc to S)
6. Label-F2-Label (Cu to S)
7. Label-F3-Label (selecting RS23) to "initialize RS232"
8. Minicom is Online
9. Label-F3-Label (selecting M100) so you can type on the M100
10. in CP/M, stat con:=uc1:

A>dir
sorta works...

   AOOT A OK  CM: ZMSC CS    CM
   A: DDT  COM : DUMP COM
   A: ED   COM : LOAD COM
   A: PIP  COM :SUBMI   CO
   :XSB   C:IPR M
   A: A    DOC : TEST DOC
   A   DOC : B    DOC
>dir
   A TAT   EXPORT   COM
   : ZORK1    COM : ZORK1    DAT
   A: MBASIC   COM :SM  COM
   A:DD    CM:DUP    COM
   A: PP    CM: SUBMIT   COM  CO  LOAD COM
   A: XSUB COM : IMPORT   COM
   A: A  DC  EST DOC
   A: STAT    OC : B    DOC
   :
>dir
   C:M CO
   :DT  OM : DUMP O
   : D    OM : LOAD COMPP    OM:SBMT CM
    : SUB  CM:IPR
  : DCA B DO
   A:

Hmmm... off to trying a lower baud rate via TELCOM

On 3/20/24 10:12 PM, Philip Avery wrote:
Yes, 19200 (98N1D) as stated in 'Initialising RS-232" 
http://bitchin100.com/wiki/index.php?title=M100_CP/M


however, maybe one can initialise in TELCOM to a different baud rate...

Philip

On 21/03/2024 3:26 pm, Will Senn wrote:

What is the default baud rate? Are the other settings - 8n1?

On 3/20/24 20:53, Philip Avery wrote:
Yes, the IO byte is fully implemented in M100 CP/M. Use 'stat 
con:=uc1:'for serial port input. Currently no way of altering baud 
rate, on the to-do list.


Search out this old thread:
[M100] Re-directing CP/M console to serial port in REXCPM

Philip

On 21/03/2024 12:02 pm, Will Senn wrote:
over on Vcf, I asked about whether serial over console was possible 
and they said:



CP/M is basically indifferent about the details of the console,
that being contained within the BIOS created by the vendor for
the platform you're running on. I'm not familiar with the M100
platform, but if it has a serial port, *AND* the vendor
implemented CP/M "I/O redirection" in their BIOS, then you can
use STAT to re-assign the console to a serial port. You have to
determine which of the devices is the serial port, but then
you'd issue a command like "STAT CON:=TTY:" after which you
should see the "A>" prompt on the serial port. Note that if you
reassign the console to the wrong device, you won't be able to
issue the command to return to the original console device
(e.g. "STAT CON:=CRT:"), and will probably have to RESET and
reboot. Read up on the STAT command, as it can show you the
available device assignments, current assignments, etc.

Which kinda makes sense, but what is the serial port called? CON is 
already TTY, so that's not it. Also, how do I set the baud rate and 
suchlike in CP/M... anyway, " it has a serial port, *AND* the 
vendor implemented CP/M "I/O redirection" in their BIOS"... does 
anyone know if this is the case?


Thanks,

Will

Re: [M100] Serial over Console in CP/M

[Philip Avery]

Yes, 19200 (98N1D) as stated in 'Initialising RS-232" 
http://bitchin100.com/wiki/index.php?title=M100_CP/M


however, maybe one can initialise in TELCOM to a different baud rate...

Philip

On 21/03/2024 3:26 pm, Will Senn wrote:

What is the default baud rate? Are the other settings - 8n1?

On 3/20/24 20:53, Philip Avery wrote:
Yes, the IO byte is fully implemented in M100 CP/M. Use 'stat 
con:=uc1:'for serial port input. Currently no way of altering baud 
rate, on the to-do list.


Search out this old thread:
[M100] Re-directing CP/M console to serial port in REXCPM

Philip

On 21/03/2024 12:02 pm, Will Senn wrote:
over on Vcf, I asked about whether serial over console was possible 
and they said:



CP/M is basically indifferent about the details of the console,
that being contained within the BIOS created by the vendor for
the platform you're running on. I'm not familiar with the M100
platform, but if it has a serial port, *AND* the vendor
implemented CP/M "I/O redirection" in their BIOS, then you can
use STAT to re-assign the console to a serial port. You have to
determine which of the devices is the serial port, but then
you'd issue a command like "STAT CON:=TTY:" after which you
should see the "A>" prompt on the serial port. Note that if you
reassign the console to the wrong device, you won't be able to
issue the command to return to the original console device (e.g.
"STAT CON:=CRT:"), and will probably have to RESET and reboot.
Read up on the STAT command, as it can show you the available
device assignments, current assignments, etc.

Which kinda makes sense, but what is the serial port called? CON is 
already TTY, so that's not it. Also, how do I set the baud rate and 
suchlike in CP/M... anyway, " it has a serial port, *AND* the vendor 
implemented CP/M "I/O redirection" in their BIOS"... does anyone 
know if this is the case?


Thanks,

Will

Re: [M100] Serial over Console in CP/M

[Will Senn]

Way back in 2021, Tom Hoppe said:

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 
portstat 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. TomOn Tue, Nov 16, 2021 at 2:55 PM Tom Hoppe http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com>> wrote:Correct, VT100 emulation.On Tue, Nov 16, 2021 at 2:15 PM 
Stephen Adolph http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.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 happeningM100 >   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 http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.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 :).TomOn Tue, Nov 16, 2021 at 11:21 AM Jim Anderson http://lists.bitchin100.com/listinfo.cgi/m100-bitchin100.com>> wrote:

Here's what I did that didn't work:

1. Fire up M100
2. CTL-C to get into CP/M
3. Change Sc to S and Cu to S (tried with M100 on F3, tried with RS23)
4. in CP/M, type stat con:=uc1:
5. in Linux, type minicom (/dev/ttyUSB0, VT102, 19200 8N1)

I don't get input or output at the linux side of things and on the m100, 
it isn't responsive after doing stat, cuz it's waiting for serial 
in/out, right?


What'd I do wrong? Is additional setup on the M100 required or some 
setting in minicom (it claims to be offline in the status bar).


Also, what does this mean:

/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)/

Is this the same F3 from CP/M to go between (M100, RS23, or CASS) or is 
it something else, if it's the same which one is the right one. If it's 
different, where is it and what to set it to.


Thanks,

Will


On 3/20/24 8:53 PM, Philip Avery wrote:
Yes, the IO byte is fully implemented in M100 CP/M. Use 'stat 
con:=uc1:'for serial port input. Currently no way of altering baud 
rate, on the to-do list.


Search out this old thread:
[M100] Re-directing CP/M console to serial port in REXCPM

Philip

On 21/03/2024 12:02 pm, Will Senn wrote:
over on Vcf, I asked about whether serial over console was possible 
and they said:



CP/M is basically indifferent about the details of the console,
that being contained within the BIOS created by the vendor for
the platform you're running on. I'm not familiar with the M100
platform, but if it has a serial port, *AND* the vendor
implemented CP/M "I/O redirection" in their BIOS, then you can
use STAT to re-assign the console to a serial port. You have to
determine which of the devices is the serial port, but then you'd
issue a command like "STAT CON:=TTY:" after which you should see
the "A>" prompt on the serial port. Note that if you reassign the
console to the wrong device, you won't be able to issue the
command to return to the original console device (e.g. "STAT
CON:=CRT:"), and will probably have to RESET and reboot. Read up
on the STAT command, as it can show you the available device
assignments, current assignments, etc.

Which kinda makes sense, but what is the serial port called? CON is 
already TTY, so that's not it. Also, how do I set the baud rate and 
suchlike in CP/M... anyway, " it has a serial port, *AND* the vendor 
implemented CP/M "I/O redirection" in their BIOS"... does anyone know 
if this is the case?


Thanks,

Will

Re: [M100] Serial over Console in CP/M

[Will Senn]

What is the default baud rate? Are the other settings - 8n1?

On 3/20/24 20:53, Philip Avery wrote:
Yes, the IO byte is fully implemented in M100 CP/M. Use 'stat 
con:=uc1:'for serial port input. Currently no way of altering baud 
rate, on the to-do list.


Search out this old thread:
[M100] Re-directing CP/M console to serial port in REXCPM

Philip

On 21/03/2024 12:02 pm, Will Senn wrote:
over on Vcf, I asked about whether serial over console was possible 
and they said:



CP/M is basically indifferent about the details of the console,
that being contained within the BIOS created by the vendor for
the platform you're running on. I'm not familiar with the M100
platform, but if it has a serial port, *AND* the vendor
implemented CP/M "I/O redirection" in their BIOS, then you can
use STAT to re-assign the console to a serial port. You have to
determine which of the devices is the serial port, but then you'd
issue a command like "STAT CON:=TTY:" after which you should see
the "A>" prompt on the serial port. Note that if you reassign the
console to the wrong device, you won't be able to issue the
command to return to the original console device (e.g. "STAT
CON:=CRT:"), and will probably have to RESET and reboot. Read up
on the STAT command, as it can show you the available device
assignments, current assignments, etc.

Which kinda makes sense, but what is the serial port called? CON is 
already TTY, so that's not it. Also, how do I set the baud rate and 
suchlike in CP/M... anyway, " it has a serial port, *AND* the vendor 
implemented CP/M "I/O redirection" in their BIOS"... does anyone know 
if this is the case?


Thanks,

Will

Re: [M100] Serial over Console in CP/M

[Philip Avery]

Yes, the IO byte is fully implemented in M100 CP/M. Use 'stat 
con:=uc1:'for serial port input. Currently no way of altering baud rate, 
on the to-do list.


Search out this old thread:
[M100] Re-directing CP/M console to serial port in REXCPM

Philip

On 21/03/2024 12:02 pm, Will Senn wrote:
over on Vcf, I asked about whether serial over console was possible 
and they said:



CP/M is basically indifferent about the details of the console,
that being contained within the BIOS created by the vendor for the
platform you're running on. I'm not familiar with the M100
platform, but if it has a serial port, *AND* the vendor
implemented CP/M "I/O redirection" in their BIOS, then you can use
STAT to re-assign the console to a serial port. You have to
determine which of the devices is the serial port, but then you'd
issue a command like "STAT CON:=TTY:" after which you should see
the "A>" prompt on the serial port. Note that if you reassign the
console to the wrong device, you won't be able to issue the
command to return to the original console device (e.g. "STAT
CON:=CRT:"), and will probably have to RESET and reboot. Read up
on the STAT command, as it can show you the available device
assignments, current assignments, etc.

Which kinda makes sense, but what is the serial port called? CON is 
already TTY, so that's not it. Also, how do I set the baud rate and 
suchlike in CP/M... anyway, " it has a serial port, *AND* the vendor 
implemented CP/M "I/O redirection" in their BIOS"... does anyone know 
if this is the case?


Thanks,

Will

Re: [M100] Failed "," key

[Peter Vollan]

I should have watched your video before I shot my mouth off; now I see that
the 102's keyswitches are different that the 100's. Where can I get the
keycap tool?

On Wed, 20 Mar 2024 at 00:26, Brian K. White  wrote:

> I had to search to find:
> "There is exactly one key on my m100's keyboard that rufuses to work,
> the K key."
>
> What was anyone supposed to do with that?
>
> What I said below and the video wouldn't help with a 100. It only
> applies to a 102.
>
> 100 has a totally different kind of keyswitch, and no similar easy
> possible fix to try, other than just wash the switch with distilled
> water (to clean out possible sugars from drinks), then alcohol (to dry
> the water), then deoxit (to refresh the actual copper contacts inside),
> and actuate the switch a bunch of times (after the deoxit soaks a while,
> you also need a little mechanical action to actually scrub away the
> oxidized surface).
>
> If simply washing and deoxit doesn't make it work, then you have to look
> for corroded traces, loose solder joints, desolder and disassemble the
> keyswitch itself, maybe replace from ebay (the switches are available
> sometimes).
>
> --
> bkw
>
> On 3/20/24 00:36, Peter Vollan wrote:
> > It would have been nice if you guys had helped me out with this when I
> > recently posted that my "K" key had inexplicably quit. I swapped the
> > keycap out with the ESC key because that is rarely used; I didn't think
> > of the extra shift key. Long story short, I overestimated my abilities
> > and thought I had wrecked my unit permanently, but by hook or by crook,
> > and solder bridges and resistor legs, my keyboard was fixed. Except for
> > the escape key. Actually the cassette relay and the modem don't work,
> > but I think that is from changing those resistors and replacing the
> > backup battery. Don't see how it could be the keyboard.
> >
> > On Mon, 18 Mar 2024 at 08:58, Brian White  > > wrote:
> >
> > 102 has carbon impregnated silicone rubber domes like calculator or
> > remote buttons.
> >
> > With care it's possible to lift the top of the key switch body off
> > and lift out the rubber dome, and see if the contacts or button are
> > dirty. Maybe use some deoxit with a q-tip to clean the contacts,
> > maybe clean the carbon pad.
> >
> > I had a stuck T key where everything looked fine but the carbon pad
> > maybe just looked worn. I swapped the rubber dome with the
> > right-shift key (a key that I don't use as much, and has a duplicate
> > on the left anyway, and was much less worn because all the previous
> > owners probably used it less than T also) and afterwards not only
> > did the T work, the right shift still worked!
> >
> > To get the keyswitch apart, I don't know how to verbally describe
> > everything clearly. I made a video
> >
> > https://youtu.be/n_oyDYRDYzs 
> >
> >
> > bkw
> >
> > On Sun, Mar 17, 2024, 10:47 PM Ronald Hudson  > > wrote:
> >
> > Hi Everyone--
> >
> >
> > My 102 has a failed "," key - all the other keys seem to work so
> > I am
> > guessing it is a bad key or broken trace.
> >
> > What say ye?
> >
> >
> > Thanks!
> >
> > Ron.
> >
>
> --
> bkw
>
>

[M100] Serial over Console in CP/M

[Will Senn]

over on Vcf, I asked about whether serial over console was possible and 
they said:



   CP/M is basically indifferent about the details of the console, that
   being contained within the BIOS created by the vendor for the
   platform you're running on. I'm not familiar with the M100 platform,
   but if it has a serial port, *AND* the vendor implemented CP/M "I/O
   redirection" in their BIOS, then you can use STAT to re-assign the
   console to a serial port. You have to determine which of the devices
   is the serial port, but then you'd issue a command like "STAT
   CON:=TTY:" after which you should see the "A>" prompt on the serial
   port. Note that if you reassign the console to the wrong device, you
   won't be able to issue the command to return to the original console
   device (e.g. "STAT CON:=CRT:"), and will probably have to RESET and
   reboot. Read up on the STAT command, as it can show you the
   available device assignments, current assignments, etc.

Which kinda makes sense, but what is the serial port called? CON is 
already TTY, so that's not it. Also, how do I set the baud rate and 
suchlike in CP/M... anyway, " it has a serial port, *AND* the vendor 
implemented CP/M "I/O redirection" in their BIOS"... does anyone know if 
this is the case?


Thanks,

Will

Re: [M100] Failed "," key

[Peter Vollan]

Just one thing at this time... took the switch out and checked it with a
multimeter, it is the switch

On Wed, 20 Mar 2024 at 00:26, Brian K. White  wrote:

> I had to search to find:
> "There is exactly one key on my m100's keyboard that rufuses to work,
> the K key."
>
> What was anyone supposed to do with that?
>
> What I said below and the video wouldn't help with a 100. It only
> applies to a 102.
>
> 100 has a totally different kind of keyswitch, and no similar easy
> possible fix to try, other than just wash the switch with distilled
> water (to clean out possible sugars from drinks), then alcohol (to dry
> the water), then deoxit (to refresh the actual copper contacts inside),
> and actuate the switch a bunch of times (after the deoxit soaks a while,
> you also need a little mechanical action to actually scrub away the
> oxidized surface).
>
> If simply washing and deoxit doesn't make it work, then you have to look
> for corroded traces, loose solder joints, desolder and disassemble the
> keyswitch itself, maybe replace from ebay (the switches are available
> sometimes).
>
> --
> bkw
>
> On 3/20/24 00:36, Peter Vollan wrote:
> > It would have been nice if you guys had helped me out with this when I
> > recently posted that my "K" key had inexplicably quit. I swapped the
> > keycap out with the ESC key because that is rarely used; I didn't think
> > of the extra shift key. Long story short, I overestimated my abilities
> > and thought I had wrecked my unit permanently, but by hook or by crook,
> > and solder bridges and resistor legs, my keyboard was fixed. Except for
> > the escape key. Actually the cassette relay and the modem don't work,
> > but I think that is from changing those resistors and replacing the
> > backup battery. Don't see how it could be the keyboard.
> >
> > On Mon, 18 Mar 2024 at 08:58, Brian White  > > wrote:
> >
> > 102 has carbon impregnated silicone rubber domes like calculator or
> > remote buttons.
> >
> > With care it's possible to lift the top of the key switch body off
> > and lift out the rubber dome, and see if the contacts or button are
> > dirty. Maybe use some deoxit with a q-tip to clean the contacts,
> > maybe clean the carbon pad.
> >
> > I had a stuck T key where everything looked fine but the carbon pad
> > maybe just looked worn. I swapped the rubber dome with the
> > right-shift key (a key that I don't use as much, and has a duplicate
> > on the left anyway, and was much less worn because all the previous
> > owners probably used it less than T also) and afterwards not only
> > did the T work, the right shift still worked!
> >
> > To get the keyswitch apart, I don't know how to verbally describe
> > everything clearly. I made a video
> >
> > https://youtu.be/n_oyDYRDYzs 
> >
> >
> > bkw
> >
> > On Sun, Mar 17, 2024, 10:47 PM Ronald Hudson  > > wrote:
> >
> > Hi Everyone--
> >
> >
> > My 102 has a failed "," key - all the other keys seem to work so
> > I am
> > guessing it is a bad key or broken trace.
> >
> > What say ye?
> >
> >
> > Thanks!
> >
> > Ron.
> >
>
> --
> bkw
>
>

Re: [M100] mvt100 and the pc terminal

[jonathan.y...@telia.com]

Hello WIll,
I think I have played around the most with wordstar 3.3.  I never tried 4.0 and 
that was different source code which didn't agree with my poking around with 
DDT.  I've seen 3.3 on different web sites for download. You can patch some of 
the keyboard lookup tables to agree with the M100 keyboard, arrows and such and 
so that the DEL key deletes the character under the cursor and the backspace 
key erases the previous character.  You would to look at  'Wordstar 
Customization Notes' (there is a copy on archive.org) and while it is for 3.0, 
the general layout is the same and the lookup tables can be found in the .com 
file with a bit of searching even though the addresses in 3.3 are not the same 
as 3.0.  I don't think wordstar would be happy with a 40 x 8 character display. 
 
I posted on this before and it is in the archives somewhere
Jonathan
Original Message
>From : will.s...@gmail.com
Date : 2024-03-19 - 22:34 (CEST)
To : m...@bitchin100.com
Subject : Re: [M100] mvt100 and the pc terminal
 Hi Jonathan,
 
 
 What version of Wordstar?
 
 
 Thanks,
 
 
 Will
 
 
 On 3/19/24 3:42 AM, 
 jonathan.y...@telia.com wrote:
 
 
 
  If you are going to play a lot with CP/M on the M100, the MVT100 device is a 
good thing to have, since a LOT of the CP/M programs want a bigger display.  
With the MVT100, you can get 80x24 characters after you connect a VGA device.  
I have used a VGA to HDMI converter and actually can use an android tablet (or 
even my phone) as a display.  You can run Wordstar under CP/M on the M100.  
CP/M adventure got a bit messed up on the M100 screen but on the MVT100 it was 
just fine.
  
 
 
  
 
 
  The device also can take a keyboard and then it runs more or less like a real 
VT100 but I don't think the gold key etc. are mapped..
 
 
  
 
 
  Jonathan
  
 
 
  Original Message
  
 From : 
  will.s...@gmail.com
  
 Date : 2024-03-19 - 01:07 (CEST)
  
 To : 
  m100@lists.bitchin100.com
  
 Subject : [M100] mvt100 and the pc terminal
  
  
  
  I'm a little confused about the MVT100... 
 on this page:
https://bitchin100.com/wiki/index.php?title=MVT100_Desktop_Application
 It sounds like it's a terminal emulator for connecting to the M100 over 
serial. But somewhere else I saw it as some kind of adapter to talk to VGA. I'm 
guessing it's both - adapter gadget provides the VGA out thing and provides a 
server for the pc terminal app? I downloaded the software and it runs fine on 
linux under wine (to the degree that it appears to start up and not crash. I 
couldn't figure out how to get it to talk to my m100... so I'm guessing I need 
the hardware gadget in addition to my rexcpm to get it working?
 Thanks,
 Will
  
 
 

Re: [M100] Failed "," key

[Brian K. White]

I had to search to find:
"There is exactly one key on my m100's keyboard that rufuses to work, 
the K key."


What was anyone supposed to do with that?

What I said below and the video wouldn't help with a 100. It only 
applies to a 102.


100 has a totally different kind of keyswitch, and no similar easy 
possible fix to try, other than just wash the switch with distilled 
water (to clean out possible sugars from drinks), then alcohol (to dry 
the water), then deoxit (to refresh the actual copper contacts inside), 
and actuate the switch a bunch of times (after the deoxit soaks a while, 
you also need a little mechanical action to actually scrub away the 
oxidized surface).


If simply washing and deoxit doesn't make it work, then you have to look 
for corroded traces, loose solder joints, desolder and disassemble the 
keyswitch itself, maybe replace from ebay (the switches are available 
sometimes).


--
bkw

On 3/20/24 00:36, Peter Vollan wrote:
It would have been nice if you guys had helped me out with this when I 
recently posted that my "K" key had inexplicably quit. I swapped the 
keycap out with the ESC key because that is rarely used; I didn't think 
of the extra shift key. Long story short, I overestimated my abilities 
and thought I had wrecked my unit permanently, but by hook or by crook, 
and solder bridges and resistor legs, my keyboard was fixed. Except for 
the escape key. Actually the cassette relay and the modem don't work, 
but I think that is from changing those resistors and replacing the 
backup battery. Don't see how it could be the keyboard.


On Mon, 18 Mar 2024 at 08:58, Brian White > wrote:


102 has carbon impregnated silicone rubber domes like calculator or
remote buttons.

With care it's possible to lift the top of the key switch body off
and lift out the rubber dome, and see if the contacts or button are
dirty. Maybe use some deoxit with a q-tip to clean the contacts,
maybe clean the carbon pad.

I had a stuck T key where everything looked fine but the carbon pad
maybe just looked worn. I swapped the rubber dome with the
right-shift key (a key that I don't use as much, and has a duplicate
on the left anyway, and was much less worn because all the previous
owners probably used it less than T also) and afterwards not only
did the T work, the right shift still worked!

To get the keyswitch apart, I don't know how to verbally describe
everything clearly. I made a video

https://youtu.be/n_oyDYRDYzs 


bkw

On Sun, Mar 17, 2024, 10:47 PM Ronald Hudson mailto:hudson...@live.com>> wrote:

Hi Everyone--


My 102 has a failed "," key - all the other keys seem to work so
I am
guessing it is a bad key or broken trace.

What say ye?


Thanks!

Ron.



--
bkw