DCQwk/Tag 2.6D Version 1.5b Copyright 1992-1993 by Daniel Corbeau FIDONet 1:167/115 Welcome to DCQwk, the off-line mail reader door written specifically for TAG 2.6c. Reading echomail and local mail can be quite lengthy, especially on the more active machines. This door will allow your users to pack up all new mail, download it to themselves, read, reply and enter new mail off-line, and upload the mail packets back to the BBS. The door will then unarchive the incoming mail packet and toss the messages into their proper message areas. This is all done with a minimum of setup and time spent by the sysop due to the DCQwk's ability to interface directly with the TAG 2.6 system files. All message areas are able to be processed, including Netmail, E-Mail, and any local areas you have defined. Of course all security and flags are in effect. Users without normal access to the area will not be allowed access through the door. DCQWK is fully share-aware and can be used on multinode systems as well as single node systems. The files created and downloaded by DCQwk are in QWK format and can be read in any off-line mail reader supporting this format. There are many available and most are share-ware or free-ware. The response packets created by the off-line mail readers are then read by the door. QWK format is the most popular format available for reading mail off-line. Legal Stuff ~~~~~~~~~~~ DCQWK is Copyrighted (c) 1992 by Daniel Corbeau. It is supplied without warranty, and the author assumes no liability for damage caused by performance or non-performance of the software. Shareware Registration ~~~~~~~~~~~~~~~~~~~~~~ DCQWK is shareware! This means that if you use it, you must register it. You are hereby granted a limited license to use this program for one month. At the end of this month, you must either register this program or stop using it. Registration price for this program is $20.00 and should be mailed to: Daniel Corbeau 357 2e Avenue #1 Ile Perrot Quebec Canada J7V 4Z6 Please fill out and mail the enclosed form called REGISTER.DCQ (part of the distribution archive) when registering. Disclaimer ~~~~~~~~~~ References to trademarks and copyrighted software not controlled by Daniel Corbeau will appear throughout this documentation. Such references are made for the purpose of clarification only and should not be construed as implying that any agreement or license exists between Daniel Corbeau and the lawful or owners of these trademarks and copyrights, nor that any endorsements are intended. Guarantee ~~~~~~~~~ DCQWK is guaranteed to take up space on your hard disk. DCQWK is guaranteed not to rip, wrinkle, or tarnish. DCQWK is guaranteed to disappear if deleted. No other warranty or guarantee is made, expressed or implied. ~~~~~~~~~~~~ ~ WARNING! ~ ~~~~~~~~~~~~ This program contains code that is designed to discourage tampering. Sections of the code dealing with registration notices and the like cannot be patched without causing undesirable results. The author assumes no responsibility for any adverse consequences or damage to systems or software that may occur if this warning is ignored. A word to the wise should suffice. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Quick and Easy Installation (New Users) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTE: A fossil driver, active for each node, is required to be installed and operating for this door work properly. Also, if running multinode, SHARE.EXE must be loaded. 1. Make a directory called DCQWK on the hard drive partition on which the TAG BBS program resides. The C: drive will be used in these examples. (The directory can reside under another directory such as C:\BBS\ if desired.) Make a subdirectory under \DCQWK called PACKET. C:\DCQWK |____PACKET 2. Unarchive the entire distribution archive into the \DCQWK directory. 3. Now check that the DCQWK.BAT file reflects your drives and directories. In our example the DCQWK.BAT reads as follows: cd\dcqwk dcqwk -B -DC:\BBS\ -W -T -R%8 *OPTIONS - SEE BELOW cd\bbs | || | | | |__ Pass the Real modem rate to DCQWK exit | || | | | | || | | |__ Use TAG Color codes | || | | | || | |__ Use the work drive | || | | || |__ Startup directory for this node | || | ||__ Disk drive containing the startup directory | | | |__ Switch to inform DCQWK of the startup directory | |__ Turn off the bell at the BBS side The functions of the commands are as follows: -B Informs DCQWK to turn the bell off on SySop side. When operating in local mode (see below), however, the bell is still active. This switch is optional. -D Informs DCQWK of the TAG startup directory for the current node. The drive and directory must follow the -D without intervening spaces. This switch is mandatory. Example: -DC:\BBS\ -W Informs DCQWK to use the indicated work drive. This can be a RAM drive to speed up performance or to a faster hard drive. Whatever drive is specified, it must have at least 1 to 2 megs of available space. This switch is optional. -T To enable the optional TAG P Default colors in the menus. Without the -T, DCQWK uses its internal colors. This switch is optional. -R Inform DCQWK the REAL modem TO modem baud rate. The TAG DOOR parameter %8 must follow without intervening spaces. This switch is mandatory for remote usage. Refer to "REALBAUD.DOC" for examples. -M To enable unattended bundling of mail for users whose user# appears in the dcqwkhol.dat file. The user can add his user# to this file if he has an AR flag set matching that which was selected while running the DCQWKINS.EXE installation program. This switch is optional and is only used during batch file automatic bundling operations. An additional command line switch exists to allow the SySop or another authorized user to log on locally. Set up a batch file or command line with the above options as desired and append a -L# (the # being the number of the user in the TAG user list). This will allow the local user to access the message areas without having to enter TAG in local mode. -L# Begins DCQWK with a local logon. The # indicates the number of the user (i.e., SySop = 1). This switch is optional and only used during local logon. When this file has been reviewed and reflects your configuration, copy or move it to the directory where TAG resides (C:\BBS in our example). For multinode sysops copy the DCQWK.CTL file to the other TAG startup directory(ies) and modify it to point to the current startup directory (i.e., -dc:\bbs1). The final batch file which must be created (or the commands of which must be added to the nightly maintenance batch file) should read as follows: cd\dcqwk dcqwk -M -DC:\BBS\ cd\bbs | | | | |__Path to the TAG startup directory | | | |__Switch to inform DCQWK of the startup | directory | |__Switch to enable unattended bundling This batch file can be named anything you want. It can either be called from the nightly maintenance batch file or the lines can be added to the batch file. 4. Go into TAG and add a selection to the Message Menu (normally menu number 3) and set it up to create the dorinfo#.def and to call the DCQWK.BAT file. See page 22 in the menu documentation package for TAG version 2.5g. The updated documentation for TAG 2.6 has not been released as of this writing. DO NOT use the `@' in front of the batch filename, DCQWK will get the real user name from TAG user.lst. The following is a suggested Menu setup for the DCQWK Door: 1. Long Program Name: (D)CQwk Off-line Mail Reader Door 2. Short Program Name: (D)CQwk Mail 3. Key: D 4. SL: 10 5. AR Flags: @ 6. Program Key: : 7. Program Data: DCQWK.BAT 9. Security: SL, GSL, AR Flags, Normal Command, No Linking Multinode sysops: Repeat this procedure for each node. 5. Enter into the DCQwk directory and run the DCQWKINS.EXE program. It will query you for certain information about the BBS. Fill in the information per the example below. A DCQWK.CTL file will be created. The Pro ; The name of your BBS. Ile Perrot ; The town where the BBS is located. 514-425-2276 ; Your BBS phone number 1:167/115 ; The FIDONet Address. THEPRO ; QWK packet name as in "THEPRO.QWK" or ; THEPRO.REP without the extension. 255 ; The SySop's security level (normally 255). Daniel Corbeau ; The SySop's name. If this is NOT a ; registered copy, leave the default value of ; NOT REGISTERED or door will NOT run! Also, ; enter your name EXACTLY as it appears in the ; FIDONet Nodelist ABCDEFGHIJKLM ; Type in the Key code obtained (see section ; below on obtaining the key). If this is a ; registered copy, type in the key code ; supplied with the registration. If this is a ; non-registered trial copy, leave the key code as ; 000000000000 or the door will not run! The Pro BBS ; A default origin line - may include the BBS ; name, phone number, or any other text you wish to ; be put at the bottom of each message. F ; The drive letter you wish to use for your ; work drive. This may be any valid DOS ; drive. It is only effective when the -W switch ; is included in the command line in the batch ; file. M ; The AR flag a user must have to be able to ; access the mail holding feature. (M is only an ; example, any flag can be used.) The @ flag is a ; special case and will allow all users to access ; the mail holding feature. This is not recom- ; mended on most BBSs due to the volume of echomail ; and the needed space to store these packets. c:\temp ; The local upload/download path. The default path ; where local uploads and downloads will take ; place. This can be over-ridden at the time of ; download if desired. This is NOT the path to be ; used for Mail Holding. 6. Ensure that the following files are in the DOS PATH: DSZ.COM (or DSZ.EXE) PKZIP.EXE PKUNZIP.EXE PKARC.EXE (Any ARC archiver can be used AS LONG as you modify PKXARC.EXE the menu commands through DCQWKINS to reflect the changes. See section #7 below.) ARJ.EXE LHARC.EXE Additionally, if you define other archive types in your archive menus or use communications routines other that DSZ.COM in your protocol menu, these files must also be in the path. Please see the section on creating custom menus for more information on this subject. DCQWK will NOT function properly without access to these files! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 7. It is highly recommended that sysops use the included menus and not try to create their own when using DCQWK. However, if after a period of use, the sysop wishes to change the menus, he may do so as part of the DCQWKINS.EXE installation program. This function will allow you to define up to four (4) different archiver types and up to four (4) different communications protocol types. A sample (and fully functional) archive and protocol menu set is included in the distribution archive and the default settings in this menu set should suffice for the majority of users. WARNING! You must have some knowledge of the command line parameters for the Archive and transfer protocol software to successfully change the menus. The sample menus are shown below: Archive Menu Sample Protocol Menu Sample [Z] Zip [X] Xmodem [A] Arc [Y] Ymodem [R] Arj [Z] Zmodem [L] Lzh *[A] Auto Zmodem * The Auto Zmodem selection allows for automatically beginning the download after the bundling is complete. For it to operate, the letter used to select the protocol MUST be "A" as shown above. The [Z] Zmodem selection requires that you press the "G" key before downloading begins.) When you exit this program, the DCQWK.MNU will be updated and the values you installed will take effect. A word of caution, the command line strings for the archive programs and for some communications programs are *VERY* specific. Even a capitol letter in place of a lower case letter can cause an error. Be sure you have them correctly set or strange results may occur. 8. The final step in installing DCQWK is deciding whether or not you wish to include certain text files in the QWK packet. Some types of files might be welcome messages, news, or new file listings. Including these previously created files is accomplished by creating an ASCII file named DCQWKFIL.DAT in the \DCQWK directory. The contents of this file are simply lines indicating the file you wish to include in the QWK packet along with the path to it. Each line must end with a carriage return/line feed (CR/LF). Please see the example DCQWKFIL.DAT below. c:\bbs\gfiles\hello. c:\bbs\tagnews\news. d:\goodbye. When this file is complete, be sure it is saved in the DCQWK directory. This file is optional and if it does not exist, its absence will be ignored and no error will occur. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Quick and Easy Installation (Upgrading from a previous version.) To upgrade from a previous version of DCQWK, please read and be familiar with the above instructions for new installations. Your DCQWK directory will have already been created and your old version of the program will be installed. REGISTERED USERS! Be sure you write down the key number from the DCQWK.CTL file in a secure location or have your registration paperwork handy. If this is not done, you will not be able to access the program after installation! Next, put a formatted floppy into one of your floppy drives and copy the contents of \DCQWK directory onto it. Also copy OFLMSG.USR from your \GFILES directory and the DCQWK.BAT file from the main BBS directory onto this diskette. This is done in case you experience problems with the new installation. You can then fall back to the older version until you find out what the problem is. Next, erase the old files from the DCQWK directory by entering it and issuing a DEL *.* command. BE SURE YOU ARE IN THE PROPER DIRECTORY! Make a subdirectory under \DCQWK called PACKET if it does not already exist. See step 1 of new user installation procedures for an example. Then remove the \WORK and the \UPLD subdirectories if they exist. Finally, proceed with the installation from step 2 above. Enter the key number you copied above into the DCQWKINS program when prompted. Finally, you have a choice as to whether you wish to convert your OFLMSG.USR file or delete it and create a new one. If you are upgrading from a version previous to 1.4, then you MUST delete the OFLMSG.USR file. If you are upgrading from version 1.4 or 1.4a you can convert the file using a program supplied called CONVOFLM.EXE. It will upgrade the file and place an original copy of the OFLMSG.USR in the same directory with the name OFLMSG.OLD. To run this program, type CONVOFLM . Substitute the path to the OFLMSG.USR file in place of PATH. In most cases this will be the \GFILES directory or in multinode setups, the \DFILES directory. (Example: CONVOFLM C:\BBS\GFILES\). ONLY RUN CONVOFLM.EXE ONE (1) TIME! If you are upgrading from 1.5(a) then only replace DCQWK.EXE with the new one and make the apropriate modifications to your batch files. OBTAINING A KEY ~~~~~~~~~~~~~~~ To obtain a key to permit DCQWK to run for a one month period with no other restrictions, log on to The Pro BBS at (514)-425-2276 and enter the door which will produce your custom key. Another option is to request a key via Netmail to Daniel Corbeau at FIDO 1:167/115. This can be direct Netmail or routed netmail. Include your full name, BBS Name, and voice phone number. The third, and easiest option for sysops able to FREQ files is to FREQ the magic name KEY from 1:167/115. The machine will look up your information in the FidoNet node list and return the proper key to you along with instructions for its use. Be sure to use your name in the installation program EXACTLY as it appears in the nodelist or DCQWK will not operate! The key you obtain will allow DCQWK to work for a period of 1 month. During this period you can decide if you want to register DCQWK or discontinue using it. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ MAINTENANCE ~~~~~~~~~~~ There is no maintenance required with DCQWK. However, if you create new areas, delete current areas or make any changes to the message areas that result in changes to an area's number or order, run DCQWKMNT from the DOS prompt to notify DCQWK of the changes. DCQWKMNT must reside in the DCQWK directory. DCQWKMNT prevents a user from uploading messages to an area that was deleted or into the wrong area in the case of the areas being moved, added or deleted. Caution: Only run DCQWKMNT once after the changes have been made. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ OPERATION ~~~~~~~~~ For the user to operate DCQWK, he must enter the program using the command (D)CQWK from the message menu prompt (or whatever key you set up to enter the program). The main screen will appear. (If the message areas have been changed, the user will be sent directly to the Select areas screen to confirm his selections.) New users will be directed to the Archive selection, Protocol selection, and Select Area screens before arriving at the Main Menu. The main menu allows for the following selections: Main Menu ~~~~~~~~~ [H] Help [S] Select Areas [A] Archive Selection [P] Protocol Selection [D] Download Messages [U] Upload Messages [M] Mail Holding [Q] Quit The [H] Help selection presents a SySop configurable help screen for the user. The [S] Select Area function allows the user to select which areas will have mail bundled and sent. Several options exist for the user to toggle areas on and off. If the user types the number of the area it will toggle on or off. If the user lists areas, separated by a comma, all areas listed will toggle. (Example: 1,2,5,8,12 will toggle areas 1, 2, 5, 8, and 12 either on or off depending on their state before the command was given. The final option is the ability to toggle blocks of numbers. The command 1-5 will toggle areas 1 through 5 to their opposite state. These commands can be issued together as 1,4,5-9,12 which would toggle areas 1, 4, 5, 6, 7, 8, 9, and 12. The [A] Archive selection function lets the user select which archiver will be used for compressing the mail bundle. This is normally PKZIP but can be whatever is set up during the installation of this door. The [P] Protocol selection allows the user to select which transfer protocol is used to transfer the mail packet. The [M] Mail Holding selection accesses the Mail Holding Menu. This menu allows users to perform various functions including turning mail holding on or off, viewing packets available, downloading packets, a help screen for this menu, and quitting back to the main menu. The specific commands will be discussed below. Mail Holding Commands ~~~~~~~~~~~~~~~~~~~~~ [H] Help [A] Activate Mail Holding [C] Cancel Mail Holding [D] Download Packets [V] View List of Packets [Q] Quit The [H] Help selection presents a SySop configurable help screen for the user. The [A] Activate Mail Holding selection, turns nightly mail bundling on for this user. The [C] Cancel Mail Holding selection stops nightly mail bundling for this user. The [D] Download Packets selection begins downloading saved mail packets using the protocol selected in the main menu. It begins with the oldest packet and progresses towards the newest packet. The [V] View List of Packets selection presents a list of packets and their sizes to the user for their information. The [Q] Quit selection returns the user to the main menu. The (D)ownload Messages selection begins searching for messages in the selected areas and presents the user with the following options upon completion of the search: The following commands are valid and are described below. If the user needs help with the commands, pressing "?" will get a display similar to the following: Scan Commands ~~~~~~~~~~~~~ Q Quit. Don't do the bundling. Return to the main menu. G Go. Do the bundling with the areas and the amount of messages scanned. -# Remove an Area from the bundling. Example: -3 -23 would remove areas 3 and 23 from the bundling. -Lx/y Bundle from Area x the last y messages. These messages will be bundled in addition to any found during the search. x = Area number, y = Number of messages. Example: -L10/20 Would bundle the last 20 messages from Area 10. Note: -# and -Lx/y command can both exist in the same command line, however, both CANNOT affect the same area. Example: -3 -23 -L10/20 is valid but -3 -L3/20 is NOT valid ? Will re-display this list (in monochrome only) The (U)pload Messages selection begins the process or uploading the user's reply packet and tossing it to the proper areas. When selected, DCQWK will prompt the user to begin the upload. At the completion of the upload, DCQWK will check the messages for matching user name, whether the messages are duplicates (accidently uploading a reply packet more than once), and toss the acceptable messages into the proper areas. The (Q)uit selection will save the current message status and lastread numbers if the download command was completed successfully. If the command was started but aborted during the download or an error was detected, the user will be asked as to whether his lastread information should be saved. Upon entering his selection the program will either save or not save the lastread information and exit to the BBS. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NETMAIL ~~~~~~~ To enable the sending of Netmail from an offline mail reader ensure that the offline reader/editor makes the first line of the message text as follows: To: Zone:Net/Node If this does not occur, either enter it manually or use a different QWK compatible offline reader which does enter the Zone:Net/Node number as above. The format must be exactly as above. DCQWK will then toss the incoming messages into the Netmail area with the proper flags set. The entire line including the "To: " must be entered (don't forget the space after the : and before the Zone number). Offline enters this information correctly but WinQWK and Bluewave 2.10 do not. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ PROGRAM LIMITATIONS ~~~~~~~~~~~~~~~~~~~ 999 areas. 32k bytes per message (FIDONet limit) No limit on # of messages except as set in the download limits. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ COMMENTS ~~~~~~~~ * You can edit the DCQWKHLP.LST file, which is the main help screen, but be sure that you don't exceed one screen length (24 lines in most cases). * You can edit the DCQWKSCN.LST file, which is the scan help screen, but be sure that you don't exceed one screen length (24 lines in most cases). * You can edit the DCQWKHLD.LST file, which is the mail holding help screen, but be sure that you don't exceed one screen length (24 lines in most cases). * DCQWK has been tested to date with OFFLINE, WinQWK, SMLR, and Bluewave Vers. 2.10 off-line mail readers. * Locked Baud rates to 38400 have been tested. * If no tagline is defined in your MBOARDS.DAT file, a tagline will be generated as entered during the installation. If none has been defined, a default tagline will be generated by DCQWK. * TOSSCAN, CONFMAIL, SQUISH, FMAIL and IMAIL mail tossers have been tested with DCQWK. * BNU and X00 Fossil drivers have been tested with DCQWK ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ THANKS ~~~~~~ Many thank's to: Debbi & Mark McKay, Ed Kwasniewski, Roger Lareau, John Riley and Tom LeClerc for doing the beta testing and for the support. Also thanks to the TAG Team for the wonderful BBS program. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ HISTORY ~~~~~~~ 1.5B Re-compiled with the TAG 2.6D version file structure. Changed the way DCQWK get the real baud rate value. Removed the "DCQWK.CTL" parameter. Added speed for DV users. 1.5A Corection of the December date problem. Corection of hte error in the mail holding maintenance 1.5 Maximum mail bundling added. Enables the sysop to restrict the number of messages packed as determined by the baud rate of the user. On local logons and nightly mail packing (mail holding) sessions the values are ignored. Added default upload/download directory for local users. Added selection of message areas by ranges. Range selection can be as x-xx (1-10) just as you can with the zscan function of TAG. Added the PERSONAL.NDX file to the archive to allow you to read messages addressed to you in any section without having to go into the section. This is a reader dependant feature. The problem addressing Com3 and Com4 has been fixed. The Main menu has been changed to include a blank line between commands and Quit. Improved the menu for non-ANSI users. DCMENU.EXE is now totally incorporated in DCQWKINS.EXE. Empty mail bundles are no longer created or downloaded. This is also true in mail holding. Added a trial usage feature. If the values of "NOT REGISTERED" and "0000000000000" are left in the configuration file, the door will operate in a demonstration mode allowing sysops to see how the door operates and actually create and download small mail packets. Limited to 15 messages per area and 50 messages per packet. Also no uploading of messages is allowed. Patched DCQWK to take into account an incorrect flag in the Bluewave netmail area and allow netmail to be sent from this and other errant readers. Corrected an error which allowed users to post in a message area even if their post SL was lower than what the area required. Added support for up to 999 message areas (the same as TAG). Note however, some readers do not support this many areas. Added a program to optionally convert your old copy of OFLMSG.USR to the new format. CONVOFLM.EXE Improved the speed of the bundling process. 1.4 Mail holding feature added. Allows selected users to enable automatic bundling of mail in their selected areas. A sysop definable AR flag must be set up in the installation program and users must have this flag for this option to work for them. Very useful when an avid mail reader goes on vacation, for instance. Created packets can be listed or downloaded from this menu also. Allowed sysop definable bulletins and other ASCII files to be bundled up with the mail packet and sent to the user. Sysop must define which files are to be sent in the DCQWKFIL.LST file in the DCQWK directory. A command line parameter (-M) has been added to enable nightly mail bundling for selected users. Modified DCQWKINS to add the user flag defined above. 1.3 Support added for TAG 2.6c multinode setup (as well as earlier multinode beta versions. Eliminated the need to create the \WORK and \UPLD directories. They are now created and removed on the fly. A separate log file is now created for each node. Node 1 is called DCQWK.LOG. Command line parameters have been added. -B Informs DCQWK to turn the bell off on sysop side. In local mode, however, the bell is still active. -D Informs DCQWK of the TAG startup directory for the current node -L# Begins DCQWK with a local logon. The # indicates the number of the user (i.e., sysop = 1). -W Informs DCQWK to use the indicated work drive. This can be a RAM drive to speed up performance or to a faster hard drive. A Minimum 1 to 2 megs of space is needed in this drive. 1.2 Added Duplicate checking for uploaded messages. Duplicate messages (up to 200 messages) are kept in a file. Useful if someone forgets to erase a reply packet after uploading it and then starts a new session. Speed increase for Hudson message bases. Added configurable archive and protocol menus. Eliminated the need for complicated batch files for the archive and protocol manipulation. Areas with 0 new messages are now skipped during the bundling. The lastread pointers to each message area are now only updated when the user uits the door. Improved the calculation of the displayed lastread indicators. The door will now use the address indicated in the MBOARDS.DAT file to enable the proper use of AKAs. If none is specified, the door will default to the main address as specified during DCQWKINS installation. Added the ability to define a default origin line. If the message is uploaded without one, this one will be used. If this origin line is also not defined, then a default origin line provided by DCQWK will be used. Added a function that will notify a user if the MBOARDS.DAT file has been modified since the last time a user has logged on. It will notify the user to update his area selections and he will be sent directly to the Area selection menu. *******####### ALSO #######******* ~~~~ A new program has been added called DCQWKMNT.EXE which performs maintenance when areas are added or deleted or whenever the MBOARDS.DAT has been modified. Its function is to prevent a user from uploading a message to a deleted area, or to the wrong area. Added a function to verify the user name when uploading a message packet. The field "From Who" is checked against the users BBS Realname or the BBS Username. If it doesn't match either of the names, the message will be rejected. *******####### ALSO #######******* ~~~~ DCQWK will change the Username to the Realname in areas that do not allow handles and will change the Realname to the Username in areas that force handles. If the Username is the same as the Realname, DCQWK will replace the name with "Anonymous" for areas with forced handles. Expanded error messages and made them more explicit. Created an error log file in the dcqwkerr.log for fatal errors. Added the "Scan" command. After issuing a "Download" command and after DCQWK has displayed the areas and message numbers in each selected area, these commands will allow various functions affecting the bundling of messages. It replaces the "Proceed Y/N" command. 1.1 Added support for password protected areas. Added Tag ^P color codes in the election screen. (Thank's to Mark McKay for the source code.) Added the ability to download and copy message packets locally. Added Auto Zmodem download. Removed the reate function. Made the reate command part of the ownload command. Modified the swap routine to use COMSPEC. Made the program update the lastread file for new users. (New users shouldn't see the lastread errors anymore.) Corrected wrong tag lines in areas. Corrected compilation errors. (Mostly the error!) 1.0 First public Release ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In case of problems I can be reached via: TAG_Doors Echo Fido: 1:167/115 BBS : (514)-425-2276 Voice (514)-425-2819 No later then 3:00 AM EST.. :-) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~