[comp.os.vms] PC <--> DECtalk <--> DECserver <--> VAX problem

CADS_COLE@GALLUA.BITNET.UUCP (10/03/87)

  Reposting an earlier message that seems to have disappeared into a black hole
of the electronic galaxy:

  Greetings.  I have a small but annoying problem (which has nothing to do with
a lack of Preparation H, thank you).
  I have an IBM (Yeuch!) AT connected to our VAX cluster via a DECserver.
Sitting on the line between the DECserver and the PC is a DECtalk.  For some
reason, a few seconds of inactivity causes a Control-K (Vertical Tab) to be
sent to my "terminal".  It disappears when DECtalk is removed from the line.
The problem shows up with all of my communications programs except ProComm.
(I've seen it with Kermit, Qmodem, Vterm and PC-VT.)  I'd stick with ProComm,
but the keypad emulation is better in Kermit (if you build the mapping
yourself, which isn't difficult).  Output looks like:

   $
     MAIL
   MAIL>
         DIR

etc. Suggestions as to the cause and/or cure???  Thanx Muchly.

--------------------------------------------------------------------------------
Kevin Cole      <Flatline>              BITNET: KJCOLE@GALLUA.BITNET
Center for Assessment and                               or
Demographic Studies  (CADS)                     CADS_COLE@GALLUA.BITNET
Gallaudet Research Institute  (GRI)     UUCP: ...!psuvax!gallua.bitnet!kjcole
Gallaudet University                    CompuServe: 76167,1406
Washington, D.C.  20002
(202) 651-5575

             "Hey Rocky!  Watch me pull a rabbit out of my hat!"

minow@decvax.UUCP (Martin Minow) (10/04/87)

In article <8710030008.AA25522@ucbvax.Berkeley.EDU> CADS_COLE@GALLUA.BITNET
(Kevin Cole; Gallaudet U.; Washington; DC) describes a problem where
his DECtalk sends <CTRL/K> to his terminal after a few seconds of inactivity.
(The DECtalk is "spliced" between his terminal and the host system.)

My suspicion is that the DECtalk is being used to speak data sent from
the host, and that some form of logging is turned on so the data is
also displayed on his terminal.  DECtalk generates a <CTRL/K> (vertical tab)
internally five seconds after the host stops sending text.  This internally
clears out all pending speech buffers.  You would need this if your system
sent, say,
	Username:
(without a <return>.)  DECtalk is stuck waiting for the rest of the sentence
and, without some form of timeout, it would never speak the partial text.
As we noted in the manual, <VT> clears out all buffers and speaks all
pending text.  I think that using LOG RAWHOST will not log the <VT>
as it is generated internally, rather than being sent from the host.
(I'm not certain, however.)

We added logging to simplify application program debugging so that
the developer could see what DECtalk was receiving.  Since the <VT>
terminates escape sequences and exits phonemic text mode, we felt
it was important to log this so the application developer could track
the system progress.

Note that you can completely control logging by sending appropriate
escape sequences from the host.  Look at the dt_splice() routine
in the Programmer's Manual (page 175 in the -003 revision).

Martin Minow (ex-DECtalk developer)
decvax!minow

The above does not represent the position of Digital Equipment Corporation.

rrk@byuvax.bitnet (10/05/87)

I've had exactly the same problem.  I don't know if it is fixed with the
newer DTC03's.  It seems to be related to the DECtalk timeout period after
which the DECtalk speaks all unspoken text even if no "." or "?" or other
terminator was received to indicate how the pitch of the spoken words sould
rise and fall.  I realize that it occurs even if host speak is turned off,
but if host speak is turned on it seems to happen simultaneously with the
flushing of the speak buffer.  It even happens if it is a DEC terminal
connected, I think.  Your emulator that doesn't do it must eat VT's.

minow@decvax.UUCP (Martin Minow) (10/07/87)

Two collegues have discovered to their dismay that DECtalk logs
a CTRL/K <VT> to the local terminal and wondered how to stop it.
As I stated in a previous note, it is logged 5 seconds after the host
stops transmitting.  In a DECtalk (DTC01) V2.0 unit, you can prevent
this by entering setup mode and specifying SET LOCAL FILTER ON.  This
supresses logging of DECtalk-specific escape sequences to the local terminal.
This is described on page 26 of the -003 revision of the Owner's manual.
You can set this parameter from the host by transmitting the sequence:
    <ESC> P 0 ; 8 2 ; 3 2 z <ESC> \
This is described on page 63 of the -003 revision of the Programmer's manual.

DECtalk 3 (DTC03) does not support a local terminal.

My apologies for not clarifying this in my earlier posting.

Martin Minow
decvax!minow

The above does not represent the position of Digital Equipment Corporation.