==================================================================== Release Notes IntelliPort(tm) II Driver Version 1.3.2 for UNIX 3.2 and XENIX October 15, 1993 P/N 0-20110-3 ==================================================================== ------------ Introduction ------------ This Release Note provides additional information for installing and using the IntelliPort II drivers on UNIX and XENIX systems. It supplements information found in the IntelliPort II UNIX Software Reference Guide. If you are installing the IntelliPort II UNIX drivers for the first time, read the section "Product Installation/Removal" in this Release Note, and read the IntelliPort II UNIX Software Reference Guide, before you begin the installation. After installing the drivers, read the sections "Known Limitations" and "Additional Notes" in this Release Note. If you are upgrading an existing IntelliPort II installation, read this entire Release note and the IntelliPort II UNIX Software Ref- erence Guide before you begin the installation. The manual has been reorganized extensively and contains much new information. We recommend that you install the IntelliPort II software before the IntelliPort II hardware. +--------------------------------------------------------------+ | Important! To avoid damage to hardware, always turn off the | | power to the system before you plug or unplug IntelliPort II | | cables or components. | +--------------------------------------------------------------+ Computone and IntelliPort are trademarks of Computone Corporation. All other company and product names are trademarks or registered trademarks of their respective companies. ---------------------------- Product Installation/Removal ---------------------------- While installing or removing the IntelliPort II drivers, keep the following in mind: - Under AT&T/Interactive 3.2.2, the Editing Package as well as the kernal configuration kit must be installed. - Under AT&T/Interactive 3.2.3, the Computone IntelliPort II Driver diskette must remain in the floppy drive during the entire installation procedure. - During installation, you will encounter a series of menu screens. While these screens are displayed, the F4 key returns you to the Main Menu instead of returning to the previous menu, as noted on the screen. - You should select the "ALL" option during product installa- tion and removal. This ensures that the file /etc/default/ fip.d/FIP_NOTES is copied onto the system. This file identi- fies all currently supported Computone IntelliFeatures. ------------------------- Additions and Corrections ------------------------- Version 1.3.2 Version 1.3.2 of the IntelliPort II UNIX driver adds new features and corrects several problems, as follows: General - Driver software version 1.3.2 supports the new ASIC- based controllers, as well as the new Slimline enclosures and the RJ-45 Tower enclosure. - Computone now provides host-based diagnostics, through the fip_report command. The fip_report command is de- scribed at the end of this Release Note. fipInit - fipInit now performs syntax checks and confirms success- ful operation during initialization. IntelliFeatures - Fixed the problem with SCO UNIX and SCO XENIX systems where sysadmsh would be unable to assign a printer to an IntelliPrint device (/dev/xlpnn) due to the wrong permis- sion types being set. SCO XENIX - During system initialization, the drivers now display the IRQ in SCO's octal format (for example, IRQ 10 decimal prints as 32, IRQ 11 prints as 33, IRQ 15 prints as 37, etc.). Version 1.3.1 Version 1.3.1 of the IntelliPort II UNIX driver adds new features and corrects several problems, as follows: System-Specific Corrections - The problem with installing the IntelliPort II drivers under AT&T UNIX has been corrected. This problem occur- red while building the kernel; the installation program would display the error message "Can't find include file sys/types.h" and would be unable to build the kernel. - For SCO UNIX, the driver uses printcfg to display IRQ numbers in the same format as other drivers. Installation - The installation program now uses the UNIX sdevice file to build a list of available choices for I/O addresses for IntelliPort II ISA and Micro Channel controllers. This prevents I/O address conflicts that could occur during kernel linking, requiring re-installation. - When installing EISA controllers, the installation pro- gram now prompts for a slot number instead of an I/O address. - For SCO UNIX systems, the installation program provides more helpful information about what to do if no IRQs are available. - The installation program no longer asks for the number of ports per box when installing a 16-port standard IntelliPort II. - The installation program no longer removes comments after the getty token in the file /etc/inittab. Comments are not displayed in the mkdev fip menu, but are preserved in the file. mkdev fip - The error message "unknown terminal type: ansi_cton" no longer occurs when installing or running in single-user mode. fipInit - These programs now confirm that the IntelliPort II con- troller is successfully initialized in fip_reinit when switching to multiuser mode and when exiting from mkdev fip. Any error messages are displayed on the screen and written to the log file (/tmp/fipInit.log). - The log file (/tmp/fipInit.log) is now cleared when the program starts up. Previous versions would leave the contents of the log file intact and display the previous error messages as well as any current error messages. Operation - During system boot, the IntelliPort II driver initializes all controllers at once and waits long enough for all of the controllers to come up. This corrects a problem that occurred in some very fast host systems (IBM model 77 and some 486/66 MHz EISA systems) where the driver would report a "board not found" error. - The driver now enforces a 250 ms pause after dropping DTR (which occurs when closing the port, setting baud=0, or with a failed open). This ensures that modems have enough time to detect a hang-up if the line tries to re- open immediately. IntelliFeatures - The maximum length of IntelliView screen switch output sequences has been increased from 7 to 15 bytes. - The maximum length of IntelliPrint "printon" and "printoff" output sequences has been increased from 7 to 15 bytes. - IntelliView no longer allows a user to switch to an Alternate screen that is not open. Earlier versions of the driver could cause a port to hang on an Alternate screen. This would happen if a user logged out of an Alternate screen (which switches the terminal to the Main screen), then switched the terminal back to the Alternate screen and entered data before the getty process could respawn and reopen the screen. ---------------------------- Default IntelliView Profiles ---------------------------- This section lists the IntelliView profiles included in the intellicap file and the hot-key sequences recognized by each pro- file. The profile names follow the convention described within the intellicap file itself. Profile Terminal Next Screen Screen Selection Name Type Sequence Sequences wy60.2t Wyse 60 [F12] none wy60.2pt Wyse 60 [F12] [CTRL][F1], [CTRL][F2] wy60.2pt.xon wy60.2pt.cts wy60.3t Wyse 60 [F12] [CTRL][F1] - [CTRL][F3] wy60.3pt Wyse 60 [F12] [CTRL][F1] - [CTRL][F3] wy60.3pt.xon wy60.3pt.cts wy60_50.7p Wyse 60 [F12] [CTRL][F1] - [CTRL][F7] wy60_50.7p.xon wy60_50.7p.cts a230.2pt Ampex 230 [SHIFT][F1] (none) a232.2pt Televideo 925 tvi925.2pt microterm.2p Microterm 6600 (none) ^JA, ^JB tr170.3pt Relisys TR170 [F12] [CTRL][F1] - [CTRL][F3] tv955.2p Televideo 955 (none) [SHIFT][F10], [SHIFT][F11] tv955.2pt tv955.2p.xon tv955.2pt.xon tv955.2p.cts tv955.2pt.cts dumb.8t Dumb terminal ^A0 ^A1 - ^A8 ------------- Manual Errata ------------- On pages 3-9 and 3-13 of the IntelliPort II Hardware Reference, the first cable diagram (on both pages) has a wiring error. The diagram is for connecting modems to the IntelliPort II. Pins 4 and 5 on the modem connector should be the reverse of what is shown in the diagram. ----------------- Known Limitations ----------------- The following are known limitations for using the IntelliPort II UNIX driver: - SCO UNIX and XENIX systems using the "per user" licensing structure count each IntelliView login as a separate user. This happens because SCO counts the number of getty processes spawned without considering the possibility that one physical port may support several logins. Contact SCO if this causes problems for you. - Systems with motherboards that use the HiNT Caesar chip set must use ISA-4, ISA-8, or ISA-CEX controllers since these motherboards do not support EISA-standard level-triggered interrupts. This is a limitation of the HiNT chip set; motherboards using this chip set are not fully EISA compatible. A motherboard known to use this chip set is the "G486HVL HiNT Super ISA and VESA Local Bus 486 Mainboard." Computone has tested this motherboard with IntelliPort II controllers and finds that ISA controllers can be successfully installed, but EISA controllers do not work. - Under Interactive UNIX versions 3.2.4.0 and 3.2.3.1, running mkdev fip may place double entries in the /etc/inittab files for IntelliPort II devices. This may be a problem with Inter- active, since this behavior was not seen in version 3.2.3.0. - Under XENIX version 2.3.4, some processes may not unlock ports using hardware flow control. - If you are running IntelliView and using tab3 expansions, switching screens may cause a problem with the expansion. - When under a heavy load, high speed input (such as 115,200 baud) may occasionally lose characters regardless of flow control settings. - Transparent print data may be corrupted when logging off a terminal with a transparent print job active. - Running fip_reinit or mkdev fip while flow control is con- tinuously active on one or more ports may result in the pro- gram terminating with an error. This only happens if you run fip_reinit or mkdev fip after system initialization; the usual cause is that a printer is off-line and data is waiting to be sent to the printer. - IntelliView and PC Term applications require 8-bit mode. However, AT&T/Interactive UNIX do not support this. There- fore we provide new gettydefs entries prefixed with cton_8bit_ that can be used for this purpose. These entries do not circulate. - Hot-key sequences (sent from the terminal to the host) are limited to seven (7) characters in length. Screen switch sequences (sent from the host to the terminal) are limited to 15 characters in length. - If IntelliView screen switch sequences or IntelliPrint printer control sequences contain linefeed (0x0a) characters, and the port is in cooked mode, these are converted to CR/LF sequences. This does not happen when the port is in raw mode. - IntelliSet "tab" and "onlcr" settings have no effect for Alternate screens. - If your application turns off the cursor, some terminals do not restore the cursor when changing screens. This is a limitation of the terminal. - Take care when using the following form of the fipInit command, where the environment variable TERM specifies an IntelliView profile: fipInit icap_file < `tty` See the section on fipInit, under "Additional Notes" below, for more information. ---------------- Additional Notes ---------------- System Initialization (AT&T UNIX) At system initialization, AT&T UNIX systems show assigned interrupt numbers in octal. For example, if you configured the IntelliPort II controllers to use IRQ 10, the system prints "irq=12" at startup. mkdev fip On UNIX systems, if additional (comment) information is avail- able in the init.d/fip entries, this information is duplicated on all IntelliView Alternate screen entries in /etc/inittab. This happens only if you manually edit comments into the init.d/fip entries. Directly-Connected Printers Printers connected directly to an IntelliPort II port can lose data at the end of the file. Use the IntelliSet "noflush" parameter on direct printer ports to avoid this problem. Scan Code Applications Many terminals using PC scan codes issue their break codes as "make+80H". But some varieties of UNIX use gettydef entries that default to 7-bit operation. (If the application echoes double characters from the keyboard (once on press, once on release), make sure the terminal and the getty are set up for 8-bit characters. Flow Control Issues Most gettydefs entries default to ixany. That means that if you press Ctrl-S to stop output, pressing any other key restarts output. If the application is sending data so fast that the terminal can not keep up, the terminal sends an XOFF to prevent its buffer from overflowing. If the operator is typing ahead in the application, the incoming keys may re-enable output inappropriately, causing loss of data. Here, it is best to specify -ixany in the gettydefs defaults. Remind users that if they press Ctrl-S, they must press Ctrl-Q to re-enable the output. Unfortunately, some applications explicitly set ixany at startup. You can use the IntelliSet option outflow=xon! to force the port to ignore changes to the flow control settings. The IntelliPort II UNIX drivers provide for two types of hardware flow control. The incoming data-set signals CTS and DSR can provide output flow control, and the outgoing dataset signals RTS and DTR can provide for input flow control. This type of flow control can be specified by using IntelliSet entries; for example, inflow=dtr! or outflow=cts!. For SCO products, the stty command supports the keywords RTSFLOW and CTSFLOW to enable this flow control. The serial hardware within the IntelliPort II can directly handle the DTR and CTS signals. However, the driver software must handle the DSR and RTS signals. This makes DTR (for input flow control) and CTS (for output flow control) more efficient for high-speed applications. When using terminals, it is not customary to use any form of input flow control. (Notice that the normal stty settings for terminal sessions usually specify ixon, possibly ixany, but never ixoff.) This is because input is never expected at a high enough rate to overrun the host. When connecting a terminal using hardware flow control, you should specify CTSFLOW (outflow=cts!) but not RTSFLOW (inflow=rts!, inflow=busyready!). In some cases, you may want to connect a PC running a terminal emulator package and other software, instead of a terminal. If you are using the terminal emulator to transfer files to the host, the host application which supports this may need to invoke input flow control while the transfer is taking place. fipInit There are some limitations to keep in mind when using the fipInit command to change the IntelliFeatures file used by the current port, as follows: cd /etc/default/fip.d /etc/fipInit intellicap icap.site < `tty` cd $HOME The contents of the environment variable TERM, used by default when the -p option is not specified, is used to specify an IntelliView profile in this command. You could use this form of the fipInit command in a .login or .profile file, after a tset command, to assign an Intelli- Features profile to the port. This is useful mainly for dialup ports that may be used with various terminals. If you use this command, make sure any IntelliFeatures profiles that could be assigned with this command support the same number of screens or the results may be unpredictable. NOTE: The TERM variable must match a profile name exactly. The easiest way to set this up is to edit the icap.site file (located in the /etc/default/fip.d directory) and let the new profile names inherit the desired profiles without any changes. The following would allow the wy60.2pt profile to be used if TERM=wyse60 and the tvi925.2pt profile to be used if TERM=tvi925. ###start of EXAMPLE icap.site entries ###PLEASE put all changes in icap.site and not in the intellicap ###file. The icap.site file will be left unmodified after a ###driver upgrade/reinstall. The intellicap file will be updated ###with the version on the driver disk. $wyse60 := $wy60.2pt $tvi925 := $tvi925.2pt ### ###end of EXAMPLE icap.site entries Keep the following limitations in mind: 1. The number of IntelliView screens (defined in intellicap) should match for all profiles used on a port. In general, you can use intellicap profiles with matching extensions. The extension ".2pt" in the above examples indicate 2 screens, transparent Print, and a Toggle key. 2. If IntelliView is used, one of the above profiles needs to be the default profile and ALL screens should be enabled. Use the "mkdev fip" command to do this. UUCP/CU Modem Control and TTY Selection Incoming lines with a modem attached should use the uppercase port or the port with modem control (/dev/ttyS00 instead of /dev/ttys00). For direct connections, the lowercase port should be used on both sides of the connection. Use the -r option with uugetty. If the originating side of the communi- cation is connected to a modem and the port is also enabled for login with uugetty, use the port with modem control (uppercase). If the port is used strictly for dial out, you can use the lowercase port. Make sure all configuration files are correct (/usr/lib/uucp/Devices, etc.) and that the modems are configured correctly. Device Characteristics The IntelliPort II driver provides a modem (uppercase) device, and a non-modem (lowercase) device. By default, the modem device reports the true state of carrier detect, while the non-modem device does not. The processes on the modem port block waiting for carrier detect while the processes using the non-modem port do not block. (For further information, see the IntelliPort II UNIX Software Reference Guide in the section "Modem vs Non-Modem Devices".) IntelliFeatures and uucp/cu Do not use IntelliView and IntelliPrint on ports that are to be used for uucp. Binary files transferred using uucp could conflict with IntelliPrint and IntelliView hot keys. It is best to use a "dumb" profile for uucp ports. You can use IntelliSet to set RTS/CTS flow control or to lock in a data rate only if both ends of the connection are set the same. Select an /etc/gettydefs entry that has IXON and IXOFF enabled for dial-in/dial-out ports. If you must cu out a non-modem port with Alternate screens configured and logins are enabled on the corresponding modem port, disable hot-key scanning with the command /etc/fip_hot -d. Direct connect and cu For direct serial connections between machines, use non-modem (lowercase) ports. For UNIX, use uugetty -r to prevent race conditions from occurring. uugetty/getty For UNIX systems, any manual entry made in the /etc/inittab file for IntelliPort II ports must also be placed in the /etc/conf/init.d/fip file. If this is not done, the entries are replaced by whatever is in the /etc/conf/init.d/fip file every time mkdev fip runs. Selection of the proper entry in /etc/gettydefs is critical for dial in/dial out ports. In general, you should avoid 7-bit entries and make sure that circulating entries (entries that may change the data rate of the port) are appropriate for the hardware connected to the port. For XENIX systems, ports can be used for both originate (dial- out) and answer (dial-in) by using the modem (uppercase) port with getty and using the non-modem (lowercase) port with dial- out programs. Use the non-modem port name in the entries for the Devices file. For SCO UNIX and Interactive UNIX, if you are using a modem on a port enabled for login, you should set up the getty or the uugetty in the /etc/inittab file to use the modem port (i.e. ttyS00 as opposed to ttys00). -------- Cautions -------- Always turn off the power to the system and to all the IntelliPort II components before you: - Unplug the cable from the controller or expansion module. - Decouple expansion modules from one another. When connecting multiple expansion modules, be sure to use the supplied clips to ensure proper operation. ------------------ Remote Diagnostics ------------------ Version 1.3.2 of the IntelliPort II UNIX/XENIX drivers now include a remote diagnostics utility. The fip_report utility runs on the host system and displays information about specified IntelliPort II ports. Synopsis fip_report [-?] [-m] [-x] [-i] [-q] [-u[k]] [-s] [-l sec] [-z msec] [[[-p ports ] [-b boxes] [-c cards]]|[-d dev]] Flags -? Lists the available options. -m Displays information on IntelliView Alternate screens. -x Displays information on IntelliPrint screens. -i Displays information about the specified controller. -q Be quiet (print no error messages) for ports not found. -u Unclogs any specified port waiting on flow control. For ports using CTS flow control, fip_report shuts off flow control entirely until you reinitialize the port with fip_reinit. For ports using XON flow control, fip_report only deasserts flow control; subsequent XON characters have their intended effect. -uk Unclogs any specified port and sends a SIGKILL to the process group. -s Displays a port summary. -l sec Loops every sec seconds until you press the DEL key. -z msec Specify the response timeout interval for the speci- fied controller. The default is 100 milliseconds. -p ports Specifies the ports to display. If this option (and the -d option) is omitted, fip_report prompts you for the ports. The argument ports can be a number, a range in the format nn-nn (where nn is a decimal num- ber from 00 to 15), or the keyword ALL. -b boxes Specifies the expansion modules to display. If this option (and the -d option) is omitted, fip_report prompts you for the expansion modules. The argument boxes can be a number, a range in the format n-n (where n is a decimal number from 0 to 3), or the keyword ALL. -c cards Specifies the controllers to display. If this option (and the -d option) is omitted, fip_report prompts you for the controllers. The argument cards can be a num- ber, a range in the format n-n (where n is a decimal number from 0 to 3), or the keyword ALL. -d dev Specifies the port(s) by device name (/dev/ttysnn, nn, or use shell wildcard expansion). NOTE: -d must be the LAST option specified on the command line. If you use this option, do not specify any of the -p, -b, or -c options. Example % fip_report -d /dev/ttys00 Valid data = Y Card = 0 Box = 0 Port = 00 (all numbers are 0 based) NOTE: UPPERCASE indicates the signal is active input rs232 signals = DTR RTS output rs232 signals = dcd cts RI dsr NOTE: RI (ring) is forced active on some cards (ISA4, ISA8, MC8, ...) The char counters are 16 bit (they will wrap at 65535) xmit char count since boot = 00053 rcv char count since boot = 00000 reasons why card is not transmitting data > There is no data in the card for this port. modem and non-modem port open status > The local (non-modem) port is open. % fip_report -i Please enter a card number (default is 0) or range (0-3) 0 Information for Card 0 The card is a IntelliPort-II Expandable Total IRQ's for all cards = 13 The board and driver are using IRQ 10 (decimal) The board is using 8 bytes of I/O address starting at 0x308 Firmware version on card is 1.0.2 Loadware version is 1.5.6 Driver Version is 1.3.2 On-board memory size is 512K CPU speed is 20Mhz CPU type is 80186 FIFO size is 1024 bytes Card interface I/O width is 16 bits The board has 1 boxes installed Box 0 has 16 ports The board is installed in a 16 bit slot Total ports = 16. The following shows the ports present (an * indicates port was found.) 0 3 7 15 23 31 39 47 55 63 +--+---+-------+-------+-------+-------+-------+-------+-------+ **************** %