CONNplex: A multi-user Personal Message and Conferencing System Introduction: About October of 1987, here in Central Connecticut, it became clear the the use of NET/ROM on packet frequencies was inconsistant with local multi-member conferences that were occuring. These conferences were done using UNPROTO mode so that everybody in the group could see the text from all members. There were some problems in the begining, in particular packet crashes resulting in text missing on some screens. Activity from PBBS stations would clog the screens. When NET-ROM came along, The problem got worse. NET/ROM, for the uninitiated, is a system to network stations together in a form of virtual pipe. You construct the pipe in segments from point A to point B and whatever you put into the pipe comes out the other end. Simple explanation but good enough for now. The problem with NET/ROM is that is uses binary information to signal between segments, or nodes, of the pipe. These signal are interpreted by terminals MONitoring the frequency as commands to clear the screen, change colors, beep, display weird characters, etc. Clearly, something had to be done. The only way to solve all the problems was to establish one station with a TNC and a computer to accept transmissions from each member and retransmit them addressed to all other members. The answer was simple. Using my Amiga I could run the software all the time in the background. Well, like most simple projects, it grew. Before long I installed the ability to store mail to each user. Errors were handled more gracefully. The ability to upload/download files was added. It GREW to more than what you have today. The system is fairly simple to install and operate. If you have a hard disk I suggest you install it there as it's own directory. ASSIGN CONNplex: to in your Startup-sequence. After you boot the system, PLAY with it. This is the best way to learn it's abilities and pitfalls. Try reading the HELP files. There is very little maintainence required if you have a hard drive. Those without may want to keep track of the disk space and delete files (or users) that are old or infrequently used. A seperate document (CONNplex.tech) lightly touches how it all works along with care and feeding instructions. Unless activity is high I have found that no regular maintenence is required. The Features: - 10 simultaneous users (9 plus yourself) - Personal mail (you may list/read only mail to yourself, messages to ALL about flying saucers or ARRL DX bulletins are NOT, and may never be, supported). (Think I got a gripe ?) - A CONFERENCE command which virtually ties together all the keyboards of those who have entered the CONFERENCE area, introducing new members when they enter and indicating when they leave. - EXTENSIVE help files, with examples. - The ability to see who else may be on and send them a one line message. - It's free and it multi-tasks well. The Pitfalls: - Because of my setup (2 meg and a 20 meg harddrive) I have had only limited testing with a basic system. It does work, however. - Without installing on a hard drive, It is slower (and noisier) than one would expect. - It uses CPU cycles when it is "sleeping". This is because of all the hooks I removed to get a decent product I could support. My system has many more features but I wish to add them after I am sure that the installation base can be supported. I dont want to embaress myself. Directions (such as they are) for installing CONNplex: Actual installation: A. Edit the file CONNplex:SYSOP and replace the text with either your call or your first name. This is the text string that the system will use to identify you as the sysop. You will be connected (logged in) by this ID. I suggest you use your callsign. B. Edit the file s:CONNplex.tnc. This file sets up the TNC (TAPR-2 and clones) for proper operation. In particular, be sure to change MYCALL to your call. DO NOT change AUtolf, CR, or any of the commands that set particular char- acters for transmiting packets, etc. You may adjust parameters such as PACTIME, DWAIT, etc. These are set up for operation here in CT and are some- what agressive. C. Either upload this file to the TNC using a terminal program or enter the parameters to the TNC directly. SET THE TNC FOR 1200 BAUD !!!! D. CONNplex may be run one of two ways: - under Amiga Basic (recommended) - as a stand-alone executable task (um, er, well, less recommended but less of a drain on your system and I wish to get comments on it). To run as a stand-alone task: Insert the disk and type, from CLI, Run CONNplex:CONNplex To run from Amiga Basic: Start Amiga Basic as you normally would. If you do it from CLI I suggest you RUN it so you still have the CLI available. Pull down the Projects menu and select OPEN. Enter CONNplex:BOOT.MSB into the requester and press RETURN. The system should boot itself from this point. You should shortly see the message "CONNplex booted...". It should be followed by some text from your tnc. If not, check your tnc to be sure it is on and set for 1200 baud. To Connect yourself to the system select CONNplex as the active window. Press ESCape followed by a RETURN. You should get text indicating the system is logging you in. I suggest that at the prompt you enter the command: Name and then begin to play around by typing HELP and then all it's permutations. Send yourself mail, list it, read it and delete it. Send a MEMO to yourself then go to CLI and type it from CONNplex:Memos Notes: Commands may be abreviated to a unique form. For example, CONFERENCE may be just C. For a case like READ and RUN, sending just an "R" will parse the READ command (if I remember right) because READ is a more frequent operation. The MEMO command is virtually the same as a letter, in this release. At my station I have additional code to spool the memos to a printer and prompt me that memos are waiting when I sit at the keyboard. I can not support these operations at your station without knowing your set-up. I suggest you use MEMOs as a direct line from the users to you. You can check for them by doing a DIR on CONNplex:MEMOS. Each file will be from a different station, identified by callsign. There are MANY hooks in this release. Some do something and some are just for future expansion. Again, some do things at MY station that I cant set up for everybody, just yet. If you find a hook, enjoy it if it does something. Future expansions: I am working on several "database" applications to hook in (callbook, etc). Here at WA1PTC users can run some BASIC, FORTRAN or script files that they have created and compiled on my system for themselves. If this proves successfull then I will release that version with some applications. I am looking at the question of Mail forwarding. I, personally, am not interested in having forwarding to/from my station. However if enough people beat me over the head, I'll try to implement it. Future releases will support selective baud rates, non-disk-spooled I/O, and the ability to edit messages that the system produces. A Request: Please advise me if you decide to use CONNplex at your station. Send a notice that you are using it, along with comments/suggestions to: Mike Staines P.O. Box 6029 Wallingford, CT 06492-0088 or: WA1PTC @ N1API-4 (path via W1AW-4) IF YOU ABSOLUTELY CANNOT GET THE SYSTEM TO PERFORM (Boot, etc) then give me a call at (203) 269-4603 (answering machine) I hope that you enjoy this program as much as I have had writing it. The shell is in place to show what a powerfull machine the AMIGA is. Tell me how to improve this to make the power of Amy available to all (via packet). 73, Mike Staines (out-of-the-closet Amy phreak)