ADB Keyboard: Problem with Function Keys When Emulating VT240



I am having problems using VT240 terminal emulators with Macintosh SEs with
Apple SuperDrives (formerly Apple FDHD) and extended keyboards. The problem
is that I can't use some function keys (PF2, PF3, and PF4), like the six keys
above the arrow keys on the extended keyboard.

It seems to be a CPU-related problem, because I have tried all the possible
combinations between the old and the new extended keyboard, reinstalled system
software 6.0.3, and used the latest revisions of the two emulators (VersaTerm
Pro and Mac240). I have problems only when using the Macintosh SEs with
SuperDrives. Everything works fine with older CPUs.

What's going on?

We tested Mac240 on our Macintosh SE with a SuperDrive, and the function keys
are working exactly the same as on the Macintosh SE with 800K drive.

According to page 82 in Appendix A of the Mac240 manual, DEC keyboard keys
F1-F5 are not present on the ADB keyboard.These keys perform local functions
on a VT240 terminal (Hold Screen, Print Screen, Setup, DataTalk, and Break).
Equivalent operations are available in Mac240 menus. DEC keyboard F6 and up
are mapped to ADB keys F1 and up as follows:


DEC Keyboard ADB Keyboard
-------- --------
F1-F5 Not Present
F6 F1
F7 F2
F8 F3
F9 F4
F10 F5
F11 F6
F12 F7
F13 F8
F14 F9
Help F10
Do F11
F17 F12
F18 F13
F19 F14
F20 F15

Pressing the F1 key on the ADB keyboard is equivalent to pressing the F6 key
on the VT240, which happens to be Control-C, the CANCEL key. Pressing F10 and
F11 on the ADB keyboard is like pressing the Help and Do keys on the DEC
keyboard. This was verified using DEC Edit/TPU program.

The six keys above the arrow keys on the ADB keyboard also worked correctly
for us on the Macintosh SE with the SuperDrive and with the 800K drive. Keep
in mind that they do not have the same meanings as their labels. They work
like the DEC keyboard labels:

DEC keyboard ADB keyboard
------------ ------------
Find help
Insert Here home
Remove page up
Select del
Prev Screen end
Next Screen page down

One other thing to check is to make sure that the terminal is set correctly on
the host machine as VT200 series. On VAX/VMS, use the command:

$ SET TERMINAL/DEVICE=VT200



Published Date: Feb 18, 2012