DlgQWK- Changes.txt ~~~~~~~~~~~~~~~~~~~ Note to previous users! This version of DlgQWK has some new features which require you to check your system defined archivers and your defined WORKPATH. Please read this document as well as the entire DlgQWK.doc file fully to understand the new changes and features. Make SURE to read the documentation regarding these changes! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Note that v0.71 of DlgQWK is an INTERIM release- I had fully intended to offer NetMail support, UUCP E-Mail support, and custom menu support but these features are currently awaiting some changes by TPT before I can fully implement. Thus consider this release a interim update that has many enhancements, but is lacking some of the things I really wanted to change. Expect another update fairly soon- most of the changes have already been made but need more testing and they also need the TPT changes. v0.71a 10-Apr-93 (Second distribution release) ~~~~~~ Installation: ------------ For current users of DlgQWK, merely copy the new DlgQWK executable over the old version, and carefully read the following. You also might want to copy the updated 'DlgConfig:Menu/DlgQWK/R.help' file. For new users of DlgQWK, read the full documentation for installation instructions, and read the following. 1) DlgQWK now uses DLG system defined archivers when compressing QWK bundles. Please read the full documentation regarding in this, paying strict attention to the following: a) You MUST have the '-r -j' options in your ZIP compression string. Recommended compression string for ZIP is: Zip -r -j ~d ~s b) See item #3 below- this is mandatory to ensure ZIP compresses properly. 2) If DlgQWK receives any failure code from an archiver when bundling user's QWK bundles, all files will be moved to DlgQWK:First_Last/. In addition, both the user and the sysop will be informed. This way the sysop can salvage the QWK files and archive them by hand and then reupload the QWK bundle to the user's private directory. 3) Due to a constraint in the current ZIP for Amiga, the temporary workpath DlgQWK uses (as defined by the keyword WORKPATH in DlgQWK.CFG) must NOT end in a colon. Thus you can not use the root directory of any device, a logical assigment, or RAM:. The WORKPATH must be an actual directory, and have the full path defined. 4) DlgQWK now allows users to upload .REP bundles directly from within the door. Users no longer must upload reply bundles to themselves via the FILE module. Note that this distribution of DlgQWK includes an updated help file for the [R]eply function (DLGConfig:Menu/R.help) 5) DlgQWK now clears the cache (if any) under OS2.0 at the appropriate times. Thus DlgQWK should now be 68040 friendly. Previous versions would immediately GURU when decoding the keyfile when run on a 68040. This new change has not been tested yet, but should work. 6) DlgQWK now has ARexx functions built in to send the special 'MSGADDED' ARexx message to DlgMail. This allows DlgMail to immediately export newly imported messages into echomail areas after the user logs off. Note that this occurs only if you have the following line in your DlgConfig:Batch/TRx.startup file: (See DlgMail documentation) DMC >NIL: UserExport 7) Users names in alias areas are now changed to their alias before messages are exported. 8) All external programs such as archivers, file transfer protocols, etc. are now launched with my special 'ForkI' code. This allows for detection of return codes, proper task priority (the task priority of these launched programs will truly inherit the current task priority, even under OS2.0), and proper task interruption should DLG wish to shut down DlgQWK for any reason. 9) More enhanced archiver detection is now implemented for decompressing user uploaded .REP bundles. ARC, ZOO, LZH, LHA, ZIP, and ARJ is now detected. 10) Switched to new version of JForth. Several enhancements realised by the switch. DlgQWK is now a bit faster and more compact (though it IS larger due to the added features). 11) Annoying (and harmless) mungwall hit upon exit is now removed. This was a compiler bug, and I was able to remove it by re-writing some low-level compiler startup code (thank goodness JForth has this ability, as most all Forths do...) 12) Changed resource locking that DlgQWK does so that DlgQWK will properly free it's private resource if forced to abort. Prior to this change, often subsequent launches of DlgQWK would 'hang'. 13) Don't forget to check Logs:DlgQWK.log for detailed logging information. Additional error logging has been added. You may wish to update your optional NEWS or HELLO text files to notify your users of some of these changes. They will particularly be interested in the fact they can now upload .REP bundles direct. A bulletin to all your users would also be a good idea. v0.65a 15-Dec-92 (First distribution release) ~~~~~~ 1) Added my internal database handling. This database tracks usage of DlgQWK. 2) Added the SYSLEVEL keyword to DlgQWK.CFG. This value determines the userlevel at which a user must be to be able to select the 'User Launches' function from the DlgQWK menu. 3) Added the [$]-UserLaunches function to the DlgQWK Menu. This function displays a brief histogram of DlgQWK usage based on data maintained internally. v0.64b 13-Dec-92 ~~~~~~ 1) Fixed 'Twirlydiddle' during area scan to work with all terminals. 2) Added logging imformation about each imported message to DlgQWK.LOG 3) Made change to use an internal dlg.library routine to display the help files, rather than call 'DF' externally. Works far better. 4) Made change that insures temporary work directory is clean before starting any bundling or reply processing. 5) Added foul language screening to imported messages. This is done the conventional way by checking for a SCREEN.DAT file in the message area (if not present, check in DlgConfig:Misc also). If you are not sure how SCREEN.DAT works, check your DLG documentation. (NOTE: This feature works ONLY on registered copies of DlgQWK!)