Columbia Kermit

home *** CD-ROM | disk | FTP | other *** search

/ Columbia Kermit / kermit.zip / c / ucapp2.doc < prev next >

Wrap

Text File | 2020-01-01 | 35KB | 775 lines

(*=== KERM.DOC1.TEXT ===*) >>>>>>>>>>>>>>>>>>>>>>> KERM.DOC1.TEXT >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ------------------------------------------------------------------------ | | | DOCUMENTATION FOR APPLE UCSD KERMIT ( Run-time Files ) | | VERSION RUG/PT V1.0 | | | | P. Terpstra | | Dept. Biochemistry | | University Groningen | | Nijenborgh 16 | | 9747 AG Groningen | | The Netherlands | | | | (20-dec-1985) | | | | Kermit-UCSD implements the Kermit file transfer protocol for the | | Apple II(e) under the UCSD-p-System V1.1 or V1.2. It works with a | | number of different serial cards in slot 2. It has been adapted from | | the IBM UCSD Kermit program. It is written mainly in UCSD Pascal | | with some 6502 assembly routines linked in. | ------------------------------------------------------------------------ ( If you have only the Kermit source files then read first part III in KERM.DOC3.TEXT. ) ----------------- PART I ----------------- ------------------------------------------------------------------------ HOW TO MAKE A SELF STARTING KERMIT DISK ------------------------------------------------------------------------ First transfer the following system files to an empty diskette: SYSTEM.PASCAL SYSTEM.APPLE SYSTEM.MISCINFO This disk KERMIT: contains the following files : 1) SYSTEM.ATTACH 2) ATTACH.DATA 3) ATTACH.DRIVERS 4) KERMIT.CODE 5) MAKEDATA.CODE 6) KERMIT.LIBRARY 7) UNKNOWN.TEXT 8) AP2.TEXT 9) APCOM.TEXT 10) SSC.TEXT 11) UNKNOWN.DATA 12) AP2.DATA 13) APCOM.DATA 14) SSC.DATA 15) KERM.DOC1.TEXT 16) KERM.DOC2.TEXT 17) KERM.DOC3.TEXT Transfer files 1,2,3 to your disk Transfer file 4 and rename it SYSTEM.STARTUP Transfer file 6 and rename it SYSTEM.LIBRARY Transfer one of the .DATA files (11..14) and rename it KERMIT.DATA. These files tell the Kermit program the type of acia on your serial card and other default parameters. Take : SSC.DATA for an Apple Super Serial Card AP2.DATA for an IBS AP2 serial card with a 6551 acia APCOM.DATA for an Apple Communications Card or a California SCC 7410 ASI 1 serial card or a Hayes Micromodem card or possibly any serial card with a 6850 acia. UNKNOWN.DATA if you do not know what type of card you have try this one. This may work but you will not be able to change from within the Kermit program the serial port settings. Also the values of these settings shown by the Kermit program may not be correct. Now you are ready to boot the disk. After the prompt "Kermit-UCSD>" type HELP to get an explanation of all the Kermit commands. If you type SHOW ALL, you will see a list of all the parameter settings. NOTE 1 - The .DATA file has the following defaults for the serial port: Baudrate 300, Wordlength 8 bits, 1 stopbit, no parity. An 80 column card is also assumed as the default. If you want to change these parameters or any other parameters in the .DATA file, then you can edit the corresponding .TEXT file (7..10). After the change execute the program MAKEDATA to transform the new .TEXT file to the file KERMIT.DATA. NOTE 2 - The Kermit program initializes the SSC or AP2 card completely according to the settings in the KERMIT.DATA file irrespective of the dipswitch settings on the card. For the Apple Communication Card ( and lookalikes ) the baud rate is only determined by the dipswitch setting on the card irrespective of the setting in the file APCOM.DATA ( for your own convenience make these settings equal ). ------------------------------------------------------------------------ SHORT INTRODUCTION TO KERMIT ------------------------------------------------------------------------ Kermit-UCSD belongs to a family of programs that do reliable file transfer between a microcomputer and a mainframe or between different microcomputers. Kermit-UCSD can also let the Apple II(e) behave as a terminal for a mainframe computer. In order to transfer files Kermit follows a certain protocol that the other side must understand. The host therefore must also have a Kermit program running in order to receive the Apple files. Files are sent as packages of printable Asci characters preceded by a <^A> and closed by a checksum. Non printable characters are converted to printable ones and preceded by a prefix character : e.g. CHR(13) ==> <#> <M> In this way Kermit avoids problems with control characters that are inter- preted differently by different hosts. If packets are not received correctly Kermit retries sending the packet a specified number of times before giving up the file transfer completely. File transfer with the Kermit protocol may be slower than other file transfer programs, but is very reliable! -------------------------------- KERMIT-UCSD AS TERMINAL PROGRAM -------------------------------- The terminal part of the Kermit-UCSD program can be used to communicate with a host computer. First make sure that the Apple serial port settings meet the requirements of the host. Then switch your modem on and make a connection with the host. After the prompt Kermit-UCSD> type CONNECT and press <return>. At the top of the screen you will see the following message: >Kermterm connecting to host (type <ESC> <C> to exit) You have now started the Kermit-UCSD terminal program Kermterm : everything you type at the keyboard will be sent to the host. Therefore type now <return> in order to get a reaction from the host. This is a general principle : type <return> when you think that the host is not responding. The host will now send its messages to enable you to login. After that you can start working on the host. If you type <ESC> while connected to the host you will get the following prompt from the Apple Kermit-UCSD: >Kermterm (<?> <C> <Q> <S> <Z>) => You are now talking to the Kermterm program. Type <?> to see the list of options the Kermterm program offers: will send a break signal to the host. <S> will show a list of all current Kermit-UCSD parameter settings. <ESC> will send the <ESC> character itself to the host. will turn on your printer to record the dialog with the host. <Q> will turn off your printer. <Z> will send <^A> <Z> to your Super Serial Card if you have one. This prevents the SSC to interpret <^A> as a command to the SSC card itself. You must do this, otherwise the <^A> preceding the Kermit packets during file transfer will never get through to the host and file transfer will not be possible. <C> will return you back to the Apple Kermit-UCSD command level. You will see "Back to the Apple Kermit UCSD" followed by the prompt "Kermit-UCSD>" . Remember that this does not logout the host!! You must logout yourself while connected to the host. If you have not logged out then you can return back to the host by typing CONNECT again. After you typed one of the above options ( except <ESC> <C> ) you will see the message : "Back to host." and you are again connected to the host. NOTE 1 - The option will not be shown if the Apple Kermit program does not know the acia type on your serial card. NOTE 2 - The & <Q> options are not shown if you don't have a printer interface card in slot 1. NOTE 3 - The printer option will only work with a Xon/Xoff protocol because a printer is a very slow device. Either define the Xon/Xoff characters at the Apple side ( SET XON-CHAR .... etc.) in accordance with the host requirements or define at the host's side the Xon/Xoff characters according to the Apple Kermit's settings. NOTE 4 - If host characters seem to be lost especially when the Apple screen starts scrolling you can try to define at the host's side a "linefeed-fill count" of greater than 0. If that does not help then you should login again at a lower baud rate. ( An Apple with a IBS AP16 80 column card ( or Videx card?) connected to a VAX will work at 1200 baud without a linefeedfill and at 4800 baud with a linefeedfill count of 5. ) NOTE 5 - The Kermit-UCSD program has a 256 byte circular REMIN buffer : If this buffer overflows you will hear a high pitched bell and the contents of the buffer will be lost. This situation could arise if the host is sending data while you are not in CONNECT mode. ------------------------------------- KERMIT-UCSD AS FILE TRANSFER PROGRAM ------------------------------------- The following is an example of a file-transfer dialog between the Apple and a VAX. 1) Start up the Apple Kermit. You will see the prompt "Kermit-UCSD>". 2) Check the serial port settings and the file-transfer parameters by typing "SHOW ALL". If these are not correct, change them with the "SET .." command. 3) Establish a connection with the VAX by typing "CONNECT". (see above). 4) After the Login procedure you will see the VAX/VMS prompt "$". 5) Start Kermit at the VAX by typing "@KERMIT" or "KERMIT". 6) You will now see the VAX Kermit prompt "KERMIT-VMS>". 7) If you want to send a file to the VAX give now the command "RECEIVE" to the VAX Kermit, followed by a <return>. 8) Go back now quickly to the Apple Kermit-UCSD level by typing <ESC> <C> 9) You will see again the prompt "Kermit-UCSD>". 10) Type now "SEND #5:APPLE.TEXT", followed by a <return>. 11) The screen display will change to give information about the ongoing file transfer. 12) If the transfer is done you will hear a bell, followed by the message "succesfull send" or "Unsuccesfull send" if something went wrong. 13) Go back now to the VAX by typing "CONNECT". 14) Type <return> and you will see again the prompt "KERMIT-VMS>". 15) If you want to send more files repeat step 7..14. If you want to stop the session give the command "QUIT" to the VAX Kermit. You will see the VAX/VMS prompt "$" again. You can now logout by typing "LOGOUT" and then go back to the Apple by typing <ESC> <C>. If you type now "QUIT" after the prompt "Kermit-UCSD>" you will return to the Apple UCSD-p-system command level. If you want to receive files from the VAX use the following dialog : 1..6) Same as above. 7R) Give the command "SEND [DIRECTORY]VAX.TXT", followed by a <return>. 8..9) Same as above. 10R) Type now "RECEIVE", followed by a <return>. 11..15) Same as above. NOTES : ad 8) - If you wait too long before giving a "SEND .." or "RECEIVE" command to the Apple UCSD Kermit, the Kermit at the host's side may have decided that the line is dead and may have aborted the transfer protocol. In that case you should tell the host Kermit to wait longer before starting the transfer protocol by giving a command like "SET DELAY 20" or "SET MAXTRY 20" ( consult the host Kermit's HELP explanations ). ad 10) - This Apple UCSD Kermit does not (yet) allow for wild-card characters in the name of the file to be sent : you can send only one file at the time. The suffix .TEXT can be omitted for textfiles. The name of the file to be sent should contain only alpha-numeric characters : all other characters are automatically changed to "X" by the Apple UCSD Kermit. If the volumename is omitted then the file should be present on the root or prefix disk. ad 7R) - The VAX Kermit does allow wild-card filenames after SEND : "SEND [DIRECTORY]*.TXT" will send all .TXT files from the specified directory to the Apple. The Apple UCSD Kermit will receive more than one file correctly. ad 10R)- The received files will be stored on the disk indicated by the "SHOW PREFIX" command. The prefix ":" means the root disk. Filenames for received files are truncated to the leftmost 10 characters and characters that are not allowed by the UCSD Filer are substituted by "X". The suffix .TEXT is added for textfiles. ad 11) - The display shows the current packetnumber (modulo 64) , the number of tries for each packet and the current filename. If DEBUG is set to ON then more information is displayed : The program state and the contents of the packets sent and received. File transfer will be slower however. If you want to break off manually the transfer protocol type <^E>. The Apple Kermit will then send an error packet to the host and both Kermits will abort the file-transfer. ad 12) - The Apple UCSD Kermit writes the received file(s) in 1024 byte (textfiles) or 512 byte (data/code files) pages to the disk. If an error occurs during file transfer ( e.g. disk full ), the current file is saved including the last full page received. (*=== KERM.DOC2.TEXT ===*) >>>>>>>>>>>>>>> KERM.DOC2.TEXT >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ------------------------------------------------------------------------ | | | DOCUMENTATION FOR APPLE UCSD KERMIT ( Run-time Files ) | | VERSION RUG/PT V1.0 | | | | | | (20-dec-1985) | | | ------------------------------------------------------------------------ ----------------- PART II ----------------- ------------------------------------------------------------------------ OVERVIEW AND SYNTAXIS OF APPLE UCSD KERMIT RUG/PT V1.0 COMMANDS. ------------------------------------------------------------------------ COMMAND SUBJECT PARAMETER ------- ------- --------- CONNECT - - EXIT - - QUIT - - RECEIVE - - (P)DIRECTORY - <volume number> SEND - <filename> SET BAUD <number> DEBUG ON / OFF DELKEY ON / OFF EMULATE ON / OFF END-OF-LINE <character> ESCAPE <character> FILE-WARNING ON / OFF IBM ON / OFF LOCAL-ECHO ON / OFF MAXPACK <number> MAXTRY <number> NOFEED ON / OFF PARITY NONE/ODD/EVEN/MARK/SPACE PREFIX <volume name> REJECT ON / OFF STOPBIT <number> TEXTFILE ON / OFF TIMEOUT <number> WORD-LENGTH <number> XOFF-CHAR <character> XON-CHAR <character> XOFF-WAIT-COUNT <number> (P)SHOW <one of the above subjects> (P)SHOW ALL - (P)HELP SET - (P)HELP SET <subject> (P)HELP <command> - (P)HELP - - - For an explanation of the commands : startup Kermit and type HELP. - PHELP, PSHOW and PDIRECTORY send their output to the printer (if present). - Commands, subjects and parameters should be separated by at least one space and terminated with a <return>. - Words in the command line can be abbreviated to the shortest non-ambiguous form. - The maximum length of the command line is 80 characters. - Control characters in the command line are echoed to the screen as e.g. <^X>. <backspace> and <return> are not echoed. However the sequence "SET END-OF-LINE<return>" will set the END-OF-LINE character to <^M>. ( see also the section on special character handling ). ---------------------------- SPECIAL CHARACTER HANDLING ---------------------------- The Apple UCSD p-system knows two classes of control characters that are treated specially when typed in from the Apple keyboard: Class I ------- <^S> stops/starts scrolling of the Apple console (program is interrupted). <^F> stops/starts output to the Apple console (program goes on). <^@> program break (system will be reinitialized). For the UCSD Kermit command line and during CONNECT these special characters are NOT checked. These characters can thus be part of the command line or can be sent to the host during CONNECT. In order to stop/start the output of the host to the Apple screen use the Xon/Xoff characters as defined for the host (e.g. <^S> and <^Q> ). During file transfer and on exit of the Kermit-UCSD program the normal action of these keys is reinstalled. Class II -------- A) 40 column screen ---------------- <^A> <^Z> <^K> <^W> <^E> are intercepted by the standard Apple UCSD keyboard driver for special screen handling functions. If you specify 40 in the last line of the KERMIT.DATA file then these characters will keep their normal Apple UCSD function, but they can not be sent to the host. For the 40 column screen you should change the file-transfer interrupt key in the KERMIT.DATA file from <^E> to something else. B) 80 column screen ---------------- If you specify 80 in the last line of the KERMIT.DATA file then the <^A> <^Z> <^K> <^W> <^E> keys will lose their special function even if you do not have an 80 column card. If your system has an 80 column card then the Apple keyboard will not be checked by the standard Apple UCSD keyboard driver but by a driver program in ROM on your 80 column card. This driver may have its own special character checking (like <^A> and <^K>). The UCSD Kermit program has no influence on this. To find out which key-codes cannot be sent to the host, test the keys after the prompt "Kermit-UCSD>" and see if they give an echo to the screen. ---------------------------------------------------------- FUNCTION OF SYSTEM.ATTACH, ATTACH.DRIVERS AND ATTACH.DATA. ---------------------------------------------------------- General ------- The SYSTEM.ATTACH program should be present on the boot disk. It is auto- matically executed before SYSTEM.STARTUP. It modifies the BIOS of the Apple UCSD p-system to allow for user-defined device drivers. The user-defined driver program is in the library ATTACH.DRIVERS and is installed in memory below the p-system heap. The file ATTACH.DATA contains instructions for SYSTEM.ATTACH. For more information consult: V1.1 : The disk ATTACHUD (I.A.C. International Apple Core) with the document "ATTACH-BIOS Document for Apple II Pascal 1.1. By Barry Haynes, Jan 12, 1980". V1.2 : Apple II Pascal Device Support Tools (Workbench Series) A2W0014 (Apple Computer Inc.) NOTE: The SYSTEM.ATTACH on this disk comes from the I.A.C. disk. The version bytes of this SYSTEM.ATTACH have been patched in order to make it work also with the Apple UCSD p-system V1.2. Function of the attached driver: -------------------------------- In the Apple UCSD p-system V1.1 and V1.2 the UCSD Pascal procedure UNITSTATUS is not implemented for the device REMIN: and REMOUT:. This means that one can not determine for REMIN whether there is a character at the serial input port, waiting to be read. The Pascal statement READ(remin, char) thus will wait in a closed loop until a character has arrived at the serial input port. In V1.2 this unacceptable situation has been partly resolved by the new procedure REMSTATUS in the unit APPLESTUFF. However REMSTATUS only works for an Apple Communication Card or a Firmware Card like the Super Serial Card. The new serial card driver in ATTACH.DRIVERS does implement the procedure UNITSTATUS (see below) for a number of serial cards. In addition it has the following features : - When first initialized (cold boot) it recognizes the serial card type in slot 2 and binds into the system the appropiate UNITSTATUS and UNITREAD routines. Then it jumps to the standard UCSD serial card initialization routine to set the default serial port parameters. - It installs a circular 256 byte serial input buffer. The serial input port is checked for an incoming character every time the UCSD system performs an I/O operation and the character (if present) is stored in the buffer. The UNITREAD or READ procedures then read only the buffer. ( This is completely analogous to the implementation of the type-ahead buffer for the keyboard driver. ) - If the circular REMIN buffer overflows then a high pitched bell is heard and the current content of the buffer is lost. - When reinitialized (warm boot or UNITCLEAR(7) ) the buffer is emptied, but the serial parameter settings remain unchanged. How to use this SYSTEM.ATTACH for your own programs --------------------------------------------------- The UNITSTATUS procedure is a standard UCSD p-system procedure like UNITWRITE, UNITREAD and UNITCLEAR and is meant for communication between a Pascal program and a device driver. It has the following form : UNITSTATUS( Device_number, Data_record, Control_Word ); The following examples explain its use for this REMIN/REMOUT driver : Use the following declarations : CONST Remin_Device = 7; { or Remin_Device = 8; effect is the same } TYPE Cntrl_Word_Rec = PACKED RECORD Channel : ( outp, inp ); Purpose : ( status, control ); A_Reserved : 0..2047; Special_Request: ( none, special_function ); B_Reserved : 0..3; END; A_Remin_Rec = RECORD Addres : INTEGER; Value : INTEGER; END; B_Remin_Rec = ( all_sp_char, stop_flush_break_sp_char, scr_40_sp_char, no_sp_char, mask_msbit_remin, no_mask_msbit_remin ); C_Remin_Rec = INTEGER; VAR Control_word : Cntrl_Word_Rec; Memory : A_Remin_Rec; System_Default : B_Remin_Rec; Remin_Buf_count : C_Remin_Rec; I) Check the number of characters in the remin buffer. --------------------------------------------------- WITH Control_Word DO Channel := inp; { or Channel := outp; same effect } Purpose := status; A_Reserved := 0; Special_Request := none; B_Reserved := 0; END; UNITSTATUS( Remin_Device, Remin_Buf_count, Control_word ); ---------- The number of characters currently present in the remin buffer is now returned in the variable Remin_Buf_count. II) Change a system default value. ------------------------------ WITH Control_Word DO Channel := inp; { or Channel := outp; same effect } Purpose := control; A_Reserved := 0; Special_Request := none; B_Reserved := 0; END; System_Default := no_sp_char; UNITSTATUS( Remin_Device, System_Default, Control_Word ); ----------- The meaning of the different system default values is: ( see also the section on special character handling ) all_sp_char : Class I and Class II special characters will be checked by the keyboard driver. stop_flush_break_sp_char: Only Class I special characters will be checked. scr_40_sp_char : Only Class II special characters will be checked. no_sp_char : Class I and Class II special characters will not be checked. mask_msbit_remin : The most significant bit of the received characters at the serial input port is set to 0. no_mask_msbit_remin : The most significant bit of the received characters is left unchanged. The system startup default values are : all_sp_char and mask_msbit_remin. III) Get the value of a memory location ( PEEK ). -------------------------------------------- WITH Control_Word DO Channel := inp; { or Channel := outp; same effect } Purpose := status; A_Reserved := 0; Special_Request := special_function; B_Reserved := 0; END; Memory.Addres := ........; Memory.Value := 0; { initialize Value first : was declared as Integer } UNITSTATUS( Remin_Device, Memory, Control_Word ); ---------- The value of the specified memory location is now returned in Memory.Value. IV) Change the value of a memory location ( POKE ). ----------------------------------------------- WITH Control_Word DO Channel := inp; { or Channel := outp; same effect } Purpose := control; A_Reserved := 0; Special_Request := special_function; B_Reserved := 0; END; Memory.Addres := ..........; Memory.Value := ..........; UNITSTATUS( Remin_Device, Memory, Control_Word ); ------------ The specified value will now be stored at the specified address. The possibility to peek and poke with this UNITSTATUS routine can be used to address the control and command registers of the acia on the serial card directly. NOTE: For each function of this UNITSTATUS routine the controlword should be defined differently! If you do not specify the correct controlword strange things may happen, especially when you start to poke without being aware of it! (*=== KERM.DOC3.TEXT ===*) >>>>>>>>>>>>>>> KERM.DOC3.TEXT >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ------------------------------------------------------------------------ | | | DOCUMENTATION FOR APPLE UCSD KERMIT ( Source Files ) | | VERSION RUG/PT V1.0 | | | | P. Terpstra | | Dept. Biochemistry | | University Groningen | | Nijenborgh 16 | | 9747 AG Groningen | | The Netherlands | | | | (20-dec-1985) | | | ------------------------------------------------------------------------ ----------------- PART III ----------------- The source text of the Apple UCSD Kermit program is obtainable on two disks from the above address. This file explains how to compile the source text into a working Kermit program. ---------------------------------- CONTENTS OF THE SOURCE DISKS ---------------------------------- Disk KERTEX1: ------------- KERMIT.TEXT The main Kermit program. KERMGLOB.TEXT Intrinsic SYSTEM.LIBRARY Unit. Contains all globals. KERMACIA.TEXT " " " KERMUTIL.TEXT " " " KERMPACK.TEXT " " " SENDER.TEXT " " " RECEIVER.TEXT " " " PARSER.TEXT " " " KERMSETSHW.TEXT " " " KERMINIT.TEXT " " " HELPER.TEXT " " " ASM.KERMIT.TEXT 6502 Assembly procedures Disk KERTEX2: ------------- KERMTERM.TEXT The Kermit terminal procedure in 6502 assembly. REMDRIVER.TEXT The REMIN/REMOUT driver for ATTACH.DRIVERS REMDR.DOC.TEXT Introduction to REMDRIVER.TEXT. AP2.TEXT Setup parameters for IBS AP2 card. APCOM.TEXT " " " Apple Communications Card SSC.TEXT " " " Super Serial Card UNKNOWN.TEXT " " " unknown serial card MAKEDATA.TEXT Program to transform setup parameter textfile into KERMIT.DATA file. ATTACH.UPD.TEXT Program to update SYSTEM.ATTACH from the I.A.C. disk ATTACHUD to version 1.2 compatibility. KERM.DOC1.TEXT Documents the run time disk KERMIT and gives an intro- duction to the program Kermit. KERM.DOC2.TEXT Documents the Kermit commands and explains the SYSTEM.ATTACH and ATTACH.DRIVERS. KERM.DOC3.TEXT You are reading it. -------------------------------------------------- INTERRELATION OF THE INTRINSIC UNITS -------------------------------------------------- Unit USES KERMGLOB KERMUTIL KERMPACK KERMACIA linked to ASM.KERMIT ---- ---- -------- -------- -------- -------- -------------------- KERMGLOB - - - - - KERMACIA + - - - + KERMUTIL + - - - + KERMPACK + + - - + SENDER + + + - - RECEIVER + + + - - PARSER + + - - - KERMSETSHW + + - + - KERMINIT + + - + - HELPER + + - - - The main program KERMIT uses all of the above units and is linked to KERMTERM. --------------------------------------------------- HOW TO COMPILE THE KERMIT PROGRAM --------------------------------------------------- 1) - Assemble ASM.KERMIT.TEXT, KERMTERM.TEXT and REMDRIVER.TEXT 2) - Make an empty SYSTEM.LIBRARY on the boot disk using the system program LIBRARY. 3) - Compile KERMGLOB.TEXT and transfer the .CODE file to the SYSTEM.LIBRARY. 4) - Compile KERMACIA.TEXT and KERMUTIL.TEXT. With the SYSTEM.LINKER link in some procedures from ASM.KERMIT.CODE. Transfer the linked KERMACIA.CODE and KERMUTIL.CODE to the SYSTEM.LIBRARY. 5) - Repeat step 4 for KERMPACK.TEXT. 6) - Compile now SENDER.TEXT, RECEIVER.TEXT, PARSER.TEXT, KERMSETSHW.TEXT, KERMINIT.TEXT and HELPER.TEXT. Transfer the corresponding .CODE files to the SYSTEM.LIBRARY. The SYSTEM.LIBRARY is now complete. 7) - Compile the main program KERMIT.TEXT and link in the procedure Kermterm from the file KERMTERM.CODE. 8) - Compile the program MAKEDATA.TEXT and run it. This will produce the file KERMIT.DATA suitable for your system. ( see also KERM.DOC1.TEXT ). 9) - Run the program LIBRARY. Choose the option New file and transfer REMDRIVER.CODE to slot 0. Give this library the name ATTACH.DRIVERS. 10) - You have now all the needed run time files except SYSTEM.ATTACH and ATTACH.DATA. These two files are not supplied on the source disks, but are present on the run time disk KERMIT. If you do not have the run time disk then you should obtain the program ATTACHUD present on : A) The disk ATTACHUD (I.A.C. International Apple Core) with the document "ATTACH-BIOS Document for Apple II Pascal 1.1. By Barry Haynes, Jan 12, 1980". For V1.1. ( and patched for V1.2 ). B) "Apple II Pascal Device Support Tools" (Workbench Series) A2W0014 (Apple Computer Inc.). For V1.2 These disks contain SYSTEM.ATTACH and the program ATTACHUD to produce the file ATTACH.DATA ---------------------------------------------- HOW TO MAKE THE FILE ATTACH.DATA ---------------------------------------------- With ATTACHUD from the I.A.C. disk ---------------------------------- 1) - Run ATTACHUD and answer the questions in the following way: 2) - Name of the attach data file? --> ATTACH.DATA 3) - Driver uses Hires page one? --> N 4) - Driver uses Hires page two? --> N 5) - Name of the driver? --> REMDRIVER 6) - Driver refers to unit number? --> 1 7) - Initialize at boot time? --> N 8) - Driver refers to another unit?--> Y 9) - Driver refers to unit number? --> 2 10)- Initialize at boot time? --> N 11)- Driver refers to another unit?--> Y 12)- Driver refers to unit number? --> 7 13)- Initialize at boot time? --> Y 14)- Driver refers to another unit?--> Y 15)- Driver refers to unit number? --> 8 16)- Initialize at boot time? --> N 17)- Driver refers to another unit?--> N 18)- Align driver on byte boundary?--> N 19)- Attach another driver? --> N This will finally produce the ATTACH.DATA file. If you want to use the SYSTEM.ATTACH from this disk with V1.2 then compile the program ATTACH.UPD.TEXT on KERTEX2 and run it. This program will update the old SYSTEM.ATTACH. With the Apple II Pascal Device Support Tools disk. --------------------------------------------------- 1)..18) same questions and answers as above. 19) - Transient initialization section? --> N 20) - Driver uses interrupts? --> N 21) - Attach another driver? --> N This will produce the ATTACH.DATA file. The SYSTEM.ATTACH on this disk can NOT be used with V1.1. The ATTACH.DATA file produced here is not compatible with the old SYSTEM.ATTACH nor is the ATTACH.DATA file produced by the I.A.C. program compatible with the new SYSTEM.ATTACH! Once you have all the run time files you can make a self starting disk as explained in KERM.DOC1.TEXT.