09/02/94: OSTerm/68K by Delphi, | Category: Delphi - Applications 6809 | 20 comments - (Comments are closed)

OSTerm/68K

89699 2-SEP 00:25 Applications (6809)
OSTerm/68K
From: KSCALES To: TIMKIENTZLE

> I’d be interested in hearing about this new OSTerm/68k. I always
> thought OSTerm/Tascom had a lot of potential, but fell down in
> the details (file transfer bugs, emulation bugs, etc.). I’d
> be interested to hear that someone addressed those problems.

Hi, Tim -

Yes, OSTerm/68K has been considerably enhanced compared with OSTerm/6809
and TasCOM. The current official release is version 2.2.0; however a few
folks have a “beta test” version 2.2.1.

I don’t have a complete list of the changes, but will list the ones that
come to mind… (I’ve included some of the known limitations, too.)

– (prompted) ASCII file transfers are now fully implemented. (Vaughn
added them to the menus when he started working on them, but hadn’t
yet finished the code.)
– Y-batch no longer resets the filelength to 0 on ASCII transfers.
(Side-effect: sometimes the xmodem padding will not be stripped.
Perhaps a future release will cover this.)
– provision added for 3 external protocols. These are defined by the
user in the osterm.config file, and become bound into the standard
OSTerm Transfer and Filepicker menu sequences, just like the native
protocols, so they appear fully integrated to the user. (I use Zmodem,
Kermit Binary, and Kermit ASCII).
– ANSI emulation has been enhanced to include all of the normal
IBM/BBS sequences, 16 foreground and 8 background colours (with
correct palettes).
– VT100 emulation has been significantly enhanced:
– host programmable tabs (also, user settable in config file; default
is the VT100 standard default)
– scrolling regions (Version 2.2.0 only has absolute origin mode;
V2.2.1 beta has relative origin mode, too).
– User selectable “Newline mode” and “Autowrap at margin” added
– many other changes/fixes too numerous to mention to bring it in
line with the VT102 “ANSI” mode.
– limitations: special character sets not supported; 80×24 mode only.
– improved ANSI/VT100 keyboard emulations (e.g., “left arrow” and “ctrl-B”
are differentiated), with online “Keyboard Assignments” menu
– can generate a true “line break”
– RTS/CTS or XON/XOFF flow control supported.
– “Rate adjust” lock to suppress autobauding for modern high-speed modems
– separate Options file for each port (/t0, /t3, etc.)
– “Echo to file” (buffer capture) now strips linefeeds AND ANSI/VT100
control sequences. Also allows append-to-file.
– A “binary” emulation mode has been added, to enable capture of all
received data, but only printing “safe” characters to the screen.
– Remote Mode can be enterred directly from command line:
osterm -r
(or) osterm -r=/dd/directory_path_to_use
– 7-bit mask (oops; bug in V2.2.0; fixed in V2.2.1 beta version)
– numbers expanded to 24-digits in autodialer
– a “graphical front end” for mouse addicts and to make it easier for
casual users. This is, frankly, a bit “clumsier” than we would like,
but since our plans are to evolve OSTerm/68K away from its current
K-Windows dependency, we implemented this as a separate module (“OST”)
to avoid putting more K-Windows stuff into the main program.
– significantly improved manual written by Colin McKay.
– many other tweeks and enhancements.

Hope this provides the info you wanted.

Cheers… / Ken
————————————————————————–
Ken Scales Delphi:KSCALES Internet:kscales [at] delphi [dot] com CIS:74646,2237

