Note: BA01 See the UPDATE.TXT file for additional changes, bug fixes, ect... Install Instruction of this version of Citadel; 1) cit_messages.sys This file contains the messages used by Citadel. about 90% of the messages are in this file. You can customize the messages. The file included has cit:helps as the location of several help files so check to see that everything is correct for your system. The messages with an "@" are references to files that must be on your system(they should be included here or in the helps). This file goes in the #MSGAREA directory. The file format is included as comments in this file. All the extra files in the archive named *.MSG also go in this area. On my BBS, the area is called "CIT:GENERAL/", this directory contains these files. This means you will find references to: "@cit:general/filename" You must customize your BBS message file or define CIT:GENERAL and put the files there. If you are updating from a previous version, there is a file called MESSAGE.UPDATES that you need to look at to see the changes that were made from the .Q02 version. The file in the archive Message_Changes is a list of updates since the last release. If you have customized your own message file, then you want to add the additions and check your file for these updates. 2) BADNAMES.SYS and BADPASSWORDS.SYS are files that are checked when a user is creating their account. You may use the files included in the archive or make your own. If you do not put these files in the room area, Citadel will not check User names and Password for validity except to make sure the password is at leas 5 chars long and not a duplicate of someone elses. These work the same way BADWORDS.SYS does. Also is the BADPEOPLE.SYS capability. This file also goes in the ROOMAREA and is used to supress messages from any particular user, in any particular room, or from any particular system. There are three field, one line per entry. You do not need this file, it is optional. It kills any message that matches the room, name, and system specified. A "*" can be used for all. You could for example supress all message from a particular user in a room, from any system, if the user is TOM, the ROOM COMPUTER, you could have: TOM SMITH,COMPUTER,* The fields are separated by commas. An entry of "*,*,*" is illegal and will generate an error(after all why net at all if your going to kill all message). If TOM SMITH is a real pain and you want to suppress all messages in all rooms, change "COMPUTER" to "*" to get an entry like: TOM SMITH,*,* This will only affect networked messages you recieve! Any messages entered on your system will be accepted normally. Note: This is pure censorship, it deletes the messages totally and no other system `downstream' network wise will see the messages or even have the option to see them, they are deleted from your system. To supress them on only your system turned out to be too much of a problem in the software, live with it... I do not recommend using it although, a certain user that was a real pain from a local system did have this invoked(a test, but he deserved it...) At one point, some systems were fighting in a room, several people were involved and you could have an entry like: *,BBS LIST,BAD GUYS BBS That would censor all their messages, no matter what the content. I came very close to doing this at one point... This is an option, use it only as a last resort... If the messages really are not a problem, ignore them, don't censor them... 3) The VORTEX checking is on by default. If you do not wish it, you must use the "-vortex" option on the command line. If you have the "+vortex" it will have no effect. 4) +netlog and +netdebug are now more effective and if you do not specify either one, Citadel will be very silent during a net session. +netdebug messages will give alot more detail and if you want +netdebug, you should also specify +netlog. Note: not specifying at least +netlog will result in some messages appearing in debug.sys by default. This will change in later versions. In addition, +CID or +RESULTS on the command line will allow you to record the text send from the modem during the baud rate recognition. The +CID will record after the first RING is seen, the +RESULTS will record all text lines. The idea of these options is to collect caller id info(+CID) and for debuging all modem text(+RESULTS). The information will go into the auditarea in debug.sys. 5) parameters for QWK parameters: #QWKWORKAREA "" Work directory for temporary files. #QWKFILEAREA "" Where all user data files are saved. #QWKMAXROOM This parameter defines the maximum rooms that will be scanned for messages for a single packet. If you set this to say 100 and have 200 rooms, then a user can only collect 100 rooms with messages at a time. This sets the maximum, users can set a lower number if they desired. #QWKMAXPACKET 10000 This parameter defines the manimum number of messages that can be collected at one time. The user can set a smaller limit if desired. #QWKNAME "STRING" This parameter defines the name of the QWK packet. In this example, the downloaded packet would be called "STRING.QWK". #QWKLOCATION "MEDFORD, NJ" This parameter defines the location of the BBS(displayed by the QWK reader). 6) parameter for biography #BIOAREA "" This specifies the directory you wish to use for the Biographies that users enter. The default will be the home area so it is a good idea to specify" #BIOAREA "bio" to get the current default. 7) Vortex checking. Citadel automatically checks for vortexed networked messages. It will reject any message originating on your BBS(if it returns in a net session), or any message it has already seen. There were improvements in this checking and you will need to go into the #NETAREA and delete all the *.vex and, v*.sys files. Citadel will create a sub-directory called vortex and put all its files there. there will be a slight increase in disk usage. To eliminate this checking, specify -vortex on the command line. There is a new structure for the vortex files, each room gets a file in the #NETAREA vortex directory. Delete all the files in this area to use this version. 8) There is extensive support for email networking. To make use of this feature, you must grab the archive Citadel_Email_Networking.lha 9) date format parameter: #default-date-format "STANDARD" for dates of the form 100 Jan01 #default-date-format "SHORT" for dates of the form 00 Jan01 #default-date-format "LONG" for dates of the form 2000 Jan01 This option allows you to specify which format you want by default. This is optional, STANDARD is what you get if you do not specify it. ***Legal-ease*** Citadel 68K and Amiga Citadel are trademarks of this Citadel BBS program and may not be used for other variants. This software is FREEWARE and may not be distributed on any system that claims a copyright. If you have specific questions about the use and rights to this software, contact me on The Amiga Zone (609) 953-8159. ***This product is not for resale***. You may not include Citadel or Citadel related files in any collection sold for a profit without my express written permission. Source for the Amiga Citadel is 100% public domain and available for downloading. If someone sold you a copy of this program, please let me know, it is not for sale. The only exception is the Aminet and Fred Fish CD collections. Those collections may re-distribute this program and the related utilities. No commercial collection may distribute this program nor may any system attempt to copyright these works just because someone uploaded it to that system. If other software collections would like to include Citadel 68K distributions, please contact me, My only wish is that the very latest is what is distributed. Internet news groups like Alt.source, comp.amiga.source and anything similar also have permission to post these archives. There are utilities, See the archive listing. If you are starting from scratch and have never run a Citadel before. You need to grab the support and help files. These files are on the C86 Test system and the Amiga Zone. Please download them from there. Start with the latest version of Citadel 68K. Read the 68K.man file. In the very near future there will be a full AmigaGuide set of documentation along with a re-organized Citadel 68K manual. Until then, read the existing docs. The AmigaGuide version of the docs(partially done) is available for you to download. Look in the Citadel Documentation room on my BBS or doc archive where you found this. I am maintaining the amiga guide files and will eventually produce an HTML version which will be linked to my WEB page which is http://www.k2nesoft.com/~apreston If you are interested in doors, The Amiga Zone has several that will run with Citadel 68K. Any CLI based program will be able to run as a door so long as it uses only standard I/O(i.e. getchar(), printf, ect.). Doors are available in the Citadel Doors room. If you have a bug to report, Please use the Citadel 68K room and prefix the report with: ***bug report*** Version Please include your phone number of your BBS. I may want to call to chat. or pick up a file or two to reproduce your bug. A list of Citadels is at the end of this file, there are probably more than those listed, but I collect this information from the vortex detector and these are active Citadels. I am working on current problems and will post new versions as they become tested. Currently, distribution is on the Amiga Zone and Aminet ftp sites. Obviously, I will have it on the Amiga Zone first. The Amiga Zone (609) 953-8159 Note: other systems will also have the latest version, I am hoping to get a system in each state(eventually). If you wish to have me post a version in your area, send me some mail or call the Amiga Zone directly. As always, the Amiga Zone will have it first and a message will be posted to the Citadel 68K room when a new version is available. In this version, you can set the stack to anything larger than 8K and Citadel will run. Anything less and it will stop. I use a stack of 30K in my testing because my compiler needs it. CTDL now does not set it's stack, you have to do it. Citadel does not require more than about 3K of stack during it's operation. You can always see what your Citadel needs with the SYSOP menu item "I"nformation. My normal BBS runs use the minimum stack of 8192. It also does not detach from the shell/cli it is started from. You have to use "run nil: ctdl" to do that. I leave the window open for any error messages. You can create a short script like: failat 100 stack 8000 ; Citadel only uses about 3K in my testing. cd cit: if not exists ctdltabl.sys echo "Citadel configuring, ctdltabl.sys not found" confg -O ; only parameters endif copy cit:ctdltabl.sys cit:log/ctdltabl.sys run ctdl +netdebug +netlog and use it to startup Citadel. This is similar to my startup routine, I also have email networking in my script. Please post a comment in the Citadel 68K room when you start running this version. I would like to have at least your BBS number and general location. Known Bug List: BA01 1) report that E hit while a message is paused did not allow the user to enter a message(or continue a held message). Could not duplicate. 2) Fast Transfers does not work with zmodem or any other external protocol. You must use the internal protocols. Probably never get fixed, my serial port is dead and I run with a GVP I/O extender card(cheaper than a new MotherBoard). 3) domain mail messages are not being sent to a node that is marked as OtherNet (MSGOUT), this affects only those using Internet Email Networking. Regular mail messages are sent... Plan on fixing... just need time. 4) Apparent bug in archived rooms, hard to reproduce, asks for the filename when you enter a message(some of the time). You will eventually need utilities, and probably want Zmodem. Grab them as you need them. Make sure your read this file and 68K.man BEFORE you start, it will save you time and effort. If you use these files, remember that they are FREEWARE. You do not have to send anyone a donation(although none have been refused) to anyone. If you wish help, find a Citadel with the Citadel 68K room, or call one of the BBS numbers listed. This is a project that is solely for the advancement of networking and communications. Enjoy it. The only restriction I would place on you is that you may not make commercial use of this program, sell it, or make people pay in anyway for it's use. If you charge your users a fee for the use of your system, you should feel guilty.... Some of the functions are based on shareware programs(like LHA). These programs are not free. You should send the shareware fee to the author for your use with your BBs. This is a copyrighted work. All rights are reserved by the people responsible for maintaining this code. It belongs solely to them. If you have questions feel free to contact me by posting a message in the Citadel 68K room. If you wish me to send you a set of disks with all the above files, I will do so, but it will cost you $10 for the disks, postage, and my time. It is free to download from any of the BBS locations. It should not be more than 3 880K disk. The Amiga Citadel is available on the mirrored ftp site: wuarchive.wustl.edu for those with FTP access. In the future, I will post all the files related to Citadel on those sites. Tony Preston Custom Services P. O. Box 254 Moorestown, NJ 08057 The Amiga Zone : US (609) 953-8159 Internet: apreston@k2nesoft.com The following systems are Citadels and may be used post messages. This List is reasonably current. You best bet is to call the Amiga Zone for the latest information. You will find the Citadel 68K room or Amiga room. These systems all net with The Amiga Zone with one or more rooms. This list is generated with the vortex detection utility, if your system is not listed, post a test seed in a shared room and eventually it will appear(Rooms:Amiga, Citadel 68K, or CitaNews). CA (604) 589-8539 CA (780) 430-9193 US (215) 946 1164 US (215) 946-1164 US (317) 843-1077 US (513) 939 1645 US (609) 346-1224 US (609) 854-9135 US (609) 931-3014 US (609) 953 8159 US (612) 470-9635 US (612) 572-1236 US (612) 623-7850 US (612) 757-7307 US (612) 783-7160 US (612) 879-0268 US (651) 460-6056 US (651) 730-0041 US (914) 244-3252