HP3000-L Archives

October 2006, Week 5

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: On-topic, but wildly left-field question
From:
Charles Finley <[log in to unmask]>
Reply To:
Charles Finley <[log in to unmask]>
Date:
Tue, 31 Oct 2006 13:42:06 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines) 
Wow, this goes way back!  I really don't remember, but here goes.  I think
this control Q is what it does when it thinks you are using an HP termtype.
I'm not sure all term types used the same protocol.  Therefore, if you
experiment with termtypes settings for a non-hp terminal.  This goes back
over 20 years but maybe if you tell it you are using termtype 18 or the
behavior could change.

Charles Finley
(619) 795-0720

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Jeff Kell
Sent: Tuesday, October 31, 2006 1:35 PM
To: [log in to unmask]
Subject: On-topic, but wildly left-field question


I'm trying to get read of the MPE "read trigger" DC1/XON character that gets
sent on a read.

The problem is a very "generic" telnet client hitting the 3000 - I've
managed to patch around control codes (HP to ansi) and almost everything is
working -- except for the darned "^Q" this client keeps displaying.  I know
I can't patch around the MPE prompt, but surely this can be disabled by an
application (?).

The only functional API to this I know of is an FDEVICECONTROL 192, parm1 =
30/32, parm2 = 0.

The reason I mention "30/32" is because at different places in the intrinsic
manual (yes, I still have a dead tree in a 3-ring binder) it documents
"30,32" as the "read trigger and block mode read trigger" parameters where
it would appear that 30 is the read trigger.  But in the table that follows,
32 is given as the read trigger.

I've tried both, to no avail.  FDEVICECONTROL gives me an FSERR 20 (invalid
operation), and of course the ^Q prevails.

>
> +-F-I-L-E---I-N-F-O-R-M-A-T-I-O-N---D-I-S-P-L-A-Y+
> !  FILE NAME IS TIOIN                            !
> !  FOPTIONS: NEW,ASCII,$STDINX,U,NOCCTL,FEQ      !
> !            NOLABEL                             !
> !  AOPTIONS: INPUT,NOMR,NOLOCK,DEF,NOBUF,MULTI   !
> !            WAIT,NOCOPY                         !
> !  DEVICE TYPE: 16     DEVICE SUBTYPE: 0         !
> !  LDEV: 14       DRT: 0         UNIT: 0         !
> !  RECORD SIZE: 80     BLOCK SIZE: 80    (BYTES) !
> !  EXTENT SIZE: 0      MAX EXTENTS: 0            !
> !  RECPTR: 0           RECLIMIT: 0               !
> !  LOGCOUNT: 0            PHYSCOUNT: 0           !
> !  EOF AT: 0           LABEL ADDR: %00000000000  !
> !  FILE CODE: 0        ULABELS: 0                !
> !  FILE OWNER:                                   !
> !  ERROR NUMBER: 20    RESIDUE: 0                !
> !  BLOCK NUMBER: 0            NUMREC: 1          !
> +------------------------------------------------+


Surely someone has successfully done this before?  What am I missing?

Jeff

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

__________ NOD32 1.1846 (20061031) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2