20 comments to OSTerm/68K

  • pucc_unknown

    89715 3-SEP 12:29 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89699)
    From: JEJONES To: KSCALES

    > – User selectable “Newline mode” and “Autowrap at margin” added

    I guess that just show that when all else fails, read the directions.
    (I must have autowrap turned off.) Silly me.

    Seriously–I appreciate the heck out of the work that’s been done
    on OSTerm.

    Opinions herein are solely those of their respective authors.

    Clipper Chip: Big Brother Inside

  • pucc_unknown

    89725 3-SEP 21:24 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89699)
    From: DBREEDING To: KSCALES

    TIMKIENTZLE’s comments:
    > > I’d be interested in hearing about this new OSTerm/68k. I always
    > > thought OSTerm/Tascom had a lot of potential,

    > > but fell down in the details

    GREAT DESCRIPTION!!! CoCo OSTerm is really great, but just a few aggravating
    details.

    Ken,

    The enhancements you describe are FANTASTIC! Do I understand that the
    ultimate goal is to make OSTerm compatible for all OSK platforms, or will
    it be strictly MM/1? I have a Delmar system and would really love to have
    OSTerm running on it. IMO, this is one void (especially for us non-MM1′ers)
    that needs to be filled.

    — David Breeding –
    CompuServe : 72330,2051
    Delphi : DBREEDING

    *** Sent via CoCo-InfoXpress V1.01 ***
    ^^^^ ^^^^^^^^^^

  • pucc_unknown

    89757 5-SEP 02:04 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89699)
    From: TIMKIENTZLE To: KSCALES

    Sounds good! In particular, it sounds like you made an effort to address
    the many problems in the VT100 emulation. (BTW, if you want, I have
    a bunch of test files for testing VT100, in the form of a fairly
    thorough `test program’ and a bunch of `VT100 movies’ that exercise
    VT100 emulations pretty thoroughly. The test program also exercises
    some VT102 functions. Old OSTerm/Tascom failed these tests pretty
    badly. Seems it kept switching into `ANSI’ emulation for no apparent
    reason.)
    – Tim

  • pucc_unknown

    89774 5-SEP 21:14 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89699)
    From: DSRTFOX To: KSCALES

    When you get a good listing of all the changes/features of the new term
    program, send me something in e-mail that I can print as an announcement in the
    next issue of “68′ micros”.

  • pucc_unknown

    89732 3-SEP 23:38 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89715)
    From: KSCALES To: JEJONES

    > I guess that just show that when all else fails, read the directions.
    > (I must have autowrap turned off.) Silly me.

    Heh, heh — yeah, I know what you mean. I don’t pay enough attention
    to the manuals, either. But let’s not tell Colin — he put a lot of
    work into it .

    Didn’t know you had been encountering difficulties — let me know if the
    autowrap doesn’t fix it.

    > Seriously–I appreciate the heck out of the work that’s been done
    > on OSTerm.

    Thanks. Actually, we did it a lot of it because _we_ wanted it, too!

    Cheers… / Ken
    ————————————————————————–
    Ken Scales Delphi:KSCALES Internet:kscales [at] delphi [dot] com CIS:74646,2237

  • pucc_unknown

    89733 3-SEP 23:38 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89725)
    From: KSCALES To: DBREEDING

    > The enhancements you describe are FANTASTIC! Do I understand that the
    > ultimate goal is to make OSTerm compatible for all OSK platforms, or will
    > it be strictly MM/1? I have a Delmar system and would really love to
    > have OSTerm running on it. IMO, this is one void (especially for us
    > non-MM1′ers) that needs to be filled.

    This has been the plan, but office workload has pretty much brought things
    to a grinding halt here since May. We had hoped to have the non-KWindows
    version well under development by now, but as it stands, that phase hasn’t
    even been begun, yet. Sorry, but stay tuned.

    Regards… / Ken
    ————————————————————————–
    Ken Scales Delphi:KSCALES Internet:kscales [at] delphi [dot] com CIS:74646,2237

  • pucc_unknown

    89784 5-SEP 22:59 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89733)
    From: DBREEDING To: KSCALES

    > > The enhancements you describe are FANTASTIC! Do I understand that the
    > > ultimate goal is to make OSTerm compatible for all OSK platforms, or

    > This has been the plan, but office workload has pretty much brought
    > things to a grinding halt here since May. We had hoped to have the
    > non-KWindows version well under development by now, but as it stands, that
    > phase hasn’t even been begun, yet. Sorry, but stay tuned.

    You bet I’ll stay tuned .. I’ve heard of another Term program that’s coming
    out, maybe for G-Windows, but everyone needs at least 3 term programs at
    hand . Seriously, I’ve grown quite accustomed to OSTerm, and all in all,
    it’s just hard to beat. I do understand the problems of getting time to
    get all the stuff done, though.

    — David Breeding –
    CompuServe : 72330,2051
    Delphi : DBREEDING

    *** Sent via CoCo-InfoXpress V1.01 ***
    ^^^^ ^^^^^^^^^^

  • pucc_unknown

    89814 7-SEP 02:15 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89733)
    From: AJMLFCO To: KSCALES

    Ken,
    I’d like to include my vote(s) on OSterm. I ran it on
    my CoCo and miss it now that I have the Kix\30 with
    Gwindows. My friend, who is using OS9000 on his ’486
    would also like to see a Gwindows port of Osterm. He is
    planning on ordering Gwindows this week for OS9000. I also
    have some friends in industry who use Gwindows/68k on VME
    and they have asked me for my recommendations on a good
    terminal program–what can I recommend?

    Allen Morgan

  • pucc_unknown

    89789 5-SEP 23:15 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89757)
    From: KSCALES To: TIMKIENTZLE (NR)

    Hi, Tim -

    > Sounds good! In particular, it sounds like you made an effort to address
    > the many problems in the VT100 emulation.

    Yes, we’ve put considerable work towards making this a good, usable
    implementation of VT100 emulation. We probably still have a bit more work
    to do. My personal approach is that ANY _known_ limitations or bugs should
    be documented, so the following exclusions were specified in the $READ.ME$
    file for V2.2.0, released at the May Chicago Fest:

    | Current limitations include:
    |
    | – only absolute origin mode is supported for scrolling regions
    | – only 80×24 character mode is supported (no double-height,
    | double width, nor 132 character width)
    | – alternate character sets are not supported
    |
    | Known bugs/deficiencies:
    | – the last character on a screen is not displayed, as this
    | causes the screen to scroll. When the line is scrolled,
    | this character will be added to the scrolled line, except
    | in the following case:
    |
    | – when “Autowrap at margin” is “off”, lines that contain
    | EXACTLY 80 characters and which are initially printed on
    | the last line of the display (or scrolling region), will
    | not display the last character of the line after being
    | scrolled upwards.

    Since then, V2.2.1(beta) has added relative origin mode for scrolling
    regions, and fixed a couple of bugs that were identified (7-bit masking
    within VT100/ANSI sequences, the switching from VT100 to ANSI mode
    “voluntarily” that you mentioned, and improved “bold” attribute handling).

    > (BTW, if you want, I have
    > a bunch of test files for testing VT100, in the form of a fairly
    > thorough `test program’ and a bunch of `VT100 movies’ that exercise
    > VT100 emulations pretty thoroughly. The test program also exercises
    > some VT102 functions.

    Tim, I would really appreciate if you could forward those files. I’ve
    been meaning to pick some up, but it’s always been “deferred”… Most
    of the testing has been against the facilities we have available.

    > Old OSTerm/Tascom failed these tests pretty
    > badly. Seems it kept switching into `ANSI’ emulation for no apparent
    > reason.)

    Heh, heh… yeah, see above.

    Cheers… / Ken
    ————————————————————————–
    Ken Scales Delphi:KSCALES Internet:kscales [at] delphi [dot] com CIS:74646,2237

  • pucc_unknown

    89872 10-SEP 15:08 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89814)
    From: DBREEDING To: AJMLFCO (NR)

    > Ken,
    > I’d like to include my vote(s) on OSterm. I ran it on
    > my CoCo and miss it now that I have the Kix\30 with
    > Gwindows. My friend, who is using OS9000 on his ’486
    > would also like to see a Gwindows port of Osterm.

    If you saw my post, I’m with you on this.. OSTerm became a standby
    with me. For my part, it doesn’t even have to be for G-Windows, just
    text-based would suffice, although some of the menus WOULD be rather
    pretty with windows.

    — David Breeding –
    CompuServe : 72330,2051
    Delphi : DBREEDING

    *** Sent via CoCo-InfoXpress V1.01 ***
    ^^^^ ^^^^^^^^^^

  • pucc_unknown

    89953 14-SEP 21:48 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89789)
    From: TIMKIENTZLE To: KSCALES

    Ken,
    I just uploaded a bunch of VT100 movies that I’ve collected over
    the years. They exercise a lot of the more obscure VT100 functions
    pretty thoroughly. Have fun!
    – Tim

  • pucc_unknown

    90023 20-SEP 00:45 Applications (6809)
    RE: OSTerm/68K (Re: Msg 89953)
    From: KSCALES To: TIMKIENTZLE

    Hi, Tim -

    > I just uploaded a bunch of VT100 movies that I’ve collected over
    > the years. They exercise a lot of the more obscure VT100 functions
    > pretty thoroughly. Have fun!

    Thanks a lot! I spent WAY too much time this weekend “having fun” .
    Thought I would follow up and let you know the results.

    I tried running the files on several different telecom packages to get
    a comparison, and so that I could have a “frame of reference” to see
    any problems that might occur.

    I set up my ’386 running Telix V3.12 (shareware) and the Windows 3.1
    “Terminal” accessory (which I will call “WinTerm” for short).

    On the MM/1, I tried OSTerm/68K V2.2.0 and V2.2.1, as well as a port of
    Brian Marcotte’s “vt100″ program and a beta copy of KTerm.

    I quickly dropped “vt100″, after having to reboot twice after using it.
    (“000:171 (E$Damage) System data structures have been damaged.” following
    one attempt…) I also decided to drop KTerm from the sample, since
    I only had the beta version, and that version didn’t even really claim
    any VT100 capabilities. (We’ll let John D. or David G. cover the
    official release.)

    There was a fairly noticeable difference between OSTerm V2.2.0 (the official
    distributed version most users have), and V2.2.1/beta. The V2.2.1 was
    created to fix some problems reported by Boisy and JEJ. These “movies”
    seemed to trigger several of the changed areas. Guess we’re going to have
    to try to package this update for release RSN… (V2.2.1 has only had
    limited distribution.)

    So, most tests were with OSTerm/68K V2.2.1, Telix, and WinTerm.

    Known limitations of these Emulation packages:
    ==============================================
    – OSTerm:
    – does not support double-height/double-width characters
    – does not support support alternate/special/line drawing character
    sets.
    – Due to the lack of “blinking characters” on the MM/1, these are
    shown using bold font.
    (Note: Since we want to port OSTerm to non-KWindows environments, we
    specifically decided NOT to incorporate these capabilities at this
    time. A bug in K-Windows pushbuttons is another contributing factor…)

    – Telix:
    – does not support double-height/double-width characters

    – Windows Terminal (“WinTerm”)
    – Specific info not available; but from tests:
    – does not appear to support “blinking characters”. They seem to
    show as bold.
    – does not appear to support “newline” mode.

    Results:
    ========
    – General notes:
    1) OSTerm only used the standard character set, and substituted these
    characters for the VT100 special/line-drawing set. This is
    standard behavior for all test files, and should be assumed below.
    2) As stated above, only WinTerm supported double-height,
    double-width characters. Telix and OSTerm behaved similarly when
    these sequences appeared (e.g., “fireworks”, “xmas”), displaying
    double-height characters as duplicated vertically.
    3) Some of the files required “newline” mode to be set externally to
    the file. For OSTerm, this is a menu option (or can be set by
    host). For Telix, I sent the sequence “ESC ( 2 0 h” prior to
    sending the file. I could not find a way to set “newline” mode
    for WinTerm (may not be supported).

    – “beer”
    – Much of the graphics info was missing under WinTerm. This may
    have been due to the use of a monochrome monitor (?).
    – “duck”, “moon”, “sun”, “twilight”:
    – No special notes.
    – “cobol”:
    – See note 3 above (newline).
    – Without “newline” mode, WinTerm performed poorly.
    – “fireworks”:
    – See note 2 above (double-size).
    – Both Telix and OSTerm left some “firework debris” on the screen,
    which may result from double-height/double-width characters.
    Telix also seemed to leave noise from unimplemented VT100
    sequences.
    – “fish”:
    – required “newline off” for OSTerm.
    – “outer_limits”:
    – See note 2 above (double-size).
    – OSTerm performed an extra scroll around the start of the “sine wave”.
    – WinTerm did not handle the “soft blur” as well as Telix, due to the
    poorer special/line character set (or possibly the monochrome
    monitor again).
    – “ship”:
    – See note 3 above (newline).
    – Without “newline” mode, WinTerm was an absolute mess.
    – OSTerm did not “sink the ship”. It was confused by the
    “1B 5B 48 0A 1B 1B 1B 1B … 1B 1B 1B 1B 5B 48 1B 4D 0A 1B …”
    sequences used to create delays; the odd number of $1B’s caused
    it to get out of sync and display the “(H” and “(1;25r” commands.
    Replacing one $1B with a $20 (space) in each sequence fixed this,
    but we’ll need to make the program robust against this.
    – “trek”:
    – Telix did not display the top front of the ship.
    – Telix and OSTerm left some debris from the RCA explosion.
    – WinTerm did not appear to show stars at different intensities.
    – WinTerm and Telix both had the Enterprise partially re-emerge on
    the left side of the screen. OSTerm (“autowrap off”) let it “exit,
    screen right”, while “autowrap on” gave behavior similar to the
    other programs. Dunno which was intended, but I preferred the exit…
    – “xmas”:
    – See notes 2 (double size) and 3 (newline) above.
    – Without “newline” mode, WinTerm was an absolute mess.
    – WinTerm’s special/graphics characters were not as good as Telix’s.
    – Telix mangled the jack-in-the-box.

    Three “bugs” in OSTerm/68K V2.2.1′s VT100 emulation were identified,
    excluding the “non-supported character sets”:
    – handling of sequential “ESC” characters (used in “ship” for time delays).
    – one spurious linefeed in “outer_limits” — cause yet unknown.
    – the “debris” left in “fireworks” and “trek” also needs to be
    investigated to determine the cause (both Telix and OSTerm).

    It sure would be nice to include support for the special/line drawing
    character sets — it would make these “movies” look a lot prettier.
    But our preference right now is not to increase MM/1-specific
    dependencies. I am glad that the basic VT100 protocol support held
    up so well under these files .

    Regards… / Ken

    PS – BTW, Boisy has provided me with a bunch of similar files for ANSI
    graphics, too. Uncovered some interesting things, like IBM ANSI homes
    the cursor after “ESC ( 2 J”, while VT102 in ANSI mode specifically
    does not…

    PPS – You probably are already aware: there are some news groups
    that carry these types of files: alt.binaries.pictures.ascii and
    alt.ascii-art are two I have run across. I picked up a variation
    of “xmas” on one of these last year, but haven’t been back much.
    Yours was a nice collection.

    Hope this long message hasn’t bored you…
    ————————————————————————–
    Ken Scales Delphi:KSCALES Internet:kscales [at] delphi [dot] com CIS:74646,2237

  • pucc_unknown

    90070 24-SEP 22:38 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90023)
    From: TIMKIENTZLE To: KSCALES

    >>Hope this long message hasn’t bored you…
    Not at all. I hadn’t heard of the two Usenet groups with these
    sorts of pictures. Definitely a good place to look next time I need
    this type of stuff.
    The “trek” problems with losing the front part of the ship
    (Telix??) were probably due to a failure to properly support underlining.
    As I recall, “trek” uses underlined spaces to draw that part.
    Generally, I’ve been quite disappointed at the various bugs
    I’ve found in many commercial programs claiming VT100 emulation.
    Sounds like OSTerm is now on a par with many PC and Mac commercial
    programs I’ve seen.
    If you have a Coco around, you might try these movies against
    KBCom (OS9) and V-Term (RSDOS). These particular movies were just
    part of the testing that Eddie and I did on those programs, and it’s
    kind of neat to see how these programs work in full. (The
    only weaknesses I know of are that KBCom doesn’t support blinking;
    V-Term doesn’t support blinking on graphics displays and lacks
    double-width/double-height/special chars on hardware screens.)
    I should also upload the “vttest” program I have sitting here.
    It’s a menu-driven program that exercises a lot of odd VT features.
    Also, feel free to ask me any questions you have. I spent
    a lot of time over the last eight years implementing and testing
    several VT100 emulations (V-Term was only the beginning!). Someone
    else should benefit from those years of effort…

    – Tim

  • pucc_unknown

    90073 24-SEP 22:58 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90070)
    From: REVKAK To: TIMKIENTZLE

    Since I use KBCom here on Delphi, I was wondering just exactly what is
    the procedure to get the Vt100 “movies” into KBCom to view them. Please
    enlighten me as to this new use. Any help is appreciated.

    Thanks, . . . Keith

    PS: KBCom is the commercial version.

  • pucc_unknown

    90102 26-SEP 00:31 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90070)
    From: DIGIGRADE To: TIMKIENTZLE (NR)

    I LOVE V-Term. The menus are a bit kludgy to get through but it’s I’m
    shure the only RS-DOS term program that actually multitasks! :) The file
    handling is great too IE: Ramdisk, not just a buffer, and enhanced control
    over the ram and normal RS-DOS drives. My first term program. Of course I
    soon went to OS9, and then when I went back to RS-DOS I used Ultimaterm
    because I forgot my way around V-Term and Ultimaterm had more of an OSTerm
    feel. :) V-Term is great though. Oh, yea, I liked to get colored ANSI garbage
    that V-Term filtered out also.

    Dave

    _____________________________________________________________________________
    |Dave Pellerito – | Posted using InfoXpress |
    |Digigrade Productions – Digital Services | with an MM/1 running OSK |
    |”I can handle more than one thought, more than|____________________________|
    | one task at a time, so why should I use a computer that doesn’t?” OS9/OSK |
    —————————————————————————–

  • pucc_unknown

    90074 24-SEP 23:14 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90073)
    From: TIMKIENTZLE To: REVKAK (NR)

    Unfortunately, it requires another computer or a null modem cable
    and two serial ports under OS9. Basically, you just put them somewhere
    where you can “list” them while using KBCom. Unfortunately, Delphi
    won’t allow you to “list” a binary file, and they must be uploaded
    as binary files lest they be damaged in transfer. With a null modem
    cable and two computers (or two serial ports on one OS9 system),
    you can use KBCom on one machine/serial port and dump the files into
    the other serial port so they come through KBCom’s screen.
    I’m sorry there’s not some simpler way, but there’s really not.
    – Tim Kientzle

  • pucc_unknown

    90081 25-SEP 15:25 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90074)
    From: REVKAK To: TIMKIENTZLE (NR)

    Tim,
    Thanks for the info on displaying “movies”. I will try to keep this in mind
    when (if) I get a second serial port. Thanks for the help.
    Keith Kounovsky

  • pucc_unknown

    90090 25-SEP 19:57 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90074)
    From: DBREEDING To: TIMKIENTZLE (NR)

    REVKAK asks:
    > Since I use KBCom here on Delphi, I was wondering just exactly what is
    > the procedure to get the Vt100 “movies” into KBCom to view them. Please
    > enlighten me as to this new use. Any help is appreciated.

    TIM’s response:
    > Unfortunately, it requires another computer or a null modem cable
    > and two serial ports under OS9.
    > – Tim Kientzle

    I may have a solution. Using a terminal program that supports ASCII send,
    simply connect to your modem and leaving it on-hook, echoing, send the
    file.. The modem will echo the data back to the term program and it works
    quite well. I don’t have KBCom, but using SuperComm, which has something
    of an “ANSI” mode, will get through the process fairly well. In trying
    “trek”, it seems that about 600 Baud is as fast as it can go… must be
    losing data… when the outpost blows up, any faster rate and the effects
    of the explosion don’t work right… It isn’t the BEST way, but at least
    you can see what is going on.

    I have G-Windows, and it is vt100.. I was able to just “merge” or “list”.
    They go by a little fast, as apparently the baud rate doesn’t seem to affect
    the speed from the keyboard, but they do work.

    — David Breeding –
    CompuServe : 72330,2051
    Delphi : DBREEDING

    *** Sent via CoCo-InfoXpress V1.01 ***
    ^^^^ ^^^^^^^^^^

  • pucc_unknown

    90171 1-OCT 11:32 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90090)
    From: TIMKIENTZLE To: DBREEDING

    Hmmm…. Using the modem’s echo is a clever trick! I’ll have to
    remember that one…

  • pucc_unknown

    90180 1-OCT 15:57 Applications (6809)
    RE: OSTerm/68K (Re: Msg 90102)
    From: DBREEDING To: DIGIGRADE (NR)

    > I LOVE V-Term. The menus are a bit kludgy to get through but it’s I’m

    Me, too! Before I went totally to OS9, I wouldn’t use anything else.
    Started with Auto-Term.. Handled OK, I guess, but trashed disks badly.

    I didn’t have any problem with the menus.. Maybe a keypress or 2 to get
    where you wanted, but worked great! Really seemed sensible to me.

    — David Breeding –
    CompuServe : 72330,2051
    Delphi : DBREEDING

    *** Sent via CoCo-InfoXpress V1.01 ***
    ^^^^ ^^^^^^^^^^