C-KERMIT 7.0 INSTALLATION INSTRUCTIONS FOR STRATUS VOS Applies to: C-Kermit 7.0 Last update: Sat Apr 17 10:57:27 1999 Author: Kernie Brashier, Stratosphere, Ltd Copyright (C) 1985, 1999, Trustees of Columbia University in the City of New York. All rights reserved. See the C-Kermit COPYING.TXT file or the copyright text in the ckcmai.c module for disclaimer and permissions. Report problems, suggestions, fixes, etc, to: The Kermit Project Columbia University 612 West 115th Street New York NY 10025-7799 USA Email: kermit-support@columbia.edu Web: http://www.columbia.edu/kermit/ News: comp.protocols.kermit.misc DOCUMENTATION Frank da Cruz and Christine M. Gianone, "Using C-Kermit", Second Edition, 1997, Digital Press / Butterworth-Heinemann, Woburn, MA, ISBN 1-55558-164-1 US single-copy price: $44.95; quantity discounts available. Available in computer bookstores or directly from Columbia University: http://www.columbia.edu/kermit/manuals.html Features added after version 6.0 was released are documented in the text file, ckermit2.txt. OVERVIEW This file contains VOS-specific information. For a description of general (system-independent) configuration options for C-Kermit, please read the file CKCCFG.TXT. For information about known limitations or bugs, and possible workarounds, see the files CKCBWR.TXT and CKLBWR.TXT. Once you have built C-Kermit according to the instructions in this file, you should install it in a directory that is in the users' library paths, but that is not likely to be overwritten when you install a new version of the operating system. A good candidate would be >system>application_library. It might also be a good idea to make a "Kermit library" directory for sample files and non-man-page-style documentation. (master_disk)>kermit might be a good place for this. Some of the files that could go there are: ckermit.ini The standard initialization file. Users should copy this to their home directories. (In C-Kermit 6A(190) and later, you can designate a single copy as the system-wide initialization file; details below). ckermod.ini A sample customization file. Users should copy this file to their home directories, and make any desired modifications (user- or site-specific customizations). ckermit.kdd A sample dialing directory file. ckermit.knd A sample network directory. ckermit.ksd A sample services directory. ckermit.env A sample "environment variable" file ckedemo.ksc Macro definitions from "Using C-Kermit". ckevt.ksc Command file to demonstrate special screen effects from "Using C-Kermit". ckepage.ksc A sample script for sending alphanumeric pages. ckermit2.txt A file listing the updates, changes, and corrections made to C-Kermit since publication of the 2nd edition of "Using C-Kermit". ckcbwr.txt The general C-Kermit "beware" file. cklbwr.txt The VOS-specific C-Kermit beware file. READING A C-KERMIT DISTRIBUTION TAPE If you have received C-Kermit on tape from Columbia University, it will most likely be written as ANSI labeled, and certainly is not VOS save format. To read the files onto your system, do something like this, substituting your tape device name and supplying the density written on the tape. create_dir kermit_tape change_current_dir kermit_tape attach_port tape %s1#mt1.0 mount_tape tape -tape_format ansi -density 1600 -access_rights readonly read_tape tape * detach_port tape You should at this point have all the files on the tape in your kermit_tape directory, and can procede to either build C-Kermit yourself, or use the pre-built version on the tape. BUILDING C-KERMIT FOR VOS VOS C-Kermit is built with a command macro called cklmak.cm. This macro recompiles and binds ALL the modules involved. It does allow you to build into a different directory than the one containing the sources, so you can build for different machines into different directories if you need to. If you want to define a system-wide initialization file for C-Kermit, rather than making each user have her/his own copy, define the symbol CK_SYSINI to be the full pathname of the file, in the -kermit_options add: 'CK_SYSINI %s1#m1_d01>kermit>ckermit.ini' It is important that the string above get quoted properly, so if you are using a command line to do this it would come out something like: cklmak -kermit_options 'STRATUS DYNAMIC DCMDBUF CLSOPEN STRATUSX25 &+ ''CK_SYSINI %s1#m1_d01>kermit>ckermit.ini''' Note: if you build Kermit to execute a system-wide initialization file, this file can (and probably should) (be modified to) "chain" to the user's own initialization file (if any) by ending (or starting, depending on the desired precedence) with a command like: if exist \v(home)ckermit.ini take \v(home)ckermit.ini After you have built and tested the C-Kermit program successfully, you can discard the object (ck*.obj) files, which are no longer needed. Then you can copy the program modules to an application directory. There are several utility programs that come with C-Kermit you may or may not want. Most of them have documentation files (*.txt) that come along that explain what they are for. None of them are vital to using C-Kermit, though some are required to build it; these are built by cklmake.cm whether you ask for them or not. You can have cklmak delete the required files and not build the others by specifying -no_tools, but generally they are helpful programs to have. IF YOU DO NOT HAVE A C COMPILER Some of the files that come with the C-Kermit distribution are hex-coded versions of the compiled and bound C-Kermit executables. Versions are provided for the 68k, i860, and continuum processors. To bootstrap C-Kermit onto your system, you only need the command macro cklxtr.cm and the hex file for C-Kermit itself; the name of that file will vary depending on your processor type. The basename will be cklker, and the suffix will be .h68 for 68k machines, .h86 for i860 machines and .h71 for continuum processors. Also included is a hex version of a compiled extraction program, which runs much faster than the command macro version. Use the command macro to convert the conversion program and the compiled program to extract the main C-Kermit program. The extraction program is called cklxtr.pm, and is made from the appropriate hex file. Both the command macro and the program take two positional parameters, the input file, and the output file. The input file is the hex coded version of the program and the output file is resulting program module. The C source for the hexifying program is also included. After unloading all the necessary files into a directory, presumably using read_tape, convert the compiled conversion program (use the appropriate suffix for your system type): cklxtr cklxtr.h86 extract.pm Then extract C-Kermit: extract.pm cklker.h86 kermit.pm If you get an error that says something like "This program contains instructions not available on this processor," the most likely cause is that you have extracted the 68k program on a i860 machine or vice versa. Change the suffixes and try it again. The file formats used by the command macro and by the program are identical, so you can simply extract C-Kermit directly, but this two step process can save a great deal of time. The C-Kermit versions that are included in hex format are built without symbol tables, with optimization, and include support for X.25 and TCP/IP networking. APPENDIX: "Packing Slip" for C-Kermit 6.0 for VOS: (Some file names have been changed for C-Kermit 7.0) Organization: Stratosphere, Ltd Date: Fri, 7 Mar 1997 15:22:31 +0000 Subject: Kermit 6 deliverables To: "Richard S. Shuford" , From: "Kernie Brashier" Gentlemen: Das source is good and has been delivered to kermit.columbia.edu in the directory /kermit/incoming. I only included the files I changed to save time and space. Here is the list with the changes made: cklins.txt Updated documentation to reference release 7 instead of 6 cklker.71 Continuum 7100 kermit executable (jetta) cklker.h68 Motorola 68000 kermit executable (fresco) cklker.h86 Intel i860 XA/R kermit executable (atlantic) cklker.txt Updated references of kermit from 6 to 7 (release) cklmak.cm Modified command macro that builds kermit release. Added new source, deleted source references no longer required, modified script to not execute ckwart. Instead compile cklpro.c cklpro.c This is ckcpro.c with the few changes necessary for Stratus to compile. Apparently, our Stratus compilers do not like the way the wart program continues lines with the '\'. To ease confusion and prevent ckcpro.c from being overwritten, I copied and modified it and renamed it cklpro.c. With this release of kermit, I had to modify the build macro to NOT execute ckwart to extract ckcpro.c from ckcpro.w cklvos.txt rename cklaaa.hlp to cklvos.txt. Added documentation for VOS developers. Had I had this, it would have made my job a lot easier. Figured I would modify it so that next time, this would be a piece of cake.... cklxtr.71 Continuum 7100 extract utility (jetta) cklxtr.h68 Motorola 68000 extract utility (fresco) cklxtr.h86 Intel i860 XA/4 extract utility (atlantic) ckusig.c Added #ifdef for STRATUS to include defines for alarm and such. ckusig.c is the only "original" kermit code that had to change. I copied the #define references from ckuscr.c. It appears this should have been included in ckusig.c. Most have been an oversight. Once again thank you for the opportunity to participate in this update. Feel free to contact me if I can be of further assistance in the future. Best regards -kernie brashier Stratosphere, Ltd (End)