Dear All:
Could you advise me on where I can get the above to
use for E11?
Thank you.
Artem Kovalenko.
artem_55555(a)yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html
Witchy <witchy(a)binarydinosaurs.co.uk> wrote:
> It sends a <CR>. Dot sends a dot :)
OK, so these are out-of-compose keys like arrows and function keys, and like the
whole keypad on VT2xx/3xx.
> Verified against asciitable.com.....
Umm, you don't remember the entire ASCII table by heart? Tsk tsk. This is the
kind of thing that everyone should know as most basic, so if anyone wakes you up
in the middle of the night and asks you to recite the ASCII table, you ought to
be able to just recite all 128 characters immediately. (Or at least the 96
characters from space through delete plus the most basic controls, I'll grant
that most of the C0 control characters are not used anywhere and have no real
meaning beyond the paper spec.)
> I get a beep and the 2nd keypress, as I expected.
Wait a moment, are you saying that if you enter a code between 80 and 9F through
hex compose while the terminal is set for VT400 mode, 7-bit controls in Setup,
it beeps in error and sends nothing? This is not what the manual says, it says
that it sends the two-byte 7-bit escape sequence equivalent to the C1 control
character entered. So the actual behaviour differs from documentation here,
right?
MS
Witchy <witchy(a)binarydinosaurs.co.uk> wrote:
> Keypad Enter just ends the compose sequence,
So after canceling the compose, it does NOT transmit the normal code(s) for
keypad Enter (CR, CR LF, or SS3 M)? Are you sure? Maybe you were testing in a
mode where it sent CR which was invisible? Could you try again with the
terminal set to local mode, display controls? According to the docs (and actual
behaviour on VT320) whenever you press a key outside "normal" in a compose
sequence, it cancels the compose and then the key does its normal action. The
only exception is Delete, which is the key you should press to get out of
compose mode you entered unintentionally.
> Interesting. I've always had my terminals set to 7 bit space parity -
> software needs from many moons ago
I used to use the VT100 mode (and still do on console/test terminals) which has
the same effect of forcing a 7-bit only Universe. In spring of last year I
migrated to using an 8-bit environment on the terminal on my desk in the command
room (one I'm typing on right now) to support Russian. Of course DEC built its
classic hardware during the Cold War and didn't support Russian, but I've hacked
it in. I use a downline-loaded 96-character KOI8-E set for my GR set on output,
and since I don't have the guts to tear the VT apart, get to its firmware ROM,
and Russify the keyboard input firmware, I have instead implemented a hack in
the Berkeley UNIX tty driver to enter Russian in KOI-8 from the VT320 keyboard.
> - but setting it to 8N shows some
> interesting things going on with 'display controls' enabled:
Yup, it's a whole new exciting 8-bit world out there. I was quite excited when
I took a VT3xx out of VT100 mode and put it in its native mode for the first
time.
> Compose key plus keypad:
>
> 00 = <NUL>
This is the hexadecimal compose feature. The keys of the numeric keypad become
hex digits in compose mode. 0-9 are themselves, PF1-PF4 are A-D, '-' is E, and
',' is F. You can enter any 8-bit character from 00 to FF as two hex digits.
> 11 = nothing
Actually it's XON (^Q), though of course it's normally unseen.
> 22 = "
> 33 = 3
> 44 = D
> 55 = U
> 66 = f
> 77 = w
These are just ASCII.
> 88 = HTS (horizontal tab stop?)
> 99 = '99' stepped like a fraction.
C1 high control characters. According to the manual the terminal only allows
you to enter them if it's set for 8-bit controls in Setup. If it's set for
7-bit controls, the manual says that C1 chars entered through hex compose will
be turned into equivalent 7-bit escape sequences. Can you test (using local
mode, display controls) whether this is actually true?
> Mixing keypad and keyboard keys results in a beep and end of sequence.
OK, the reasonable behaviour, just as I was going to implement in my code.
> With
> parity set to 7S I get slightly different results, but then a lot of compose
> sequences don't work with 7S.
Well, yeah, Compose is basically for entering 8-bit characters. The standard
ASCII main keypad supports all 128 possible 7-bit ASCII characters, so you
should never need Compose or anything else for 7-bit ASCII, unless of course you
are one of those strange people who configure their LK201s for some non-ASCII
national mode.
MS
Through the generous donations of several individuals (especially Gaby
Chaudry for allowing me to mirror her site and Barry Smith for a copy of his
archives) I now have available over 600MB of CP/M software and data, as well
as machine-specific information, from a variety of sources.
I'm making this available now, although I'm not finished organizing it
(there's a lot of duplication, gaps, etc.). Also a lot of the archives are
in old (current-at-the-time) formats, and I will be indexing them for easier
traversal. This has already been done for most of the ZIP archives,
particularly those from Barry's collection.
Please feel free to browse/download. I've hobbled the bandwidth a bit at
the moment just to get a feel for how much this may affect my network, so
please forgive the temporary configuration of the server.
ftp://ftp.staunch89er.com/pub/
Suggestions, pointers, info about broken files, donations of missing files,
etc., are all appreciated!
--Patrick
Does anyone have an electronic copy of the operator's manual for an HP 1630
logic analyzer (specifically 1630G, but I think any of the series will be
pretty much the same).
TIA! --Patrick
Well today I got a pallet with 2 strange items on it:
One was a AS/400 Advanced Type 9402 with all it's cables and a internal QIC
2GB tape drive.
The second item was a Hitachi Color TV Camera with a zoom lens by Fujinon
mounted on it. This a large unit dated as mfg'd in Oct 1979. There were
several other items on the pallet but nothing of interest but for $5 I can't
complain.
I'm writing a software module that turns a DEC LK201 keyboard into an IFCTF
keyboard (one that generates ASCII/ISO codes and sequences) and among other
features supported on LK201 in various DEC products I want to implement hex
compose on the numeric keypad like on VT420. The problem is, some fine details
of how it should work are unclear and I don't have a VT420 to experiment on,
only VT320 and VT340 which don't have hex compose. I'm wondering if someone on
this list has a VT420 and could test something for me.
First, what happens if you press keypad Enter or keypad '.' in a compose
sequence? I can think of 3 reasonable ways the firmware can handle this:
* Do what it does for Tab, Return, arrow and functions keys in a compose
sequence, i.e., cancel the compose sequence and let the pressed key do its
normal non-compose action.
* Ignore the key (suppress the keyclick) and remain in the compose sequence in
the same state.
* Store the invalid key in the compose sequence accumulator and proceed to the
next character of the sequence. Then at the end of the compose sequence
complain with a warning bell about the invalid sequence.
Can someone with a VT420 please try this and see which of the above (or
something else altogether) does the firmware do?
Also what happens if you mix a main keypad key and a numeric keypad key in a
compose sequence?
MS
P.S. Reverse-engineering state machines is fun, isn't it?
ps I am in Eastern Pa.
nIcK
_________________________________________________________________
Stay informed on Election 2004 and the race to Super Tuesday.
http://special.msn.com/msn/election2004.armx
