Hi,
Yes I realize that the stock vt100 emulation doesn't support the m100 escape 
codes.  I've only done this with rexcpm and it's a patched version of wordstar 
that intercepts the m100 cursor keys and gets the program to do what one 
expects.  I actually haven't gotten around to using the more m100-specific 
things, probably because I was so familiar with cpm .
Jonathan
----Ursprungligt meddelande----
Från : twospru...@gmail.com
Datum : 2021-01-20 - 15:59 (CEST)
Till : m...@bitchin100.com
Ämne : Re: [M100] vga monitor solutions
 Jonathan,
 
  
  
   The difference is that your use case is this:
  
  
   'M100 (CP/M) --->  RS-232--->FTDI --> USB--->PC'  
   
  
  
   
  
  
   (that is to say, I think you are running M100CP/M on REXCPM)
  
  
   
  
  
   In this case, stock VT100 works fine because there are no custom M100 ESC 
codes.
  
  
   
  
  
   Just to reiterate, 
  
  
   If the goal is to extend the native M100 OS to leverage external video, then 
you have to have an external video solution that can cope with the necessary 6 
additional ESC codes.
  
  
   
  
  
   Here is an example of why.
  
  
   In M100 BASIC, you can lock the bottom row of the screen to show the setting 
of the Function keys.   Such a function does not exist in standard VT100.
  
  
   
  
  
   
  
  
   ..Steve
  
 
 
  On Wed, Jan 20, 2021 at 9:47 AM 
  jonathan.y...@telia.com <
  jonathan.y...@telia.com> wrote:
  
 
 
  
   Hello,
  
  
   
  
  
   I think a lot of the terminal emulation programs for a PC already emulate a 
VT100.
   
  
  
   
  
  
   I did the 'M100 (with VT100 driver) --->  RS-232--->FTDI --> USB--->PC' just 
for fun, using minicom under linux.  This worked just fine, the normal 'xterm' 
under linux is vt100 compatible, so I could run wordstar or supercalc on the 
m100, and look at the output on an xterm with minicom running under xwindows.  
Not sure WHY I would do that, but I realized that it should work and it was 
just a matter of plugging in the FTDI serial device to a usb port on the  
computer. I bootstrapped the rexcpm using minicom to upload the rxcini.do file.
   
  
  
   
  
  
   A custom app for android that could interpret the vt100 codes would save a 
lot of hardware.  Would be even nicer if it could switch to the m100 codes but 
I imagine the number of people that would use that aspect is rather limited. 
   
  Since I generally use mcomm to put things in and out of the m100, a custom 
app would use the same hardware--basically just the FTDI adapter and the right 
cables.
  
  
   
  
  
   I haven't uploaded any pictures of this because it is kind of a mess with 
cables and adapters running all over the place.  I'm starting to think about 
custom-made USB power cables just to reduce the tangle.
   
  
  
   
  
  
   Jonathan
   
  
  
   ----Ursprungligt meddelande----
   
Från : 
   twospru...@gmail.com
   
Datum : 2021-01-20 - 13:32 (CEST)
   
Till : 
   m...@bitchin100.com
   
Ämne : Re: [M100] vga monitor solutions
   
   
   
    
     
    
    
      Thanks Jonathan, very cool. Stitching it together like that is a nice 
combination of solutions. 
    
    
     
    
    
      So this is more representative- 
     
    
    
      M100 (with VT100 driver) --->  
RS-232--->MVT100--->VGA---->converter--->HDMI ---->video capture --> 
USB--->tablet 
    
    
     
    
    
     
       This might be possible with a new app (like a VT100 terminal app + 6 
custom ESC codes)- 
      
     
     
       M100 (with VT100 driver) --->  RS-232--->FTDI --> USB--->tablet 
     
     
      
     
     
       This is also a possibility, with a new application (like a VT100 
terminal app + 6 custom ESC codes) - 
     
     
       M100 (with VT100 driver) --->  RS-232--->PC 
     
     
       M100 (with VT100 driver) --->  RS-232--->FTDI --> USB--->PC 
     
     
      
     
     
       This being the 'standard' MVT100 adapter approach- 
     
     
       M100 (with VT100 driver) --->  RS-232--->MVT100-->VGA--> VGA monitor 
     
     
      
     
     
      
     
    
   
   
  
  
  
 

Reply via email to