ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / MISC / NETWORK / UUPC11QD.ZIP / INSTALL.PRN < prev next >

Wrap

Text File | 1991-12-08 | 25.2 KB | 611 lines

December 8, 1991 Installing UUPC/extended 1.11q Table of Contents Table of Contents Table of Contents Table of Contents.............................................1 Viewing This Document on a Terminal...........................2 Revision......................................................2 Overview......................................................2 Installing or upgrading UUPC/extended.........................2 The Fine Art of Chat Scripts..................................6 Modem files...................................................8 Permissions (PERMISSN) files..................................8 Forward Files.................................................9 - 1 - December 8, 1991 Installing UUPC/extended 1.11q Viewing This Document on a Terminal Viewing This Document on a Terminal Viewing This Document on a Terminal This document includes overstrikes for printing on a printer. To read this document on-line, extract the program NOVRSTRK from the UUPC/extended optional programs archive and issue the following command: NOVRSTRK INSTALL.PRN INSTALL.TXT You can then browse the terminal ready version of the document, INSTALL.TXT. Revision Revision Revision This document applies to version 1.11q of UUPC/extended, and was last updated on December 8, 1991 by Drew Derbyshire. Overview Overview Overview This document provides installation instructions for UUPC/extended. Questions or suggestions on this document should be directed to the UUPC/extended help desk, help@kew.com. Installing or upgrading Installing or upgrading Installing or upgrading UUPC/extended UUPC/extended UUPC/extended Note: Note: Note: Because UUPC/extended now includes a total of 13 executable files, it is suggested that these files be placed in their own directory, and this directory then be added to your MS-DOS or OS/2 PATH variable. When this is done, be sure to delete any executable files for previous releases of UUPC/extended from other directories on your hard disk. Note: Note: Note: Each file that must be customized for UUPC/extended has comments in it describing the information that goes in the file. The general procedure for installing UUPC/extended is as follows: Backup your system.1 If upgrading UUPC/extended, read the CHANGES.PRN file for changes related to the newest release. In many cases, CHANGES.PRN includes documentation of new options and configuration file variables before any other documents. If upgrading from a release of UUPC/extended previous to 1.11a, you must clear your spool directories of files before installing the new release. In general, this is - 2 - December 8, 1991 Installing UUPC/extended 1.11q done by invoking UUIO for the previous release to deliver any queued files to other sites. Choose a host name for your system, and user id for yourself. Get the phone number, user id & password, and login procedure for the system that will act as your mail server. Under MS-DOS, add the following line to your CONFIG.SYS, or create a CONFIG.SYS in the root directory of your boot disk or diskette if you currently do not have one: FILES=20 Note: Note: Note: If you already have a FILES= line in your CONFIG.SYS, it should read at least 10 and should be raised to 20. If the number is greater than 20, then do not lower it. If you are upgrading from a release of UUPC/extended previous to 1.11p, delete the old version of UUXQT, UUXQT.COM. This has been replaced by UUXQT.EXE. If you are upgrading from a release of UUPC/extended previous to 1.11a, delete the old communications module, UUIO.EXE; this has been replaced by UUIO.BAT, UUCICO.EXE and UUXQT.EXE. If you are upgrading from a release of UUPC/extended previous to 1.09a, delete the old version of UUPOLL, UUPOLL.EXE. This has been replaced by a smaller UUPOLL.COM. Copy the MAIL.EXE, UUCICO.EXE, UUXQT.EXE and RMAIL.COM files to a directory in your path; the suggested name for this directory is \lib\uupc\bin. These files are required. Note: Note: Note: Several of the programs, including UUCICO and UUXQT, change directories as required to search for spool files. Because of this, programs such as RMAIL and (if used) RNEWS must be in your path. Having them in the current directory is not sufficient. Note: Note: Note: Version 1.11p of UUPC/extended includes two version of UUCICO, UUCICO.EXE and UUCICOLD.EXE. UUCICO.EXE includes support for newer serial port UARTS, but may not work on all systems. If this version of UUCICO does not work on your system, please send mail to plummer@wang.com describing the problem, and use the alternative version of UUCICO by copying UUCICOLD.EXE to UUCICO.EXE. Copy the SU.BAT, UUIO.BAT, FMT.COM, GENSIG.COM, NOVRSTRK.COM, UUPOLL.COM, UUSUB.COM, UUSTAT.COM, UUX.COM, - 3 - December 8, 1991 Installing UUPC/extended 1.11q and UUCP.COM files to a directory in your path. These files are optional. Note: Note: Note: Under OS/2, the SU.BAT and UUIO.BAT files can be copied to SU.CMD and UUIO.CMD. Also under OS/2, there are no .COM files; all modules have an extension of ".EXE'. Customize the UUPC.RC file, and copy it to the directory defined in the file as the 'ConfDir' within the file. This file defines the directories and other basic configuration parameters of UUPC/extended. Customize the SYSTEMS file and copy it to the 'ConfDir' directory defined in UUPC.RC. This file defines the names of other systems connected to yours and when and how to call them. Note: Note: Note: If you are converting from a release previous to 1.10a, you must update the SYSTEMS file to the newer format. See the sample SYSTEMS file for details. Create a PERMISSN (permissions) file in the 'ConfDir' directory defined in UUPC.RC. This file defines the access that remote systems have to your programs and data files. Basic instructions for a PERMISSN file which allows only mail are listed below. Copy to the 'ConfDir' directory and modify as needed any modem (*.MDM) files you need to define the behavior of your modem; files are included for the Hayes Smartmodem 1200, Hayes Smartmodem 2400, Microcom SX/1200, and others. See below for short discussions on writing modem files and general chat scripts, and see the supplied modem files for examples. Generate MAIL.HLP and TILDE.HLP in the 'ConfDir' directory defined in UUPC.RC via the NOVRSTRK program as follows: NOVRSTRK MAIL.PRN ConfDir\MAIL.HLP NOVRSTRK TILDE.PRN ConfDir\TILDE.HLP Where 'ConfDir' is replaced by the actual configuration directory name. These files provide on-line help to the MAIL command. If special routing is required for hosts, customize the HOSTPATH file, and copy it to the 'ConfDir' directory defined in UUPC.RC. This file is not usually needed, but can used to: Gateway mail from UUPC/extended to another mail program Alias the local host to another name Alias a remote host to another name Prevent improperly addressed mail from leaving the - 4 - December 8, 1991 Installing UUPC/extended 1.11q local domain Route mail via a non-default path If only one user will be using the system, customize the PERSONAL.RC file, and copy it to the 'ConfDir' directory defined in UUPC.RC. This file defines the personal configuration for a user of UUPC/extended, including his/her full name, home directory for storing files, and so forth. If multiple users are to share the same system, create multiple customized copies of the PERSONAL.RC in the 'ConfDir' directory defined in UUPC.RC, each with a unique name such as "TOM.RC", "DICK.RC" or "HARRY.RC". Customize the PASSWD file, and copy it to the 'ConfDir' directory defined in UUPC.RC, and add each user to the PASSWD file. This file defines the name and home directory of each local user, and the user id and password for remote users (systems) logging in. For each user, customize the PERSONAL.SIG file, and copy it to the 'Home' directory defined in PERSONAL.RC for that user. This file is appended to all outgoing mail for the user to provide a boiler-plate signature with the user's reply address. If this file is not installed, then the line in the PERSONAL.RC file describing it must be commented out with a pound sign (#) in column 1. Note: Note: Note: Especially for users of new systems, it is strongly advised that you do create a signature file and include in it your name, electronic mail address, snail mail address, and telephone number. This extra information is needed for a person to contact you if your electronic mail address cannot be replied to.2 Customize the ALIASES.TXT file, and copy it to the directory defined in the PERSONAL.RC file as your Home directory. This file defines short nicknames for longer e-mail addresses and lists of addresses. If this file is not installed, then the line in the PERSONAL.RC file describing it must be commented out with a pound sign (#) in column 1. Note: Note: Note: The addresses supplied in the ALIASES.TXT file, are valid addresses; they are provided as examples and to assist you in getting more information about UUPC/extended, communications software in general, USENET, and the Internet. However, they are not for random testing; abuses such as a recent user who sent mail to all the addresses in the file as a "hello world" test will force discarding of the live information in the file for future releases. - 5 - December 8, 1991 Installing UUPC/extended 1.11q Edit your AUTOEXEC.BAT (CONFIG.SYS if using OS/2), adding SET commands for the variables UUPCSYSRC, the fully qualified name of your UUPC.RC file, UUPCUSRRC, the fully qualified name of your PERSONAL.RC file, and for TZ, your local time zone. Sample TZ variable SET commands are as follows: SET TZ=EST5EDT or (Eastern Time, 5 hours behind GMT) SET TZ=EST5 (Eastern Time, but no daylight savings change) SET TZ=CST6CDT or SET TZ=MST7MDT or SET TZ=PST8PDT or (Pacific Time, 8 hours behind GMT) SET TZ=GMT0 (GMT, no offset, no daylight savings) Your mileage and time zone may vary. Time zones ahead of GMT should use a minus sign in front of the hours offset. Reboot your system to allow your changes to your AUTOEXEC.BAT to take effect. Test the system by sending mail to yourself (see below). The Fine Art of Chat Scripts The Fine Art of Chat Scripts The Fine Art of Chat Scripts The hardest part of setting UUPC/extended is setting up the chat scripts used in the SYSTEMS and various modem (*.MDM) files. A chat script, in its simplest form, is a series of strings sent to the modem or remote system alternating with the expected responses to those transmitted strings. On output, carriage returns are automatically appended to the strings unless explicitly overriden by the special escape sequence (\c). In UUPC/extended, the sequence always begins with an expected string, like this sample string to initialize a modem: "" "" "" ATZ OK \dATX4&D2V1E0 OK The first empty string ("") says to expect nothing, the second transmits nothing except the automatically appended carriage return, nothing is again expected in return, the string ATZ is sent followed a carriage return, OK is expected in response, the string ATX4&D2 is sent after a two second delay caused by the escape sequence \d, and finally a second OK is expected. Things to note about this sequence include the use of the empty strings to insure the ATZ command is issued at the beginning of a new line, and the use of the delay sequence (\d) to give the modem time to recover from the first command. The most common failure of new chat script writers is to omit delays where needed on - 6 - December 8, 1991 Installing UUPC/extended 1.11q output; this can cause a modem or system to lose characters and generally louse up one's day. To round out the escape sequences supported by UUPC/extended, the complete list follows; the empty string ("") is used on input, all other strings are recognized on output only. Quotation marks may used on input or output to enclose a string which includes whitespace. The list includes: "" Expect a NULL string BREAK Send BREAK \b Insert Backspace \B \d Delay two seconds \D \c Omit carriage return at end of string \C \m Insert carriage return \M \r \R \n Insert newline \p Delay four tenths of a second \P \t Insert tab character \T \s Insert space character \S \Znnnn Set serial port speed to nnnn \nnn Convert the numeric octal string nnn to a single character and transmit it \\ Insert a backslash (\) In addition, one other special syntax exists; to allow for alternate output when an expected string is not received, hyphens in an expect string delimit alternate output to be sent, such as: "" "" ogin:--ogin:--ogin: - 7 - December 8, 1991 Installing UUPC/extended 1.11q If a login prompt (ogin:) is not received by the standard timeout period (generally, 30 seconds), the string between the hyphens (nothing, followed by the appended carriage return) is sent; if no response is received, the sequence is repeated one more time. Modem files Modem files Modem files Modem files are configuration files which define the strings used to command a modem for dialing out; this allows commands always used with a particular modem to be written once rather being placed everywhere they are used, and also allows different modems to be used with the system by only changing the modem file (or changing the reference to the modem file in the SYSTEMS or UUPC.RC files). All strings defined in a modem file are standard scripts as described above with the exception of the dial prefix and dial suffix strings. These are combined with the phone number listed in the SYSTEMS file for a host and sent as one string to the modem when dialing out. Sample files are included for the Hayes Smartmodem 2400, Trailblazer 2500, the Microcom SX/1200, and a few other modems; most modems have behavior similar to one of these modems, so minor changes to one of these files should get you up and running. Note: Note: Note: If you make changes to modem file, copy it to a new name to avoid confusion with the distributed version. Permissions (PERMISSN) files Permissions (PERMISSN) files Permissions (PERMISSN) files For each system you contact, it must be defined in a PERMISSN file located in the UUPC/extended configuration directory. In the permissions file, systems can classified by whether they are called out to, dial in to the local system, or both. Note: Note: Note: If you allow anonymous logins, an entry should also be placed in the PERMISSN file for the system "*anonymous". Systems you call out to must have a MACHINE entry, such as MACHINE=system This defines the existence of the machine "system", and default permissions are granted to the system. These permissions include the ability to execute RMAIL and RNEWS, and the ability to send files to the spool directory. If the additional keyword REQUEST=YES is added to the MACHINE statement, then the remote system may also read and write files in your public directory, which is the directory defined by the variable PubDir in the UUPC.RC file. - 8 - December 8, 1991 Installing UUPC/extended 1.11q Systems which dial into you must have a LOGNAME entry, such as: LOGNAME=userid VALIDATE=system SENDFILES=YES This allows host "system" to login as user id "userid" with the same default permissions as described above. It further allows your system to transmit files to the other system even though it called you (SENDFILES=YES)3. However, to run UUXQT they must also have a MACHINE entry, because UUXQT does not look at LOGIN entries.4 Thus, to handle the general case, both of the above entries must exist in the permissions file, but they can be combined: LOGNAME=userid VALIDATE=system MACHINE=system SENDFILES=YES The remote system can be granted access to additional directories and programs through the use of additional parameters on the LOGNAME and MACHINE statements; these are documented in Managing UUCP and Usenet. Note: Note: Note: One difference between the PERMISSIONS file as defined in the Nutshell Handbooks and as implemented in UUPC/extended is that only one user id may be specified per LOGNAME entry in UUPC/extended. This restriction is by choice to prevent a system from logging in as another system. Forward Files Forward Files Forward Files UUPC/extended has the ability to forward mail destined for a single user or entire system or domain. Routing mail for an entire system or domain is performed via an entry in the HOSTPATH file, which is documented in the supplied sample HOSTPATH file. Forwarding mail for a single user is performed by placing a file named FORWARD in the user's home directory as defined in the PASSWD file, and contains one or more destinations, one per line as follows: address Simple address, subject to normal forwarding rules on the local system \address An address prefixed by a backslash; remote addresses are delivered normally, but if a local address it will be delivered without being subject to user id verification or forwarding. |command An MS-DOS command prefixed by an or bar (|). The mail is piped into the specified command. pathname An absolute path name. To be recongized as a file, the file must begin with a slash (/), a tilde (~), or a driver letter/colon sequence (x:). The mail - 9 - December 8, 1991 Installing UUPC/extended 1.11q is appended at the end of the specified file normally, with a line of binary ones separating mail items just as if it were a mailbox. For file names beginning with tilde (~), the file name is expanded as described in MAIL.HLP. As an example, the following data, if saved in the user's home directory under the name FORWARD, would cause the mail to formatted to the console via the UUPC/extended FMT program, to be forward to the postmaster normally, to be saved in the mailbox for user BOGUS without checking if such a user exists or has forwarding enabled, and finally to be saved in the user's home directory in the file BKUPMAIL.TXT: |FMT postmaster \bogus ~/BKUPMAIL.TXT 1If you do not currently backup your system, this is an excellent time to start. 2Recently, help@kew.com was sent the same query multiple times by a user with an invalid return address. He failed to include his telephone number or other address in his note; thus, both his original query and the follow-up letters asking why the original query could not be answered could not be replied to. 3The default, carried over from UNIX, is that files are only transmitted when you are the calling system. This means that SENDFILES=YES is not needed on a MACHINE statement. 4This is because UUXQT runs and processes eXecute files after UUCICO has terminated. As UUCICO has terminated, there is no way to tell if the file were delivered by an outbound or inbound telephone call. - 10 -