03/26/94: Supercomm… by Delphi, | Category: Delphi - Telecom 6809 | 9 comments - (Comments are closed)

Supercomm…

86509 26-MAR 12:21 Telecom (6809)
Supercomm…
From: DBREEDING To: RANDYKWILSON

Randy, I think that you are the agent for supercomm, so I’ll address this
to you. I just grabbed it a week or so ago, and in working with it, I
found something that seems to be a problem in at least my setup.

My setup is a Disto SC-2 w/4in1, Disto Clock Edition 9, sacia w/the
supercomm patches (only, not the ones Paul uploaded), and VRN suite of
modules.

When I close a capture buffer (that is SHIFT-Downarrow) after the prompt
“…Close it “… after I respond “y”, something is sent to the modem
and supercomm locks up. This is with the modem in command mode.. I also
tried this with the standard Disto clock and ACIAPAK with the same results.

One other thing… with IT.XTP set with bit 6 (forced DTR) set, as supplied,
if I exited my telecom program (OSTerm also), and turned my modem off, it
would crash my system. (I know this is not a fault of supercomm, but thought
I might add it).

Anyway, I thought I’d throw this up at ya and see what you might come up with.
The above situation might not be the way things would need to be done (close
buffer with modem in cmd mode), but at any rate it does represent a
possiblity for error and should be looked into. Of course the situation
might be caused by the way my port handles RTS/CTS etc, but I would think
that this port should be supported.

BTW, here’s my current xmode:
nam=T2 mgr=SCF ddr=SACIA hpn=07 hpa=FF54 upc=00 bso=01
dlo=00 eko=01 alf=01 nul=00 pau=00 pag=18 bsp=08 del=18
eor=0D eof=1B rpr=09 dup=19 psc=17 int=03 qut=05 bse=08
ovf=07 par=0C bau=04 xon=11 xof=13 col=50 row=18 xtp=05
wnd=05 val= sty= cpx= cpy= fgc= bgc= bdc=
Well, TTYL

— David Breeding –

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

