Super Net 1

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

/ Super Net 1 / SUPERNET_1.iso / PC / OTROS / EXTRAS / UUCODE / UUCP / SNUUPM23.ZIP / SNUUPM23.DOC < prev

Wrap

Text File | 1994-01-26 | 58.2 KB | 1,572 lines

snuupmXX.doc Rhodes University Computing Centre ---------------------------------- SNUUPM ------ 24 January 94 - Version 23 - Mike Lawrie ---------------------------------------- A Combined SNews/UUpc/PMail system for MS-DOS --------------------------------------------- ------------------------------------------------------------------------ Please Note: "Portions of this software were derived from SNews, which is copyright by John McCombs <john@ahuriri.gen.nz>, and are included by permission of the author. NOTE: This version of SNews is not distributed under the GNU Public Licence. No warranty is offered by John McCombs in respect to this software and no liability is accepted for the consequences of its use." Similar caveats apply to PMAIL, UUPC, DOUGMENU - read the documentation files within those packages for full details regarding constraints on use and on redistribution. Some extracts are give below. ------------------------------------------------------------------------ FILES REQUIRED IN ORDER TO INSTALL SNUUPM ----------------------------------------- You need to copy the following files into a single directory, from which you run the install process:- SNUUPMxx.ZIP (where "xx" is the 2-digit version number) DMENU168.ZIP PMAIL301.ZIP SNEWS191.ZIP UPC12BAD.ZIP UPC12BD1.ZIP UPC12BD2.ZIP UPC12BD3.ZIP You will obtain these files off the main archive servers of the Internet. (eg wuarchive.wustl.edu: /mirrors/msdos/uucp or omnigate.clarkson.edu: /pub/msdos/uucp). If all else fails, try hippo.ru.ac.za: /pub/pc/snuupm. The DOS programs "find", "sort" and "more" are also required. ------------------------------------------------------------------------ T H A N K S ----------- The author of SNUUPM would like to express his thanks to:- the authors of SNEWS, UUPC and PMAIL. Paul Nash for the idea, initial work and the original uu2pm.exe program, all of which led to the development of SNUUPM. Dave Wilson for help with enhancements to SNUUPM. various folk at Rhodes University who have been brave enough to give it a try in the development stage. a goodly number of folk on the Internet who have been kind enough to report problems, and sometimes to provide the fixes. Look in c:\usr\lib\snuupm\changes to find out who suggested what. Some of these folk, in alphabetical order, are:- Americo Muchanga of Mozambique Arvind Kumar of USA Dave Wilson of South Africa Don Findley of Mozambique Eberhard Lisse of Namibia Gordon Taylor of New Zealand Ian Dore of South Africa Jiri Kuchta of Czechoslovakia Klaus Hektor of Argentina Royce Robbins of USA, while based in Lesotho Scott McNabb of New Zealand Quentin Jones of Australia ------------------------------------------------------------------------ INTRODUCTION ------------ Electronic mail has become a very widespread means of communication. What started off as requiring huge computers and expensive networks is now available on the ubiquitous DOS-based PC, and can use a modem that costs between $50 and $200. The telephone cost of communicating by email is less than 2% of that of fax, and there is no expensive paper required. One telephone call can send and receive all of the email that is directed to and from all addresses - this saves having to make a multitude of phone calls for multiple recipients, and (in the case of international dialing) it allows for the costs to be kept in a country where the telephone rates are low. Email does not have the glitches of fax, due to the superior error-correcting protocols used by email. It is now possible for private individuals who have a PC, a modem and a telephone, to join the world of email at an extremely low cost. The software package described in this document is available at no cost for non-commercial use. There are NO catches. The installation and operational procedures are simplicity itself. The PC DOS packages known as SNews, UUpc, and PMail have been strung together to form a single suite called SNUUPM. This idea, as far as the author of SNUUPM knows, came from Paul Nash <paul@frcs.alt.za>, but what now exists has been enhanced somewhat on his original work. This document describes the method that has been used to link these packages into a simple to use email and usenet news system, but with full facilities. The DOS directory structure that has been used is Unix-like, so knowledge gained from the use of the one is relevant to the other. The DOUGMENU package allows for a simple user interface to be provided. The objective is to produce a standalone DOS-based email and Usenet news system that connects via a telephone call to a suitable uucp mailserver computer. The programs are such that a LAN of PCs could be linked in this way such that each PC on the LAN can access email, but the SNUUPM package is not (yet) geared to this. The author of SNUUPM simply does not have the enironment in which to develop this, but there are people on the network who are doing this kind of thing. A major design criteria is that the SNUUPM system must be easy to install and simple to operate, and must be rugged. The purpose of developing this package is two-fold. One is to allow students and former students of Rhodes University to stay in touch with their alma mater. The other is to spread email into undeveloped countries. In both regards the package has been highly successful. The hardware needed is simply an MS-DOS based PC with a hard disk and a modem. The system has been tested under MS-DOS 3.3 and 5.0, with CGA, EGA and VGA. In order to comply with conditions of distribution of the indvidual component packages of SNUUPM, those individual packages need to be acquired separately (see elsewhere in this document for details). SNUUPM itself consists of the single file SNUUPMxx.ZIP, where 'xx' is the version number. Apart from having a PC, a modem and the software, you have to make arrangements with another computer (ie, a mailserver) in order to exchange email and/or news with that computer. Any computer that runs the widely available uucp 'g' protocol will do, but clearly one that has a direct connection to the TCP/IP Internet that spans the world would be an excellent choice. But whatever computer you choose, you need to agree on certain information with whomever runs that computer. The minimum information is:- name of your PC domain in which this name resides name of the mailserver telephone number of the mailserver password of your PC for logging into that mailserver name of your organisation make and model of modem that you are using baud rate between your PC and your modem You might well need to know the specific configuration of your modem so that it is compatible with that of the mailserver. This information should be obtainable from the mailserver site. The modem files that are part of the package have been written and tested by active users of the UUPC package, so they should work with minimum changes. Armed with the above information, follow the QUICKSTART section, and you could be exchanging email with Internet sites within 30 minutes or less. ------------------------------------------------------------------------ QUICKSTART ---------- You will need about 4 Mb in a drive of your choice in order to install the package (this includes the space for the non-SNUUPM files). More space is needed on the same drive to hold your email and news items. When installed, the total package occupies about 1.2 Mb if you run pklite on most of the .COM and .EXE programs in \usr\lib\snuupm\. No files are installed into the top-level directory, but rather they go into (your\choice)\etc and (your\choice)\usr. It is sensible and practicable to make the 'your\choice' be simply the name of a disk drive, and not a lengthy path (eg C: is better than c:\some\long\path). Step 1 If you have not yet unzipped the SNUUPM distribution file, then proceed as follows:- (make some convenient temporary directory, say c:\tmp) (change to that installation directory) (copy in somehow the files that are needed to install SNUUPM) PKUNZIP SNUUPMxx.ZIP (where xx is a 2-digit version number) (make a directory into which you will install SNUUPM, c: is fine) The pkunzip'ing of SNUUPMxx.ZIP will create the .DOC file that you are presently reading, as well as the files SNUUPM.ZIP, INSTALL.BAT and INSTALL.MNU. Step 2 Edit your AUTOEXEC.BAT file to have the following lines (best to copy them in from this .DOC file, don't try typing them directly):- rem -------------------------------------------------------- rem SNUUPM additions to AUTOEXEC.BAT rem -------------------------------------------------------- rem Set sndrive to be the disk drive or the directory from rem which you will run SNUUPM. set sndrive=c: rem rem You might wish to change pmuser later, to be the user-id rem of the person who uses this PC the most often, but for now rem leave it set to "root" set pmuser=root rem rem Set TZ to be suitable for your timezone rem For reasons known (only?) to the author of UUPC, the value rem that you set in this TZ variable is added to the time rem that appears in the mail messages. Clearly, the time in rem your PC is your local correct time, and needs no mathematics rem to be done on it, but that's how the package is written. rem For whatever reason, if you are AHEAD of GMT then you rem use a negative sign, if you are BEHIND GMT then you rem use a positive sign. Good old US-centric authors, but rem then you can always ask for you money back. rem South Africa is 2 hours to the East of GMT, ie when it rem is midday in South Africa then it is 10:00 am in London. set tz=GMT-2 rem rem You might have set TMP for some other package, in which case rem there is no need to reset it here. rem set tmp=%sndrive%\tmp rem rem The SNUUPM installation process will invoke your favourite rem editor program if you have set the EDITOR environment rem variable to some suitable value. The author of SNUUPM rem has resigned himself to using vi, which he gets from the rem CALVIN or ELVIS packages. rem set editor=c:\bin\vi.exe rem rem From here on, don't change anything rem ----------------------------------- set path=%sndrive%\usr\lib\snuupm;%path% set uupcsysrc=%sndrive%\etc\uupc\uupc.rc set uupcnews=%sndrive%\usr\spool\news set uupcusrrc=%sndrive%\usr\%pmuser%\%pmuser%.rc set snewsrc=%sndrive%\usr\%pmuser%\snews.rc rem ----end of SNUUPM setup--------------------------------- The rest of this document assumes you have used drive C:. However, as mentioned above, you may choose to use any other drive or directory for installing the package (by altering the setting of 'sndrive'). NOTE 1: The "tmp=%sndrive%\tmp" can be changed if you have a moderately large RAMDISK (say much more than 64 Kb), or it can point to any suitable temporary directory. NOTE 2: The "tz=GMT-2" appears to be appropriate for South African time, which is 2 hours to the east of the zero meridian. Step 3 Edit your CONFIG.SYS file to set a moderate amount of space for environment variables, eg:- shell=c:\command.com /e:2048 /p If you are running under Windows, ensure that the setting of the CommandEnvSize is also at least 2048 - this is done in the file \WINDOWS\SYSTEM.INI. Step 4 Now reboot so that the AUTOEXEC.BAT and CONFIG.SYS parameters take effect. Step 5 Proceed with the installation by typing cd ... (to the directory holding the SNUUPM .ZIP files) install This leads you via a series of menus through the install process. You have to specify the basic information that any mailing system needs, by means of the System Setup submenu. You can elect to install PMAIL and SNEWS together or to omit the installation of SNEWS if you so choose. The INSTALL option will install SNUUPM in subdirectories ETC and USR of the directory defined by the "set sndrive" command in your AUTOEXEC.BAT file. The install process pkunzips the files SNUUPM.ZIP, creates directories and sets up some basic newsgroups. There are a number of predefined modem files from which you must select. Most of them are part of the UUPC package, but those that have been developed at Rhodes University are:- FIRSTV22 First V.22bis FX14400 Practical Peripherals FX14400 V32.bis PENRIL Penril 14.4 SARONV22 Saron V22.bis ZMFC9624 Zoom Fax FC96/24 MAKE SURE THAT YOUR MODEM DOES NOT USE XON/OFF FLOW CONTROL, AS THIS WILL CAUSE THE UUCP TRANSFERS TO HANG. USE RTS/CTS FLOW CONTROL INSTEAD. Step 6 You might need to edit some of the files if they don't "look right". For example, the COM port of the c:\etc\uupc\modem.mdm file might need to be changed, and you might need to alter the ATDP or ATDT modem string according to your telephone system. That's All You are now ready to run the system. Type:- snuupm and follow the menus. None of the install files are required once the package is installed, so they may be deleted. You might one day wish to look into the various documentation files of the individual packages (eg dougmenu), so retain copies of the .ZIP files. You can modify your installation at a later stage without having to remove and reinstall the entire package. Now read on only if you wish to find how the component packages dovetail together. The definitive information regarding the individual packages is contained in the the distribution files of those packages. There is also some information from some of the users of the system, who have installed the package in an environment different to that of the authors. This information is included with permission. ------------------------------------------------------------------------ User's Tips/Comments -------------------- From niherst!lars_j@upr2.clu.net Fri Dec 10 00:21:53 1993 Return-Path: <niherst!lars_j@upr2.clu.net> Received: from upr2.clu.net by hippo.ru.ac.za (4.1/Hippo-02.06) id AA08755; Fri, 10 Dec 93 00:21:29+020 Received: by upr2.clu.net (/\==/\ Smail3.1.28.1 #28.13) id <m0p7uGw-00001JC@upr2.clu.net>; Thu, 9 Dec 93 17:55 EST Received: by niherst.gov.tt (1.65/waf) via UUCP; Thu, 09 Dec 93 17:47:03 AST for ccml@hippo.ru.ac.za To: ccml@hippo.ru.ac.za Subject: Greetings from Trinidad From: lars_j@niherst.gov.tt (Lars Johnson) Message-Id: <7V7aec1w165w@niherst.gov.tt> Date: Thu, 09 Dec 93 17:00:53 AST Organization: National Institute of Higher Education Status: RO Hi, Mike! I've spent most of today drafting a report of our EMAIL project, and I thought that perhaps you would appreciate knowing that your SNUUPM is very well recieved by us. I'd also like to give you some advance warning of some things, so that you will be able to indicate wherever you think I may be compromising the permission to use SNUUPM which is implicit and explicit in the documentation. Thus, please understand that the "consultant's role" in which I have cast you is largely a matter of salesmanship, and in no way is intended by me to indicate a binding committment on your, or anyone's part. In turn, let me say that if you like the things which I say about SNUUPM after only a couple days' use, feel free to use ALL my Advertising Copy: I was Account Executive at McCann-Erickson (Trinidad) Ltd. for three full years, and I know what sells. SNUUPM can make money for you, in today's INTERNET-aware world. My advice? Forget giving it away; forget shareware; go COMMERCIAL in as big a way as you can NOW! (Research the market first, though!) BTW, have you given any thought to the Packet-Radio medium for netting? I'd be interested to get your feedback on that, also. advantages of SNUUPM vs WAFFLE To: [name removed] [some text removed], Trinidad/Tobago. [para removed] This UUCP-for-DOS software offers the following main advantages over WAFFLE: 1) Clearer, cleaner, more business-like user interface, with an intuitive hierarchy of menus. 2) All functions are available through a single, main menu. 3) Novell NetWare compatibility is built-in (In fact the mail module, "Pegasus Mail", was written by David Harris as an alternative interface to the mail module of NetWare v. 2.15 and higher. Among its more unusual and attractive features is its price: FREE) 4) Allows easy multi-user access to email accounts (via individualized log-in procedures), whilst preserving system administrator status for a "Root" or "Super-User" account. 5) Built-in message/text/file editor is far and away superior to the WAFFLE editor, offering among other features which WAFFLE does not have: - easy movement between lines via word-processor type commands and cursor keys. - easy text formatting (margins, tabs, etc .) - message mode allows carbon copies, blind copies, alias recognition on the address fields. - allows the composition of special characters from the ASCII extended character set. - does spell-checking, and includes 5000 term user- maintained dictionary as well as 60,000 word built-in dictionary. - maintains templates for frequently contacted addressees - will save work in progress if the writer is interrupted before he or she has completed the message. The user is prompted, upon logging in for the next time, whether to resume the previous email, (there's that insidious, insipid, inchoate, noun again! When I read my MAIL I don't read IT MAIL by MAIL, but LETTER by LETTER. Ergo, when reading my EMAIL, I read IT MESSAGE by MESSAGE, n'est-ce-pas?) or to begin another email message. - context-sensitive, on-line help. 6) User-lists, address books, distribution/mailing lists, from which text can easily be selected via a highlight bar, for insertion into messages, either as addresses, or as content. 7) MIME (Multi-purpose Internet Mail Extensions), a recent INTERNET standard for transmitting binary attachments to normal ASCII text messages is supported. (N.B. I have not verified this feature yet, though I have no doubt that it works, and that it will make life considerably easier, in that users will be able to share non-ascii files much more easily over the net once this MIME standard gains more widespread support.) 8) Offers confidentiality for sensitive data/messages, via individual user-chosen encryption keywords for message text. 9) SNUUPM incorporates full adherence to the INTERNET's RFC 822, which relates to the Unix to Unix CoPy Protocol. This means that it will interface readily with ANY system running UUCP, including UPR2.CLU.NET running UNIX SunOS, and our own host concentrator node, niherst.gov.tt running WAFFLE v. 1.65 under MS-DOS v. 6.0. 10)The entire suite of programs, including source code in C is FREE, provided that simple guidelines are followed with respect to non- commercial usage, etc. 11) The author/programmer of the SNUUPM application program is an INTERNET Domain co-ordinator, and is available on the net for help and advice. (N.B. Since Feb 1992 when NIHERST first started using WAFFLE, we have never had any response from the programmer when we contacted him via emial with queries regarding WAFFLE. SNUUPM could hardly do worse.) Now, I would very much like to see the end of WAFFLE on our system, but I think I'll need to keep using it for it's BBS capabilities, for persons who either cannot or will not use the SNUUPM batch mode of sending messages. (Masochists, like the people looking for their UNIX gurus, I presume!) However, I'd much prefer it if I could get SNUUPM to talk to WAFFLE on the SAME machine, so that I would be able to utilize its capabilities more fully. Here's my setup: I'm running WAFFLE on drive E: of a DELL 486DX/33 box, in a protected DOS window under MS-Windows 3.1. The BBS is on-line all day, and there's no other way I can do this under "DOS" (not that I know any other OS, either!) There are a couple of other offices that run WAFFLE on their machines, and call in to batch their outgoing messages; and there are a few users who call in via their "PROCOMM PLUS" or "TELIX" software (TELIX is an old favourite of mine. Do you know it? Is there a shareware version after v 3.11?). Now, both those types of users are going to be well served if they can be persuaded to switch to SNUUPM: that's no problem. My problem is a selfish one: how to get access to SNUUPM for MYSELF. Any suggestions? [personal message removed] Best regards. Lars. *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=* Lars Johnson | 4 Serpentine Place, | Tel 1-809 628-8523, NIHERST, | St. Clair, | 1-809 622-7879 /80. Documentation | Trinidad, W.I. | Fax 1-809 622-1589 Centre | lars_j@niherst.gov.tt ;-) | root@niherst.gov.tt :-| *=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=* From aau!aau.ru.ac.za!jbp@kudu.ru.ac.za Tue Jan 18 20:04:06 1994 Return-Path: <aau!aau.ru.ac.za!jbp@kudu.ru.ac.za> Received: from kudu.ru.ac.za by hippo.ru.ac.za (4.1/Hippo-02.06) id AA20973; Tue, 18 Jan 94 20:04:05+020 Received: from aau by kudu.ru.ac.za with uucp (Smail3.1.28.1 #1) id m0pMKmZ-000MjqC; Tue, 18 Jan 94 20:04 EET Message-Id: <m0pMKmZ-000MjqC@kudu.ru.ac.za> Received: from aau by aau.ru.ac.za (UUPC/extended 1.12b) with UUCP; Tue, 18 Jan 1994 17:30:44 EST From: <jbp@aau.ru.ac.za> To: ccml@hippo.ru.ac.za Date: Tue, 18 Jan 1994 17:30:35 Subject: Signons note Priority: normal X-Mailer: PMail v3.0 (R1) Status: RO Dear [name deleted] Greetings from the AAU Secretariat. We hope that the year 1994 will see electronic networking and communications proliferating in West and Central Africa through our collaborative efforts with you our member universities in the region. AAU's present email connection through the UUCP/Internet gateway at Rhodes University in South Africa is working remarkably well. We recovered from a serious problem with our own set-up and this has brought us useful experience with the SNUUPM package. Meanwhile, we have received information from Mike Lawrie to the effect that he has set up a UUCP/Internet signon account for you on the host machine at Rhodes. The information follows: [information removed] Thus your computer's full address will be <arcis.ru.ac.za>, and if you followed SNUUPM's default installation procedure, the primary (base) user will be "root" (ie. <root@arcis.ru.ac.za>). After the installation, you can register other users on the system by selecting option "A) Register a New User on SNUUPM" on the SNUUPM opening (main menu) screen. But for a start just use the "root" user-id. Following are a few instructions and tips which we feel will be helpful in getting you off to a good start. A. Installing SNUUPM i. You need to have the two SNUUPM installation diskettes which were distributed at the workshop with you. You need also have at least 4Mb of free space on your PC's hard disk. ii. Create a directory on your hard disk (say, MD \SNUUPM), change into this directory (CD SNUUPM), and copy (copy a:*.*) all the files on the SNUUPM diskettes into this directory. iii. ENTER pkunzip snuupm21.zip (This will create the following 3 files: SNUUPM21.DOC, SNUUPM.ZIP, and INSTALL.BAT. It is advised, and indeed essential, that you read at least the first 4 screenfuls of the SNUUPM21.DOC file before proceeding with the installation). iv. Edit your AUTOEXEC.BAT file to contain certain lines indicated in the SNUUPM21.DOC file. (Better to put these lines at the end of the AUTOEXEC.BAT file to avoid mixing it with its original contents). The author advises these lines be copied, as is, into your AUTOEXEC.BAT file to avoid making any typographical errors when re- typing. You can do this in any standard DOS text editor, or in a wordprocessor such as WordPerfect. But remember, in the case of WordPerfect 5.1, to save the final amended AUTOEXEC.BAT file as DOS (ASCII) Text [ie. Ctrl-F5, 1(Dos Text), , 1(Save)], and not as normal WP text. v. Include the following line at the end of your CONFIG.SYS file to make some amount of memory space available for environment variables - SNUUPM uses a lot of them. shell=c:\command.com /e:2048 /p vi. Re-boot so that all the changes/additions take effect. vii. Change back into the directory where you copied the SNUUPM files in step ii. above, and ENTER "install". [This next para applies to SNUUPM21 - SNUUPM22 has a "better" menu-controlled installation process. Mike Lawrie] >From this point onwards, the procedure is pretty automatic, but you will be required to answer a few questions about your system - your modem speed (baud rate) and type (very important, therefore look carefully through the list that SNUUPM displays screenful by screenful, jot down the name(s) that best describes/matches your modem type and speed, and type back this name when asked), password, domain name, etc. If your modem type is not listed, then you will need to create your own "modem.mdm" file into the \etc\uupc\ directory. And some level of expertise is required to do this successfully. At the end of the installation process, the system lists (on your screen) the options that you chose, and asks for your final confirmation. It is advised that you print and keep a copy of these settings using the "Print Screen" key on your keyboard. (Of course, a Ready printer should be attached to your PC in order to achieve this). The system also advises you to check on certain settings in certain files. But before tampering with any of these files, read the relevant portions in SNUUPM21.DOC file about the mentioned files or settings. You are now ready to start SNUUPM and to create and send/receive messages. Start SNUUPM by ENTERING "snuupm" at the DOS prompt. B. Creating a simple mail message in SNUUPM In the opening SNUUPM screen, observe that "User is root" is indicated right on top of the SNUUPM Main Menu options. i. Select 1) Mail ii. Select S: Send a mail message You are taken to the Send Message: Editing Screen, with your cursor at the "To: [ " line. iii. ENTER the e-mail address of your message's recipient. (In this case, pls. send a simple test message to me <jbp@aau.ru.ac.za> or to Mike Lawrie <ccml@hippo.ru.ac.za>). iv. The "Subj: " slot could be any text - the "theme" of your message. v. Type in a short test message, then press Ctrl-Enter. You will see the message being queued by "rmail" for onward forwarding through "kudu" to your intended recipient. C. Connecting to Kudu (Transmitting your message) i. Make sure that your modem is turned on, and that it is connected to your PC's serial (COM) port via a RS-232 (printer) cable. Ensure also that your International Direct Dialing (IDD) line (often attached to your fax machine) is plugged into the slot on your modem marked "TO LINE" not the one marked "TO PHONE". You are now all set to connect to kudu, and to transmit your message(s). ii. Return to the SNUUPM Main Menu screen by pressing Esc or Q(Quit) as many times as necessary. iii. Select option 4) Connect to the Mailserver, and watch your modem trying to talk to kudu's modem and to exchange messages with it. Dont give up if the first few trials report "BUSY" or some similar messages. Kudu's modem may be engaged or your local IDD line may also be trully "BUSY" and in heavy use at the time of your call. Neither mind any "funny" (machine language) characters that appear on your screen - they may all be due to "noise"/surges on the phone lines. There is, therefore, the need to persevere. If you receive "NO DIALTONE", it may be because your IDD line is not connected to your modem at all, or that it is connected to the "TO PHONE" slot instead of the "TO LINE" slot. As soon as you see: "arcis connected to kudu: at [your modem baud rate, eg. 2400 bps], g protocol, z grade" then you know that your system has been recognized by kudu, and you can send e-mail anywhere in the world! All the best, and please feel free to contact us again if you have any further questions. Yours sincerely, John Bart-Plange Technical Assistant PS: Please pardon me if the above "instructions" are seen as an "intrusion" and a belittling of your knowledge and expertise, but we wanted only to help. From garuda!garuda.indiacur.com!arvind@hustle.rahul.net Wed Jan 19 18:38:59 1994 Return-Path: <garuda!garuda.indiacur.com!arvind@hustle.rahul.net> Received: from hustle.rahul.net by hippo.ru.ac.za (4.1/Hippo-02.06) id AA10544; Wed, 19 Jan 94 18:38:52+020 Received: from garuda.UUCP by hustle.rahul.net with UUCP id AA15634 (5.67a8/IDA-1.5 for ccml@hippo.ru.ac.za); Wed, 19 Jan 1994 08:39:18 -0800 Message-Id: <199401191639.AA15634@hustle.rahul.net> Received: from garuda by garuda.indiacur.com (UUPC/extended 1.12b) with UUCP; Wed, 19 Jan 1994 08:38:13 GMT From: <arvind@garuda.indiacur.com> To: ccml@hippo.ru.ac.za Date: Wed, 19 Jan 1994 08:38:11 Subject: Suggestion Priority: normal X-Mailer: PMail v3.0 (R1a) Status: RO Hi Mike, Last night, I installed the same version of SNUUPM on four other machines which are networked to my PC mailserver machine. Here are some notes: 1. Well, first I had to modify a lot of SNUUPM configurations files by hand, changing the drive letter D:\SN (my %sndrive%) to the *network* drive letter K:\SN. Had I chosen K: at the time of installation, it would have saved me a lot of work later. Is this something you want to suggest in the documentation? 2. Next, I had to modify the CONFIG.SYS, AUTOEXEC.BAT, and SYSTEM.INI file on four other machines as follows: CONFIG.SYS SHELL=C:\DOS\COMMAND.COM C:\DOS /E:2048 /P AUTOEXEC.BAT I found it easier to create one common file K:\SN\USR\LIB\SNUUPM\INITENV.BAT which contains all your suggested commands and then to insert the following line in AUTOEXEC.BAT files of all other computers *after* loading the network drivers so that the K:\SN drive is defined: CALL K:\SN\USR\LIB\SNUUPM\INITENV.BAT This work very well. The CALL does modify the environment before it ends. SYSTEM.INI To make SNUUPM-in-a-window work, I had to patch the Windows SYSTEM.INI file on all computers so that the appropriate line in there read 2048 instead of 512: CommandEnvSize=2048 3. Next I reboot all machines with the new configurations. 4. If you try to run SNUUPM at the same time on more than one machine, you get a "sharing violation error". The solution is to mark all the files in K:\SN\USR\LIB\SNUUPM as read-only. This seems to make it work. I haven't run into any problems as a result -- yet! Perhaps you can advise as to which specific files should *not* be read- only. 5. After this, I go into Windows, define a new program manager item using your SNUUPM.PIF file, and I'm all set! Works like a charm. One suggestion I have for the SNUUPM.BAT file: If the user doesn't specify a name in %1 argument, and PMUSER is not defined, it prints an error msg and refuses to run. This is good. What would be better is if it then asks for your user name and then runs. From Windows, it asks for a "parameter" which is not terribly obviously to new users of SNUUPM. Just a thought. [This suggestion has been incorporated into SNUUPM23. Mike Lawrie] Another question: Is there some way to configure UUPC so it would connect to the remote mailserver automatically, say, every half-hour? Right now, I have to initiate that on my own, and my unix machine will not initiate a call on its own (their policy/terms). [The answer is to look at the UUCP documentation for UUPOLL. Mike Lawrie] Many, many thanks for a fine package. The more I use it, the better it feels. Thanks for the online support, too. Without it, it would have taken me much longer. - Arvind Kumar P.S. Do I need to say that I am composing this in SNUUPM on my PC? In minutes, it shall make its way from my PC to South Africa, halfway around the globe! ii cccc India Currents arvind@indiacur.com ii cc The Complete Indian American Magazine * Since 1987 ii cc P.O. Box 21285 Phone: (408) 274-6966 ii cccc San Jose, CA 95151-1285 Fax: (408) 274-2733 ------------------------------------------------------------------------ Key to the Configuration ------------------------ 1. CONFIG.SYS, AUTOEXEC.BAT =========================== The SNUUPM system makes extensive use of environment variables. Some have to be preset in the AUTOEXEC.BAT file, others are used as and when the system is working. Thus you have to allow for far more than the default environment space. The additions to AUTOEXEC.BAT, as described under QUICKSTART, cause your PC to boot up ready to be used by user "root". While using "root" as you personal user-id is not good Unix practice, it gets you going very simply and is perfectly legit. The file c:\usr\lib\snuupm\utl\main.mnu controls the options that are available to users - root is permitted to dial to other systems, and to run the user registration operations. It is a simple matter to alter MAIN.MNU to allow all users to do all things. 2. SNUUPM1.BAT ============== Start the system by typing snuupm or snuupm USER-ID This will invoke the SNUUPM.BAT file that you have installed in a directory in the search path, and this in turn invokes SNUUPM1.BAT. SNUUPM1.BAT creates three environment variables that are unique to the user-id. This allows many users to use the same PC, as long as they accept that MSDOS provides no protection against one user prying into the files of another. There is no password protection, although PMAIL does allow messages to be encrypted. SNUUPM1.BAT file needs no editing, but you need to ensure that you have first created the necessary files/directories for other users. (The ADDUSER commands makes this a simple procedure). If you have configured AUTOEXEC.BAT according to the QUICKSTART description, the system will default to using the user-id "root". You might prefer to modify your autoexec.bat file once you have registered a "better" user-id for yourself. If you do this, then you might like to give yourself the privileges that "root" enjoys, so edit a few lines in c:\usr\lib\snuupm\utl\main.mnu The SNUUPM command sets these environment variables:- 2.1. uupcusrrc=c:\usr\USER-ID\USER-ID.rc -------------- 2.2. snewsrc=c:\usr\USER-ID\snews.rc ------------ 2.3. pmuser=USER-ID ----------- These three are used by PMAIL to identify one user from another. 3. UUPCSYSRC (c:\etc\uupc\uupc.rc) ============ This environment variable is defined in AUTOEXEC.BAT. The file that it points to, viz uupc.rc, must have the following configuration in order to dovetail the UUPC system to PMAIL and SNEWS. 3.1. confdir=c:\etc\uupc ------------ This points to the directory that contains the UUPC files HOSTPATH, PASSWD, PERMISSN, SYTEMS and the MODEM.MDM file. 3.2. maildir=c:\usr\spool\mail ------------ This is where the UUPC program RMAIL will store mail for each user-id. The name of this directory must dovetail with the setting of PMAIL's "New mailbox" and "New mail path" parameters. Use PCONFIG's "Standalone configuration" and "create a User-defined gateway" options to set the PMAIL parameters. 3.3. newsdir=c:\usr\spool\news\incoming ------------ This is where the UUPC program RNEWS leaves batched news. The SNEWS UNBATCH program expects to find it in the directory set by NEWSDIR. For whatever reason, the setting of UUPCNEWS in AUTOEXEC.BAT must differ from the setting of this NEWSDIR value. 3.4. spooldir=c:\usr\spool ------------- This names the directory that holds the log files of the UUPC programs. You need to examine/shorten/delete these files from time to time. The log files are useful during debugging, and could be used as the basis for monitoring the usage of mail/news. 3.5. rmail, rnews ----------------- These parameters point to the location of the RMAIL.EXE and RNEWS.EXE program files. 3.6. Organisation ----------------- Use something sensible. 3.7. Uncompress --------------- Set to "c:\usr\lib\snuupm\compress -d %s". Note that this COMPRESS.EXE is not the same as a "normal" DOS COMPRESS.EXE program, due to the fact that news is batched according to Unix standards of end of line sequences. 3.8. Inmodem ------------ Must be MODEM, which is a file in the c:\etc\uupc\ directory. This will be used to drive the modem for incoming UUCICO calls. This matches the word "modem" in c:\etc\uupc\systems. This is a copied-and-renamed file from the collection of .MDM files that are extracted during the installation of SNUUPM. 3.9. Mailserv ------------- The name of the host computer that provides you with email connectivity. 3.10. Nodename -------------- The name of your computer. Less that 8 characters in size, and must not contain "funny" characters like ".". For example, nodename=c119 defines a legitimate nodename. Liaise with the sysop at the site of your Mailserv machine in order to match. The nodename value also appears in the c:\etc\uupc\systems file. 3.11. Domain ------------ The fully qualified domain name of your host. For example, domain=c119.ru.ac.za or domain=c119.uucp. THIS IS CRITCAL, IF YOU DON'T KNOW WHAT TO PUT HERE, ASK SOMEONE WHO DOES KNOW! 3.12. Other ----------- Other settings follow a Unix style of setting - ie the directory C:\USR\SPOOL is used extensively. Be wary of what parameters that you remove - there is some "real dirty" parsing and counting of the parameter file by some of these programs (of the SNEWS suite), and the error messages are not very helpful. 4. UUPCNEWS (c:\usr\spool\news) =========== This environment variable is defined in AUTOEXEC.BAT. The directory to which it points contains the following:- 4.1. Newsbase ------------- the NEWSBASE directory, where the news items are stored in a form ready to read by the SNEWS program 4.2. Active newsgroups ---------------------- the ACTIVE file, which links the names of the newsgroups to the contents of the NEWSBASE directory 4.3. .NRC files --------------- the users' .NRC file (ie a file per user), holding the information as to what newsgroups have been read. 4.4 The HISTORY file -------------------- Tracks the delivery of news. SNEWS won't run without it. 4.5 The USER-ID.NRC files ------------------------- There is one per user-id, which contains the current pointers for the particular user-id. 4.6. INCOMING Directory ----------------------- The UUPC.RC parameter NEWSDIR is set to the setting of the uupcnews environment variable followed by "\INCOMING". This is used to hold the unbatched news items. 5. UUPCUSRRC (c:\usr\USER-ID\USER-ID.rc) ============ The file pointed to by this environment variable contains the UUPC setups that are unique to USER-ID. 5.1. Name --------- Your personal name. Not critical. 5.2. Mailbox ------------ Your user-id. Absolutely critical, this must dovetail with several other parameter settings. DOUBLE CHECK THAT YOU HAVE THIS CORRECT if your are bold enough to attempt to change things at a low level. 5.3. Home --------- Set this to c:\usr\USER-ID for safety sake. Probably not used by the system (it is used by the MAIL process of UUPC). 5.4. Signature -------------- Not critical. Point it to the signature file that you set up for PMAIL, ie c:\usr\USER-ID\mbox\inetsig.pms. In general, limit your signature to be no more than 4 lines because there are a goodly number of folk on the networks who pay high rates for telephone calls and you will be causing them some expense each time that your signature is mailed to them at the end of your messages. 5.5. Editor ----------- This is the name of your favourite ASCII editor - it must produce ordinary ASCII codes, not the fancy stuff of a word-processor. Add a "%s" after the name of the editor, so that the correct filename will be substituted on the command line. For example:- Editor=c:\bin\vi.exe %s 5.6. Aliases ------------ This is a list of aliases used by the MAIL (not PMAIL) program of UUPC. The contents are a series of single lines with an alias name, gap, and the address to be used when MAILing to that alias. Probably not of much use. 6. SNEWSRC (c:\usr\USER-ID\snews.rc) ---------- The file pointed to by this environment variable contains the SNEWS setups that are unique to USER-ID. 6.1. Name, Mailbox, Home, Signature, Editor, Aliases, Organization. ------------------------------------------------------------------ Set these EXACTLY as you have done for your USER-ID.rc file. SNEWS will make use of them. Spell "Organization" with a "z" not an "s". 7. PCONFIG, PMAIL, BURST and UNBATCH ==================================== The parameter values of these must dovetail EXACTLY with the rest of the package, or mail and/or news will not flow. Incoming mail and news are processed like this:- a) UUCICO receives uucp-style files into c:\usr\spool\kudu\{D,X} This filename is made up of UUPCSYSRC(spooldir) \ Name of system that is dialed D or X as required by the uucp process b) UUXQT processes the mail files, and leaves them in the file c:\usr\spool\mail\USER-ID, in a uucp format. The RMAIL program is run by UUXQT to do this work. This filename is made up of UUPCSYSRC(maildir) \ UUPCUSRRC(mailbox) News is deposited in the c:\usr\spool\news\incoming directory, and would normally be in a batched format. RNEWS is run by UUXQT to do this work. c) BURST transfers the mail files output by UUXQT/RMAIL into the PMAIL 'new mail' directory c:\usr\USER-ID\mail\. It does this by running a program UU2PM under control of the file c:\pmail\burst.bat. The parameters that UU2PM takes look like this:- uu2pm -d <source-file> <destination-file> The <source-file> is whatever file appears in the directory \usr\spool\mail\ The <destination-file> is stored under the appropriate USER-ID according to the address of the message, and looks like \usr\USER-ID\mail\uuXXXXXX.CNM It is CRITICAL that <source-file> of UU2PM matches the output file of UUXQT, and that the <destination-file> of UU2PM matches the directory names that are configured into PMAIL and into the c:\usr\lib\snuupm\burst.bat file. d) UNBATCH moves the INCOMING news into the NEWSBASE directory, and sets up the necessary index files that are used by the SNEWS newsreader. 7.1. PCONFIG ------------ The dovetailing of PMAIL into the UUPC style of working described above is done by running PCONFIG, and removing the DEFAULT.PM file of PMAIL, if indeed it exists. The first PCONFIG menu offers three options, viz:- 7.1.1. Standalone configuration -------------------------------- The following are set and need no changing:- Home mailbox ~%sndrive%\usr\~8\mbox New mailbox ~%sndrive%\usr\~8\mail Async gateway? N The home mailbox can be anything that is not yet used, but it is essential that the new mailbox matches the directory of the <destination-file> used in the UU2PM run. 7.1.2. Create a User-defined gateway ------------------------------------ Select the (only) defined gateway, viz UUPC, and you will find (and must leave) this setting:- New mail path ~%sndrive%\usr\~8\mail This is the same as the "new mailbox" of the standalone configuration of PMAIL. These values should all be preset in the disk issued by Rhodes University, so you will have nothing to do unless you are changing the way that the three separate packages dovetail together. Some of the settings have evolved as SNUUPM has matured, and at version 22 of SNUUPM look like this:- New mail search path *.cnm Run for outgoing mail snu_fpm ~c | rmail ~t Reply address format ~p <~8@~%snu_hd%> 8. Modem file, Systems file =========================== Here you might need to have some guru advice, and this cannot be obtained from a document such as this. You need to select or create a suitable .MDM file, and to store this file in c:\etc\uupc\modem.mdm. There is the Rhodes University's collection of .MDM files in the c:\usr\lib\snuupm\mdm directory and there are a further number included with the UUPC package, in one of the .ZIP files. You might well have to modify any .MDM as necessary (eg to use COM1 or COM2 and/or other options), and copy it to c:\etc\uupc\modem.mdm. There is further advice on configuring the .MDM and SYSTEMS files in the SAMPLE.MDM file that is part of the UUPC package. Note, however, that the .MDM file must be called "c:\etc\uupc\modem.mdm" or you will have to alter some well-hidden configuration parameters. You need to edit the c:\etc\uupc\systems file to have the correct dialing sequence, username and password to allow your system to exchange mail with a remote uucp host. 9. Essential Directories and Files ================================== Certain directories and files need to be created in order for the programs to run. In spite of what the documentation of the individual packages say, not all of these are created automatically by the programs of those packages, so don't be lulled into a false sense of security. All the necessary directories that SNUUPM uses are created by SNUUPM. 9.1. Directories ---------------- The empty directories that the pkunzip -d process does not create are created by the INSTALL.BAT file. 9.2. Files ---------- Create these files, if somehow you have destroyed them:- \etc\uupc\hostpath A single line "# Nothing here!" is fine. \usr\spool\news\history A single line with a space will do. 10. General Maintenance ======================= 10.1. Registering users ----------------------- The commands ADDUSER and RMUSER simplify this process. The following directories are made by ADDUSER:- c:\usr\USER-ID\mail c:\usr\USER-ID\mbox The following files are created by ADDUSER:- c:\usr\USER-ID\USER-ID.rc c:\usr\USER-ID\snews.rc c:\usr\USER-ID\aliases.txt The contents of these files are described above, under UUPCUSRRC and SNEWSRC. An entry needs to be made in the c:\etc\uupc\passwd file:- USER-ID:*:::USER'S REAL NAME 10.2. Newsgroups ---------------- Edit the file c:\usr\lib\snuupm\active.bat to cause the ADDGROUP program to add newsgroups to the list of newsgroups that you wish to read, and then execute this ACTIVE.BAT file. Use the RMGROUP program to remove any groups that you no longer wish to read, and edit them out of the ACTIVE.BAT file. Understand, however, that in order to get news, and to be net.sociable, your news configuration and that of your newsfeed host must match. From time to time, run the expire program to remove old news groups, or run the iexpire program to do this interactively. Specify on the command line the age in days of the news that can be expired. The simple way to do this is to choose the appropriate option from the SNUUPM main menu. 10.3. Log files --------------- Periodically tidy up (eg delete and/or edit/truncate) the *.LOG files in the directory c:\usr\spool\ -- this is a main menu option. 11. Operation ============= The whole system should be run from either the SNUUPM command. ie:- snuupm A menu is displayed, and you select whichever operation you want by point-and-shoot, or by function key. You can set your system into receive mode (ie to allow other uucp hosts to call it) by selecting the "Listen for incoming calls" option. Use Ctl-C or Ctl-Break to interrupt the listening process. 12. Copyright ============= NONE OF THE COMPONENT PARTS OF SNUUPM, NOR THE ENTIRE PACKAGE, MAY BE SOLD. FOR COMMERCIAL USE, CONTACT THE AUTHORS OF EACH PACKAGE AND MAKE WHATEVER ARRANGEMENTS EACH AUTHOR REQUIRES. 12.1. UU2PM.EXE --------------- The UU2PM.EXE file is freely distributable, thanks to ideas from Paul Nash <paul@frcs.alt.za>. The current (SNUUPM22) production release was written by the author of SNUUPM, do what you will with the code at your own risk. 12.2. UUPC 1.12 --------------- The file UPC12BAD.ZIP contains the licensing information in the file LICENSE.PRN. This is too lengthy to include here, and difficult to summarise, so the specific file should be consulted. It seems to be clear, however, that use of the package in a non-commercial environment and in an unchanged form is well within the scope of the license, and distribution of the package should include the source code. The SNUUPM distribution does not include the UUPC package or any component of that package. 12.3 PMAIL v3.01 ---------------- The PMAIL program GUIDE.EXE displays the following text:- Pegasus Mail is an electronic mail system for use with Novell Netware (versions 2.15A and later): it is a fully-fledged mailer, one of its more unusual characteristics being that it is free - not shareware, but free. You can use it without charge, restriction or obligation on as many servers as you wish. I do sell manuals for the porgram, in order to support development costs, but manual purchases are strictly optional. An order form for manuals is provided in this guide - please print it out and attacht it to your order or cheque if you place an order. ...more... The PMAIL author can be contacted at david@pmail.gen.nz (preferred) or at david@otago.ac.nz. Do NOT distribute PMAIL except as the complete PMAIL3xx.ZIP file. The SNUUPM distribution does not include files from the PMAIL package, but does include files created by this package for the UUPC<->PMAIL gateway. These files were developed by the author of SNUUPM, do what you will with them at your own risk. 12.4. SNEWS191 -------------- Here is an extract from the file SNEWS.DOC found in SNEWS191.ZIP. You are referred to that document for more details:- >CAVEATS AND COPYRIGHT >===================== > > Version 1.12 of this software is copyright (1991) by John McCombs, > Christchurch, New Zealand <john@ahuriri.gen.nz> > > Version 1.90 is copyright 1992 by Michael Studte/John Dennis (Shinohara > Industries) > > Version 1.91 is copyright 1993 by Daniel Fandrich <dan@fch.wimsey.bc.ca> > or <72365.306@compuserve.com> (some portions are copyright > 1992 by Kai Uwe Rommel <rommel@jonas.bofe.sub.org> or > <rommel@informatik.tu-muenchen.de>, and copyright 1985, > 1989 by Bill Davidsen) > > This package is free software, but NOT public domain; you can > redistribute it and/or modify it under the terms of the GNU > General Public License, version 1, as published by the Free Software > Foundation. > > This program is distributed in the hope that it will be useful, > but WITHOUT ANY WARRANTY; without even the implied warranty of > MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > GNU General Public License for more details. > > See the file COPYING, which contains a copy of the GNU General > Public License. > > The compress program and documentation included with the SNews > distribution were not written by the SNews authors and are not a formal > part of SNews. The are part of the public domain compress ported by > Donald J. Gloistein. At the request of the author of SNEWS, when the SNUUPM package was being developed, this text is included:- "Portions of this software were derived from SNews, which is copyright by John McCombs <john@ahuriri.gen.nz>, and are included by permission of the author. NOTE: This version of SNews is not distributed under the GNU Public Licence. No warranty is offered by John McCombs in respect to this software and no liability is accepted for the consequences of its use." This note is still included even though SNEWS is not distrbuted as part of SNUUPM. 12.5. ASKENV.EXE ---------------- Written by T Salmi and released for non-commercial, non-institutional and non-profit use. <ts@uwasa.fi>. 12.6. DOUGMENU Version 1.68 --------------------------- Taken from the DOUGMENU.DOC file:- "TERMS OF USE for DougMenu v1.67, released on July 31, 1992 "Revised August 2, 1992 "This program is a freeware product and so should be distributed at no charge, besides that of a reasonable media fee, if applicable. "No charge should ever be made for the program itself, or any program using source code from this program. "While users are free to modify DougMenu for their own use, modified versions of DougMenu are not to be distributed out side of the business or organization which created or commissioned them. The DougMenu package should always be distributed complete with source and unaltered except when being installed for use at multiple sites within a business or organization. Then it is permitted to install only the files deemed necessary to use the menu system as long as one complete copy is maintained by the business or organization. "If you have suggestion concerning the further development of DougMenu, please contact the author concerning any changes you suggest to the official version. "A copy of the most recent version of DougMenu can be mailed to you for US $10. Printed Documentation is available for US $25. US $5 surcharge for postage outside North America. One year of customer support via electronic mail is available for US $35. "Send requests, comments, or orders to: "Douglas A. Bell 2585 Euclid Heights Blvd., APT #1 Cleveland, Ohio 44106 USA "-or- "dab6@po.cwru.edu "THERE IS NO WARRANTY, EXPRESSED OR IMPLIED, FOR DOUGMENU. WHILE THE AUTHOR HAS ATTEMPTED TO PRODUCE AN ERROR FREE PROGRAM, THE AUTHOR ASSUMES NO RESPONSIBILITY FOR ANY DAMAGE THAT THIS PROGRAM MIGHT CAUSE. "(c) Copyright 1992" 13. Mailserver, Hostname, Domain, User-id, Baud Rate ---------------------------------------------------- The mailserver name "kudu", the hostname "c119", the domain "ru.ac.za" and the user-id "root" are what the author of SNUUPM uses. You will need to alter these to suit your particular circumstances. Adding new mailservers and user-ids to your PC involves making a few directories as well - SNUUPM provides a simple interface for adding new users, but not for adding new mailservers so you are "on your own" if you attempt this (it has been done). Changing your modem baud rate will require several files to be changed, it is probably best to do this by a re-installation of the package. The INSTALL.BAT and INSTALL.MNU files make use of install-time environment variables to set the values that the user specifies interactively, and this is really the easiest way to do things and to get them correct. 13.1. Mailserver ---------------- 13.1.1. Directories to be made ------------------------------ c:\usr\spool\MAILSERVER c:\usr\spool\MAILSERVER\c c:\usr\spool\MAILSERVER\d c:\usr\spool\MAILSERVER\x 13.1.2. Files to be edited -------------------------- c:\usr\lib\snuupm\callin.bat c:\usr\lib\snuupm\callout.bat c:\etc\uupc\passwd c:\etc\uupc\permissn c:\etc\uupc\systems 13.2. Hostname -------------- Files to be edited:- c:\etc\uupc\systems c:\usr\uupc\uupc.rc 13.3. Domain ------------ File to be edited:- c:\etc\uupc\uupc.rc 13.4. User-id (default=root) ------------- Type adduser (or better still, select the "Register a new user" option from the SNUUPM menu) which will prompt you for the user-id (eg ccml, or mike, or anything that is a valid DOS filename without an extension), and then for the person's name (eg Mike Lawrie). The various files will be created for this new user. Apart from making an entry in c:\etc\uupc\passwd, all files and directories for the user are created within the directory c:\usr\USER-ID, so removing a user involves removing files and directories within this directory. 13.5. Baud Rate --------------- The baud rate has to be configured into the c:\etc\uupc\systems and c:\etc\uupc\modem.mdm files. The fourth field of the systems file and the Inspeed parameter of the modem.mdm file must match the baud rate of the modem. 14. Removing the Package ------------------------ Deregister user-ids with the RMUSER command. Remove the contents of the directories c:\etc\uupc c:\usr\lib\snuupm c:\usr\root c:\usr\spool and undo changes to your AUTOEXEC.BAT and CONFIG.SYS files. Simple but sad :-( 15. Clashes ----------- The PMAIL program was originally designed to run on a Novell network. So, if you PC is on such a network, the chances are that the IPX and NETX programs will clash with the snuupm configuration. Too bad, until someone provides a workaround. ------------------------------------------------------------------ Please send comments and corrections regarding this document to Mike Lawrie <ccml@hippo.ru.ac.za>. This software is supplied on an "as is" basis, and there are no guarrantees regarding fitness of purpose, reliability, workability or anything of that nature. Under no conditions may it be sold. The snuupm component may be distributed only for the reasonable cost of distribution. Commercial use is prohibited. ------------------------------------------------------------------