DataMuseum.dk

top - metrics - download

    Length: 2697 (0xa89)
    Types: TextFile
    Names: »msxv90.msg«

└─⟦9ae75bfbd⟧ Bits:30007242 EUUGD3: Starter Kit
    └─⟦71044c191⟧ »EurOpenD3/misc/kermit.ms-2.32.tar.Z« 
        └─⟦31f2d420d⟧ 
            └─⟦this⟧ »msxv90.msg« 

TextFile

26-Apr-86 01:00:08-EST,2714;000000000011
Received: from CUVMA by CU20B with HASP; 26 Apr 86 01:00:06 EST
Received: by CUVMA (Mailer X1.23a) id 8476; Sat, 26 Apr 86 01:00:10 EST
Date: 04/26 00:29:49
From: FDCCU@CUVMA
Subject: PETERSON MAIL - PUN file from RSCS
Tag: FILE (7560) ORIGIN BYUVAX   PETERSON  4/26/86  0:31:55 E.S.T.
To: SY.FDC@CU20B
Reply-To: PETERSON@BYUVAX

Date:     Fri, 25-APR-1986 22:31 MST
From:     Bryan Peterson <PETERSON@BYUVAX>
Subject:  KERMIT 2.29 (2.28 jrd/5g) for Victor
To:       fdccu@cuvma


Following are 5 files for Kermit for the Victor 9000/Sirius:

MSXV90.ASM - System dependent I/O file
MSYV90.ASM - Terminal emulation (Heath and VT100)
MSYV9T.ASM - Terminal emulation (Heath, VT100, and Tektronix)
MSKV90.BOO - Boot file from MSYV90 (Heath and VT100 emulation)
MSKV9T.BOO - Boot file from MSYV9T (Heath, VT100, and Tektronix emulation)

Some differences from the 2.28 files:

The emulation is set by SET TERMINAL xxxxx, where xxxxx is either HEATH
or VT100 (or TEKTRONIX for MSKV9T).

The screen region for the Tektronix terminal is now above the program and
data areas.  When Kermit is started up, the screen memory is obtained from
DOS and checked to be sure that it is in a valid area.  If the allocation
process fails to obtain a valid screen area, a warning message is issued
regarding Tektronix emulation, and that option is disabled.

Even though the STATUS command will show TERMINAL EMULATION as NONE when
doing Tektronix emulation, the correct way to select Tektronix emulation
is SET TERMINAL TEKTRONIX.

VT100 emulation code was obtained from Andreas Stumpf in Germany
(DS0RUS1I::ZRZS) and integrated with the previous files.  The emulation is
not complete, but it does work with the VAX EDT editor in screen mode and
with software using either FMS-generated forms or the new SMG screen
management subroutines on the VAX systems.  Further testing has not been
reported - that is all I personally have access to.

The routines to get and set the terminal baud rate have been cleaned up
some and modified to use the MSDOS IOCTL function top directly access the
serial port driver.  Thus, the default baud rate is the one that was specified
the last time the serial port driver was set up (usually at system boot time).
Note that the code in this section expects the devices to be named SERIALA
and SERIALB, as they are supplied from VICTOR.

These files should not be considered complete - they are still being tested
and are provided for others who may want to test them.

                                        Bryan Peterson
                                        BYU Physics Dept.
                                        Bitnet Peterson@BYUVAX