9 comments to Supercomm…

  • pucc_unknown

    86517 26-MAR 19:02 Telecom (6809)
    RE: Supercomm… (Re: Msg 86509)
    From: RANDYKWILSON To: DBREEDING

    David,
    Both problems are known. Unforch, due to the coco telcom enviroment, there
    ain’t much I can do about it.

    Turning modem off hangs the system. Yep, sure does, but only with certain
    clock modules. congrats on tracing this to bit 6. Took me forever to figure this

    one out, though I was doing it via email/forum. with the 6551, to leave DTR true

    means leaving the chip partially hot. Turning the modem off causes the lines to
    change state, and the 6551 tosses an IRQ (it shouldn’t but does. BUG!).
    Of course, SAcia is gone, the irq handler has been removed, and so clock runs in

    an endless loop looking for someone to turn this damn interupt off. Apparent
    lockup. The answer is… DON’T SET BIT 6!!! :>

    The lockup with ascii capture close is a lot tougher. SuperComm sends out
    an X-Off (if enabled) to stop the sender before going to disk. It has to do
    this in order to not loose massive amounts of data on floppy based systems.
    But when you’re in command mode, the modem just echos this x-off char right
    back to SAcia. When SuperComm is done writing, it sends an X-On. But in
    this case, SAcia won’t send the char out, since it’s x-off’d. Deadlock.
    Nasty.

    Normally I recommend running with only partial xon-off control. Disable
    the Tx side. i think the setting is par=04, but need to check it. This
    makes SAcia ignore the bounced Xoff. But if you’re using a high speed modem
    with soft flow control, this will screw things up.
    I just realized how to fix it. Let me screw together a new SAcia, and I’ll
    mail it to you for beta testing.

    Randy

  • pucc_unknown

    86524 26-MAR 23:41 Telecom (6809)
    RE: Supercomm… (Re: Msg 86517)
    From: DBREEDING To: RANDYKWILSON

    Randy, thanks for taking the time to describe the turn-of-modem problem
    and the thing about closing files. I would assume that the problem with
    file-close would not persist with modem in data mode – I didn’t really
    have the XOff figured out, but in the back of my mind, I had a suspicion.
    Hadn’t really given S-Com a thorough wring-out. Is it actually superior
    to OSTerm? OSTerm has a few shortcomings itself – no ascii upload being
    my main gripe.

    RE: the modem turn-off thing: I experienced a similar thing when I patched
    my Clock module with the Bruce Isted Gime toggle with WizPro. Of course
    it provided its own Driver and in this light, I would suspect that its
    problem was possibly a result of the same thing. I never did use the Wiz
    package, although it did have some appealing screens.

    I’ll give S-Com a further wringout with my local BBS – I feel a little
    giddy when trying something like this till I get used to it. Feel like
    I’m walking on eggs . BTW.. I think I mentioned that I’m using the
    version of Sacia that came with the SuperComm pkg. Didn’t install the
    patches that Paul uploaded.

    Thanks again…

    — David Breeding –

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

  • pucc_unknown

    87085 1-MAY 13:15 Telecom (6809)
    RE: Supercomm… (Re: Msg 86524)
    From: 10BAUD To: DBREEDING (NR)

    Not a big point, but every time I see the remark about osterm not
    having ASCII upload, I like to point out that some kind soul created
    “slowio” which I’m sure must be in the telcom data base here.
    You just use the clear key to toggle to another window and type+
    slowio /t2
    where “filename” is the ascii file you want to upload. Once you get the
    hang of it, it’s really very easy. If you toggle back to the osterm
    window while the file is still uploading, you can see the characters
    go by.
    I mention it because I think that without slowio, I’d be looking for a
    replacement for osterm which I love in every other respect.

  • pucc_unknown

    87103 2-MAY 00:38 Telecom (6809)
    RE: Supercomm… (Re: Msg 87085)
    From: KSCALES To: 10BAUD (NR)

    > Not a big point, but every time I see the remark about osterm not
    > having ASCII upload, I like to point out that some kind soul created
    > “slowio” which I’m sure must be in the telcom data base here.
    < <<<<< edited for brevity >>>>>>
    > I mention it because I think that without slowio, I’d be looking for a
    > replacement for osterm which I love in every other respect.

    Yes, the ASCII upload in the Level 2 version of OSTerm does not work:
    from looking at the source, it appears that Vaughn probably added it
    to the menu while he was working on it, but released the package before
    finishing the code (and forgot to remove it from the menu). The ASCII
    upload isn’t broken because of a problem with the code; it simply
    doesn’t work because it was never finished! This also applies to the
    MM/1 release of TasCOM.

    Northern Xposure has licenced the code for development of an enhanced
    version of OSTerm (OSK only). The “prompted ASCII uploading” is fully
    functional in the current development version of OSTerm 68K.

    Sorry, there are no plans for releasing an enhanced 6809 version, BTW.

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

  • pucc_unknown

    87214 8-MAY 01:52 Telecom (6809)
    RE: Supercomm… (Re: Msg 87085)
    From: DBREEDING To: 10BAUD (NR)

    Hey, thanks for your reference to “slowio”. I’ve heard of it, but never did
    get it to use. OSTerm is a pretty nice app, could use a touch-up or two.
    One thing I could never get it to do was send CTRL-chrs correctly. Tried
    to get it to send CTRL-C for CIS logon and never did work. Learn produced
    a string “\3c” (I think) but didn’t work. Aside from this and maybe another
    or two, it is really neat.

    If you refer to my rep to KSCALE’s rep to your msg, I have a System 5 on order
    so may not be pursuing my coco stuff as avidly, bad as I hate to leave it.
    I hope to do some more with my coco, but I figure that OSK will occupy most
    of my time.

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

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

  • pucc_unknown

    87465 20-MAY 00:28 Telecom (6809)
    RE: Supercomm… (Re: Msg 87085)
    From: TONYPODRAZA To: 10BAUD (NR)

    You could also use the shell call from Osterm and do the same thing
    by redirecting the output to t2 from that shell. When you’re done listing,
    exit from the shell and violin! you’re back in Osterm…no drop in carrier
    nor nuttin.

  • pucc_unknown

    87213 8-MAY 01:51 Telecom (6809)
    RE: Supercomm… (Re: Msg 87103)
    From: DBREEDING To: KSCALES

    > Yes, the ASCII upload in the Level 2 version of OSTerm does not work:

    > finishing the code (and forgot to remove it from the menu). The ASCII
    > upload isn’t broken because of a problem with the code; it simply
    > doesn’t work because it was never finished! This also applies to the

    I kinda figured that this was the case.

    > MM/1 release of TasCOM.

    > Northern Xposure has licenced the code for development of an enhanced
    > version of OSTerm (OSK only). The “prompted ASCII uploading” is fully
    > functional in the current development version of OSTerm 68K.
    >
    > Sorry, there are no plans for releasing an enhanced 6809 version, BTW.

    Well, I may have to give it a try. I have just sent in my order for a
    System 5 and of course will be on the lookout for a good telecom program.
    ‘Course my Delphi/CIS msg stuff will be handled by “IX”.

    BTW… is there any t’com support for something like XModem-G or some
    non-error-correcting protocol? I want to use V.42bis or ’32, but as
    everyone has written, I found out that all the error-correcting protocols
    are actually slower with this turned on. I wanna go hi-tech with this

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

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

  • pucc_unknown

    87644 29-MAY 23:48 Telecom (6809)
    RE: Supercomm… (Re: Msg 87214)
    From: 10BAUD To: DBREEDING

    Oh yeah–the ^C problem. Some one here on Delphi gave me the
    solution to that one,too. I run osterm from the following
    procedure file:

    t
    chd /d0/USR/DLD/telcom/WORK
    display c
    tmode .1 abort=0 quit=0
    load osterm&
    osterm tmode .1 abort=3 quit=5

    The “abort=0″ in the tmode command prevents the operating system
    from intercepting the control-c character allowing osterm send it
    to delphi.

    Another solution to that problem is to get to an os9 prompt (by using
    the shell command or the clear key to get to another window) and
    typeing:

    display 03 >/t2

    You’re right that it could use a few touch ups, but by now, it feels
    to me like the software equivalent of an old comfortable sweater.
    And I just make allowances :>

  • pucc_unknown

    87658 31-MAY 00:07 Telecom (6809)
    RE: Supercomm… (Re: Msg 87644)
    From: DBREEDING To: 10BAUD (NR)

    > Oh yeah–the ^C problem. Some one here on Delphi gave me the
    > solution to that one,too. I run osterm from the following
    > procedure file:

    > …

    > The “abort=0″ in the tmode command prevents the operating system
    > from intercepting the control-c character allowing osterm send it
    > to delphi.

    I never had any problem with it being intercepted, I just sent it from
    the keyboard and then let the autodialer do the rest. I just could not
    get the control sequence to work from a macro.

    > You’re right that it could use a few touch ups, but by now, it feels
    > to me like the software equivalent of an old comfortable sweater.
    > And I just make allowances :>

    I like it too. And as you say, it is pretty comfortable.

    Also I guess any software you name has something somewhere that could be
    fixed. I know “we” can always find something that could be done better .

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

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