Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / WONDER10.ZIP / HISTORY.DOC < prev next >

Wrap

Text File | 1993-03-13 | 59.6 KB | 1,475 lines

W o n d e r W h o ----------------- Version 1.00 Released March 13th, 1993 I Wonder Who Transfered That File ? Shareware program door for PCBoard v14.x Copyright (C) 1993 by José De Almeida. All Rights Reserved. P.O.Box 4185. 1504 Lisboa Codex. Portugal. --- VERSION HISTORY --- ------------------------------------------------------------------------------ WonderWho v1.00: Mar 13, 1993 ------------------------------------------------------------------------------ ■ This is the first 'true' release. The first non-beta version of WonderWho. If you are installing WonderWho for the first time, you don't need to read this file. Instead, please refer to the WONDER.DOC Documentation file. ■ If you are updating from the previous version 0.19, first delete the following files: HISTORY.TXT LICENSE.DOC Then, you will need to overwrite or add the following files: WONDER.EXE WONDER.DOC (documentation file, this is new!) WONDER.CFG (please re-configure, if that is the case) WW_LANG (please re-configure, if that is the case) WW_NEWS HISTORY.DOC That's all! But please continue to read this file. ■ Changed the message "Waiting for Call" to "No Caller this Node" in the [WHO] commands. ■ Removed the LICENSE.DOC file from the file. Its contents are now included in the Documentation file WONDER.DOC. ■ Concluded the WonderWho Documentation file WONDER.DOC. Many many thanks to Mr.Afonso Vicente, SysOp of Intriga Internacional BBS, who revised my english in the Documentation file as well as this version history file. ------------------------------------------------------------------------------ WonderWho v0.19: Mar 4, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.18, you will only need to overwrite or add the following files: WONDER.EXE WONDER.CFG (please re-configure, if that is the case) HISTORY.TXT That's all! But please continue to read this file. ■ Moved from ProKit version 3.4 to ProKit version 3.44. WonderWho remains the same. ■ Added another option to the WONDER.CFG configuration file: CALLER_LOG= With this option you can enable or disable saving information about each command a user entered while in the WonderWho door, in the PCBoard CALLER's log file. Unless you un-comment the line in the WONDER.CFG file and specify differently, by default this option enables the written to the CALLER's log file, as it happens in the previous versions. So, if you want WonderWho to written to the file, don't do anything about this in the configuration file. ■ Corrected bugs of the [WHO] command. Now WonderWho is compatible with PCBoard's new file USERNET.XXX format and also with the older file USERNET.DAT format. Routines for reading this file where written from scratch. Many thanks to Mr.Mário Pozzetti (SysOp of SkyShip BBS) who helped me getting all the necessary informations about this new file format. ■ This version of WonderWho requires about 191 KBytes of RAM to run (8 KBytes more than previous version). ■ If nobody complains with bugs or so, I will continue to write the WonderWho Documentation, which I already started. It's the last missing thing, in order to distribute version 1.0. ------------------------------------------------------------------------------ WonderWho v0.18: Mar 2, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.17, first delete the following files: WONDER_W.* WONDER_N.* WONDER_M.* WONDER_Q.* HELP_*.* Then, you will need to overwrite or add the following files: WONDER.EXE WONDER.CFG (config file; see bellow) WW_LANG (THIS IS NEW!: language file; see bellow) WW_H_* (all help files have new names } WW_WELC (welcome file have a new name) WW_NEWS (news file have a new name) WW_MENU (menu file have a new name) WW_QUIT (quit file have a new name) HISTORY.TXT That's all! But please continue to read this file. ■ As you probably notice, all Help files have different names. Also, the Welcome, News, Menu and Quit screen files have different names. I think this is a better solution, in order to isolate all filenames from other programs that can have similar names, specially for the Help files. Simply delete all older files, and replace them with the new ones, as is described in the above step. ■ There is a bug in the [WHO] command. I could not correct this problem in this version. I already know what the problem is, but I do not have enough informations right know in order to correct the problem. The problem is that ProKit is reading the USERNET.DAT, when it should be reading the new USERNET.XXX. This is not exactly a ProKit bug. The latest ProKit version simply is not new enough to have know about this new file and format. This problem was first related by Mr.Mário Pozzetti (SysOp of SkyShip BBS), who told why the bug happens. Also Mr.Pedro Chaves (co-SysOp of MsMac BBS) related this problem. ■ I have included a ProKit macro $NONSTOP$ at the beginning of the Welcome, News, Menu and Quit files, in order to continuously display those files. There was some problems found at SkyShip BBS about this subject, probably related with each user page length configuration. This feature was suggested by Mr.Mário Pozzetti (SysOp of SkyShip BBS). Many thanks! ■ New log off feature. Now you will be able to configure the user log off. That is, you now can select which file is displayed to the user when he logs off using the [G]oodbye, [BYE] or [BY] commands. By default, unless you specify differently, WonderWho will display the log off script questionnaire as specified in PCBOARD.DAT. However, you can specify a different file, or simply disable this feature. Please refer to the WONDER.CFG comments concerning this option, for further details. ■ Config file Besides the options already working in the previous version 0.17, INTERRUPT or BIOS DLD_DIR= WELCOME_FILE= NEWS_FILE= MENU_FILE= QUIT_FILE= here is a list of all the new options you cab set: LANG_FILE= LOGOFF= OP_LEVEL_X= OP_LEVEL_M= OP_LEVEL_H= OP_LEVEL_G= OP_LEVEL_PRO= OP_LEVEL_WHO= OP_LEVEL_UU= OP_LEVEL_UF= OP_LEVEL_UD= OP_LEVEL_US= OP_LEVEL_UP= OP_LEVEL_UE= OP_LEVEL_UA= OP_LEVEL_UR= OP_LEVEL_UV= OP_LEVEL_UC= OP_LEVEL_DU= OP_LEVEL_DF= OP_LEVEL_DD= OP_LEVEL_DS= OP_LEVEL_DP= OP_LEVEL_DE= OP_LEVEL_DA= OP_LEVEL_DR= OP_LEVEL_DV= OP_LEVEL_DC= OP_LEVEL_AU= OP_LEVEL_AF= OP_LEVEL_AD= OP_LEVEL_AS= OP_LEVEL_AP= OP_LEVEL_AE= OP_LEVEL_AA= OP_LEVEL_AR= OP_LEVEL_AV= OP_LEVEL_AC= So, except for the INTERRUPT or BIOS option, all other options in the original included WONDER.CFG file are disabled. WonderWho doesn't need that you un-disable the options in order to work properly. Still, WonderWho remains plug and play! Nevertheless, you may want to change things, and you can do it! One of the interesting things of the above options, is that the SysOp have now full control about the security level a user must have in order to be allowed to execute a command. By the default, all commands are set to security level 0 (zero). You cannot set security levels for the two [VER]sion commands and also to the two [Q]uit commands. ■ Language file. This is a new and very powerful feature of WonderWho. It was foreseen in my mind for quite a while. Support to this file was created in order to provide SysOp's a way to change the names of all commands (except the two [VER]sion commands). Here is a list of all options you can set: OP_NAME_X= OP_NAME_M= OP_NAME_H= OP_NAME_Q= OP_NAME_G= OP_NAME_PRO= OP_NAME_WHO= OP_NAME_UU= OP_NAME_UF= OP_NAME_UD= OP_NAME_US= OP_NAME_UP= OP_NAME_UE= OP_NAME_UA= OP_NAME_UR= OP_NAME_UV= OP_NAME_UC= OP_NAME_DU= OP_NAME_DF= OP_NAME_DD= OP_NAME_DS= OP_NAME_DP= OP_NAME_DE= OP_NAME_DA= OP_NAME_DR= OP_NAME_DV= OP_NAME_DC= OP_NAME_AU= OP_NAME_AF= OP_NAME_AD= OP_NAME_AS= OP_NAME_AP= OP_NAME_AE= OP_NAME_AA= OP_NAME_AR= OP_NAME_AV= OP_NAME_AC= Please refer to the WW_LANG file comments, for further details about all the above options. You cannot set names for the two [VER]sion commands. This file looks like a WONDER.CFG config file. And it almost is. You ca have as many language files as you want. That is, you can have 1 file per each language you have installed in your PCBoard system. By default this file is called "WW_LANG" but you can specify a different name in the WONDER.CFG config file. No path is allowed: file must be located in the same directory where the config file is. Also, you can not specify the file extension, because WonderWho will add the file extension accordingly to the PCBoard active Language Extension (as happens, for instance, with the Main Menu file). So, you can configure the door commands for all languages you may want, by creating one Language file for each language. The default Language file is the one that cannot have file extension (as in PCBoard). All other Language files must have the same extension as you defined in PCBML.DAT. If the user is currently using a specific language other than the default one, then WonderWho will look for a file with that extension. If he founds the file it will read it. If not, it will read the default file, the one without an extension. All options in the original included WW_LANG file are disabled. WonderWho doesn't need that you un-disable the options in order to work properly. Still, WonderWho remains plug and play! Nevertheless, you may want to change things, and you can do it! Besides all this, there is another major and powerful thing that WonderWho permits when using the Languages files. The routine that processes the Language files is the very same that processes the WONDER.CFG config file. The very same! This means that anything (really *ANYTHING*) you can set in the WONDER.CFG you can set (and overwrite) in the Language files. So, besides you setting things in the WONDER.CFG file you can specify language specific settings in each Language file. This gives you SysOp the total control about the WonderWho door! ■ News date limit SysOp's can now specify a date limit after which the WW_NEWS news file stops to be displayed to the users. This is done in the WONDER.CFG config file (available in Language files too) using the following option: NEWS_LIMIT= Please refer to the WONDER.CFG comments for further details. In this version, by default, NEWS_LIMIT= is set to 1993-03-31 (yyyy-mm-dd); ■ Corrected bug in the routine that saves log errors to $DOOR.ERR file. It was saving empty lines in some cases. ■ This version of WonderWho requires about 183 KBytes of RAM to run (1 KByte more than previous version). ------------------------------------------------------------------------------ WonderWho v0.17: Feb 29, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.16, you will only need to overwrite or add the following files: WONDER.EXE WONDER.CFG (see bellow) WONDER_M HELP_WHO (this is new!) HISTORY.TXT That's all! But please continue to read this file. ■ Added another command: [WHO] is on another node ? This is always a useful command. Now WonderWho has it! The Help files for this commands are included. ■ All yes/no prompt questions, besides the conventional"n" and "y" answers, now also supports "yes" and "no" answers, either in uppercase or lowercase letters. Mr.Pedro Duarte, at SkyShip BBS, told me that, in face of a yes/no prompt question, he answered "no", and WonderWho (by the time still JAwho) took his answer as a "yes". And he found it rather strange, and related it to me as a bug. Well, this was not a bug. Simply I didn't cared about this subject, and so I didn't implemented this feature. But of course this was kind of stupid: if a user type a "no" answer, WonderWho MUST process the user's answer as a "no", and not as a "yes"... Many thanks to Mr.Pedro Duarte for reminding me this! ■ Started to build the configuration file WONDER.CFG. The following options can are currently available in this version of WonderWho: DLD_DIR= WELCOME_FILE= NEWS_FILE= MENU_FILE= QUIT_FILE= Please carefully read instructions written in the file. Unless you have particular reasons, you do NOT need to change this file. ■ Minor program enhancements. ------------------------------------------------------------------------------ WonderWho v0.16: Feb 28, 1993 ------------------------------------------------------------------------------ ■ From now on, this door will be called WonderWho instead of JAwho. There four major reasons for this change. First, nobody liked the name. Several SkyShip BBS users have send me messages telling me this. They also proposed alternative and very interesting names. I appreciated very much their concern. I also did not liked the name two, after the moment I realized how "JAwho" sounds in english. It sounds awful... Third, it is much more easy to remember. Forth, this new name tells more about what the door is. Except for BBSs that have a door manager installed (such as DoorBill), the loggies should now enter WONDER instead of JAWHO command. ■ If you are updating from the previous version 0.15, you will only need to delete ALL previous files, overwrite ALL this new files, and configure directory names, paths, etc, from scratch. I am terribly sorry for this inconvenient. ■ Besides [G] and [BYE], WonderWho also recognizes the [BY] command. This new [BY] acts like [BYE], and this appears for more compatibility with the PCBoard commands. This feature was proposed by Mr.Afonso Vicente (SysOp of Intriga Internacional). Many thanks to him! ■ Added the parameter "Y" to the [G]oodbye command. If a user type: "G Y" at the command prompt, this will act exactly as the [BYE] command. It logs off without prompting anything, as PCBoard also does. This feature was suggested by Mr.Afonso Vicente. Many thanks to him! ■ Revised the HELP_G.* screen, and inserted information about the new [G]oodbye exclusive parameter "Y". A suggestion was made by Mr.Afonso Vicente, who remarked that the ALT-X command was not, in a communications program, the usual command to Hang-Up, but the ALT-H. Again, many thanks to him! ■ I have made some small revisions in this HISTORY.TXT file. ■ Finished the last three commands: [US], [DS] and [AS] Since date Again, there is nothing much to say about this. Try it ! ■ Revised output search headers for all search commands. ■ Errors and Average CPS commands, now displays the found field in White On Black color. ■ Here is a list of all new commands with Help files concluded in this version: HELP_US (since date) HELP_DS HELP_AS These are new files. The last Help files that were missing. ■ Removed the HELP_$$ and HELP_$$.TD files. These files are not anymore required by WonderWho, because all Help files for all commands are now available. ■ Revised the Main Menu file WONDER_M in the System section. Removed the "yellow options are available", are re-arranged the free space. ■ This version of WonderWho requires about 182 KBytes of RAM to run. ■ The future will be putting WonderWho working with the configuration file, an write the Documentation. ------------------------------------------------------------------------------ JAwho v0.15: Feb 26, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.14, you will only need to overwrite or add the following files: JAWHO.EXE JAWHO_M JAWHO_N HELP_UE (this is new!) HELP_DE (this is new!) HELP_AE (this is new!) HELP_UA (this is new!) HELP_DA (this is new!) HELP_AA (this is new!) HELP_UV (this is new!) HELP_DV (this is new!) HELP_AV (this is new!) HISTORY.TXT That's all! But please continue to read this file. ■ Changed the routine that searches the scan entries in a DOWNLOAD.TXT entry line back to Turbo Pascal, instead of using fast Assembler code as in last previous versions. Probably the performance for this step decreased about 14%, because at the time of the first inclusion of assembler in this routine, the results gave me 14% faster running. The reason of this change its because of a bug in the assembler routine. Some times the routine finds what it searches, sometimes not (but it was there). I really don't know the reason why this happens. Apparently the assembler was very erroneous and not perfectly stable. This bug was related by Mr.Pedro Duarte at SkyShip BBS. Many thanks to him! This bug was detected in a kind of amusing situation! Mr.Pedro Duarte tried to find entries for its wonderful LusoComm program, and also for the JAwho program. JAwho, in a very envious and despicable attitude, did not showed to him the LusoComm entries, only JAwho entries... ■ Finished more three commands, [UE], [DE] and [AE] Transfer Errors. There is nothing much to speak about. See for yourself and read the Help. ■ Finished more three commands, [UA], [DA] and [AA] Average CPS. There is nothing much to speak about. See for yourself and read the Help. ■ Finished more three commands, [UV], [DV] and [AV] Verbose list. There is nothing much to speak about. See for yourself and read the Help. ■ Here is a list of all new commands with Help files concluded in this version: HELP_UE (transfer errors) HELP_DE HELP_AE HELP_UA (average cps) HELP_DA HELP_AA HELP_UV (verbose) HELP_DV HELP_AV ------------------------------------------------------------------------------ JAwho v0.14: Feb 25, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.13, you will only need to overwrite or add the following files: JAWHO.EXE JAWHO_N (this is new!) HISTORY.TXT That's all! But please continue to read this file. ■ Beginning with this version, JAwho now supports writes to the LOG CALLER file. This is amazing! As usual, multinode support is available. Here follows an example, which I think is self-explanative. JAwho specific lines are the ones marked with a "->". "**************************************************************" "02-24-93 (09:03) (1) JOSE ALMEIDA (Local) (G) " " Caller Number: 880 " " Caller Security: 110 " " Opened Door (JAWHO) at 09:03 " -> " (AU) # 1: JOSE ALMEIDA " -> " (UF) # 1: JAWHO012.ZIP " -> " # 2: JAWHO013.ZIP " -> " # 3: JAWHO014.ZIP " -> " (DC) Count entries " -> " (PRO) View user profile " -> " (X) Expert mode is now on " -> " (M) Graphics mode is now off " -> " (VER) Program version info " -> " (H) Help about: (PRO) " -> " (G) Goodbye (from inside door) " " Minutes Used: 1 " "02-24-93 (09:04) (1) JOSE ALMEIDA Off Automatically " "**************************************************************" All search entries are logged, except for the [Q]uit command. Trailing characters past each log entry is filled with ASCII #255 for clear output, and in order to allow the file to be edit without any problem caused by ASCII text editors discards trailing space characters. All call entries are saved prior to execute the command, for convenient debug operations. JAwho will not save to LOG CALLER file if in Local Test mode (when you pass the word "LOCAL" as the third parameter to the program). But ProKit itself does this anyway, if a "Keyboard Time Expired!" takes place. In future, with the presence of the configuration file, the LOG CALLER writes can be disabled. ■ Corrected (I hope) error concerning the multi-language file support. JAwho processes Welcome, Menu, Quit and Helps files as follow: 1.: Gets the PCBoard language extension. 2.: Locate the file with the proper extension returned by PCBoard (which can be none). 3.: If the file was found, then the file is displayed. 4.: If the file was not found, then: 4.1: If file extension in none, the file is not displayed. Returns an error. 4.2: If file extension is not none, then tries to locate the same file, without extension. 4.2.1: If the file was found, then the file is displayed. 4.2.2: If the file was not found, then the file is not displayed. Returns an error. This process was, and still is, the process I have implemented. Except one thing I have changed. The routine that locates the files was not working properly when in a network environment. So I switch from my own routine to the equivalent ProKit routine, that supports networks. Many thanks to Mr.Pedro Chaves, Co-SysOp of MsMac BBS, who related the problem. As it happens in all other previous versions of JAwho, SysOps with multi-language systems can create language dependent files in order to work with JAwho. This also includes the Help files. But, even in a multi-language systems SysOps do not need to create those files. Because, as I said bellow, JAwho will display the files without language extension, if the proper file is not found. ■ Rewritten the error log routines. 1. Now it is ProKit itself that verifies the number of parameters passed to the door. 2. All errors are now displayed both to local screen and to the remote user (probably except the one listed above, I'm not sure). But they look the same as in previous versions. I created a special string: "Please notify the SysOp, @FIRST@..." in order to your users send you relate you the problem. 3. Errors are saved in $DOOR.ERR either by ProKit (always in the current directory) or by JAwho itself (in the door directory). 4. Remember, if a Welcome, Menu, Quit or Help files are not found at all (considering something I have said above in the multi-language file support) JAwho will display an error. But does not exit to PCBoard. 5. Errors are not saved into CALLER's log. ■ Added support for a NEWS file. This filename is: JAWHO_N. This file is provided originally by me, each new version of JAwho, listing new features and changes. But not necessarily all: only the things the users should now about. This file is taken care in almost the same way is done for the Welcome, Menu, Quit and Help files. You can edit this file, if you want, or simply delete it. If you delete the file, JAwho won't care about it. It won't display an error, even. So, a special treatment goes around this file. Still, multi-language support is available. By the time the JAwho configuration file is available, in future, the SysOp will have the possibility to specify a date after which the file will be no longer displayed to the user, let's say a date that represents a month after installing each new version of JAwho. By doing this, the News file will be displayed only until that date in reached. And the SysOp will not need to remember or care about this. ■ At last, LICENSE.DOC and ORDER.FRM are included. ------------------------------------------------------------------------------ JAwho v0.13: Feb 24, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.12, you will only need to overwrite or add the following files: JAWHO.EXE JAWHO_M. HELP_PRO. HELP_UC. HELP_DC. HELP_AC. HISTORY.TXT That's all! But please continue to read this file. ■ Concluded the [PRO]file command. ■ Added a sound beep at the time of displaying the statistics It advises the user that the search as been concluded. ■ Statistics could display more than 100.00% in the "Total uploads" or "Total downloads" fields, if the "Total search item(s) found" was equal to one of them. This has been fixed. ■ In the statistics, the accuracy of the following fields has been increased to 2 decimals digits: ■ "Average number of errors" ■ "Average CPS" ■ Revised the statistics, in the aspects described bellow. I think this way is preferable. ■ JAwho was displaying the LAST older filedate found in a matched search. Now displays the FIRST. ■ JAwho was displaying the LAST newer filedate found in a matched search. Now displays the FIRST. ■ JAwho was displaying the LAST worse number of errors found in a matched search. Now displays the FIRST. ■ JAwho was displaying the LAST best number of errors found in a matched search. Now displays the FIRST. ■ JAwho was displaying the LAST worse CPS found in a matched search. Now displays the FIRST. ■ JAwho was displaying the LAST best CPS found in a matched search. Now displays the FIRST. ■ Minor screen revisions in the search items prompt. Nothing important enough to speak of. ■ Concluded the [UC], [DC] and [AC] count commands. Help files are also available and included. ■ Increased the DOWNLOAD.TXT file buffer size from 4096 bytes to 10240 bytes. This should increase global search speed in about 17% or so. ■ Here is a list of all new commands with Help files concluded in this version: HELP_PRO (profile user) HELP_UC (count) HELP_DC HELP_AC ■ The TheDraw *.TD Welcome, Menu, Quit and Help files, are now included in the package in a ZIP archive. Filename is: TD_FILES.ZIP. So, if you don't plan to use them, simply leave them in the ZIP archive in the JAwho directory along with the other files. This will give you a more "clean" JAwho directory. ■ This version of JAwho requires about 177 KBytes of RAM to run. ------------------------------------------------------------------------------ JAwho v0.12: Feb 23, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.11, you will only need to overwrite or add the following files: JAWHO.EXE HELP_G. HELP_G.TD HELP_H. HELP_H.TD HELP_M. HELP_M.TD HELP_Q. HELP_Q.TD HELP_VER. HELP_VER.TD HELP_X. HELP_X.TD HISTORY.TXT That's all! But please continue to read this file. ■ Here is a list of all new commands with Help files concluded in this version: HELP_G (goodbye) HELP_H (help on help) HELP_M (mode graphics) HELP_Q (quit) HELP_VER (version information) HELP_X (expert mode) You must copy this files to the JAwho directory. ■ JAwho now again recognizes the older [VERSION] command. So, [VER] and [VERSION] will both be valid commands, and act in exactly the same way. ■ The [H]elp command is also recognized by JAwho as [HELP]. This is not a new feature of this version. But I think I did not said this before. Both commands act exactly the same way. ■ JAwho now also recognizes the [?] command as Help request. All [H], [HELP] and [?] act in exactly the same way. ■ Some small color screen bugs have been corrected, in the [X]pert and [M]de graphics commands. Nothing important to speak of. ------------------------------------------------------------------------------ JAwho v0.11: Feb 21, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.10, you will only need to overwrite the following files: JAWHO.EXE JAWHO_M. JAWHO_M.TD JAWHO_Q.TD (only this) JAWHO_W.TD (only this) HELP*.* (*** all of them ***) HISTORY.TXT And delete the following files, because JAwho do NOT use it anymore (see bellow the reason why this happens): HELP. HELP.TD That's all! But please continue to read this file. ■ Added the [G]oodbye option. JAwho also recognizes the [BYE] command. If the user enters [G] then JAwho will ask: "Proceed with logoff (Enter)=No ?". If the user enters [BYE] then no question will be asked to the user. So, JAwho handles this command the same way PCBoard does. In both cases, JAwho will also display, before dropping DTR: "Minutes used: @TIMEUSED@" "Thanks for calling, @FIRST@, and goodbye!" Thanks to Mr.Mário Pozzetti (SysOp of SkyShip BBS) who proposed this command. ■ Corrected some bugs regarding the Carrier Lost, Keyboard Expired situations. ■ JAwho no longer displays the ProKit........... message when exiting. ■ Benchmark test: BBS : SkyShip BBS NODE : Node #3 (node #1 is the server) NETWORK : Lantastic CONNECTION: 38,400 baud Search : DF JAWHO JAwho took 17 seconds to find 7 entries in 13,665 lines of the DOWNLOAD.TXT file. ■ Revised the Menu screen. Re-arranged the System group. Looks much better now, and leaves space for four future commands. ■ Some Help text files are now available and fully working. Proceed as follow. Delete the older two Help files from previous version 0.10, because JAwho no longer reads them: HELP. HELP.TD This were only used as temporary files for the last version, in order to put JAwho working properly with the Help system. Now both files have been substituted by two other ones: HELP_$$. HELP_$$.TD Still these two files are being used only to provide no errors. This file says that there are no Help available for that command, because it is not ready at this time. Now, you must copy all the HELP*.* files to the same directory were JAwho is stored. Each group of two files with the same name represents Help description for just one command. Example: HELP_UU and HELP_UU.TD. As I said before, all *.TD files are native TheDraw files used to design each screen. JAwho itself does not need these TheDraw files, and they may be deleted if SysOp wants to. They are included for the only reason of giving the SysOp the possibility to edit the original files, for instance, for translating purposes, using the very same design. Here is a list of all commands with Help files available at this time: HELP_UU (user name) HELP_DU HELP_AU HELP_UF (file name) HELP_DF HELP_AF HELP_UD (date) HELP_DD HELP_AD HELP_UP (protocol) HELP_DP HELP_AP HELP_UR (raw) HELP_DR HELP_AR ------------------------------------------------------------------------------ JAwho v0.10: Feb 19, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.09, you will only need to overwrite the following files: JAWHO.EXE JAWHO_M. JAWHO_M.TD HELP. HELP.TD HISTORY.TXT That's all! But please continue to read this file. ■ Changed the command "Version Info" from [VERSION] to [VER]. ■ Finished the following commands: [UP] Upload Protocol [DP] Download Protocol [AP] All Protocol ■ Accuracy of the percentage numbers in the statistics have been increased, and now displays 2 decimals floating point numbers. ■ Added support for some protocols that makes PCB to put the word "External" in the Average CPS field. Now JAwho no longer treats this case as a "Corrupted entry!". Instead, it displays "Ext." in the CPS field (except when in Raw searches, which displays whatever he founds there). When the "External" word is found in the CPS field, the entry will not count for the calculation of: Best CPS Worst CPS of the statistics. Of course, because the entry is valid, this will affect calculation of Average CPS. Average CPS is calculated by the following formula: the sum of all CPS fields of each DOWNLOAD.TXT entry line that matches the search, divided by the total number of DOWNLOAD.TXT entry lines that matches the search. This calculation is only done by the time JAwho displays the statistics. In this particular case I am dealing here, this means, in other words, each time DOWNLOAD.TXT entry line matches the search, JAwho will increase the number of entries found by 1, but JAwho will not increase the Average CPS account. So, Average CPS will be calculated without 100% accuracy, when the "External" word is found. Nevertheless, it is calculated, and should represent approximately the true Average CPS. I have found the "External" word in two different situations, in two different BBSs (both systems using PCboard v14.5a/10): 1) At SkyShip BBS, were the problem was first detected, only 1 entry in more than 12,000 lines were found. The protocol used in that specific case was HS/Link in a bi-directional transfer. Mr.Mário Pozzetti (the SysOp) and I, found this to be very strange, and we though that this was a 1 in 12,000 case. Nothing to be cared about, so. 2) However, at Intriga Internacional BBS, 182 entries in almost 3,000 lines were found. But ALL entries were LOCAL SysOp uploads using PCBoard's Ymodem/G internal protocol. Still is, strange... Many thanks to Mr.Mário Pozzetti and Mr.Afonso Vicente (SysOp of Intriga Internacional BBS), who help me to get this thing almost cleared out. ■ Besides the [Q]quit option, now JAwho will also understands [QUIT]. Both commands are the same, off course. ■ Revised the command line prompt system. It looks the same, but in some cases JAwho was displaying two empty lines, when it should display only one. This no longer happens. ■ Help system is ready to work. The command to call the Help can be [H] or [HELP]. Help systems supports multi-language, and works the same way as other JAwho files, and the PCBoard Help files. As soon as possible, probably next version, all the Help text files for available working commands will be included in JAwho Package. For the time being, only HELP. is provided. Please copy this file to the JAwho directory, where all Help text files should be also located. ■ This is a note, not a new feature: If you wish to change the JAwho screens, using the included *.TD files, you should get a program named PCBX. This is a TSR utility that captures the contents of a screen (full or region) and saves it to disk using PCBoard @X?? color codes fully supported by JAwho. This is a way I do the screens for JAwho. ------------------------------------------------------------------------------ JAwho v0.09: Feb 18, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.08, you will only need to overwrite the following files: JAWHO.EXE HISTORY.TXT And delete the following files, because JAwho do NOT use it anymore (see bellow the reason why this happens): JAWHO_I JAWHO_I.TD That's all! But please continue to read this file. ■ I have made some enhancements in the statistics. JAwho now formats better the screen outputted text, and in some cases it also shows at which entry the issue was found. Very nice, I think. ■ Added a Yes/No question before displaying the statistics. So, a user can now decide not to see the statistics, if he prefers. ■ Command line search items input has been totally rewritten. And this is why JAwho doesn't look anymore for the JAWHO_I. Instructions files. Now it has a PCBoard download prompt style for search items. I think this is quite better interface for doing such inputs. But, see for yourself. Added a Yes/No question is prompted before starting searches. The user can now abort, after he specifies the search items. Many thanks to Mr.Pedro Duarte who gave me some ideas about this, while discussing the JAwho door with me, in public, in the Main Conference of SkyShip BBS. Mr.Duarte is author of an extremely very good communications shareware program named LusoComm. Take a look as soon as possible! ■ I think I did not said before that JAwho command line is "buffered". I mean, in almost any part of the program (except when prompting yes/no question, more?, etc) you can immediately type a new command and its parameters. Try it! ■ I also think that I did not said before that SysOps can Chat and Shell to DOS, along with many other options, from within JAwho. ------------------------------------------------------------------------------ JAwho v0.08: Feb 18, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.07, you will only need to overwrite the following files: JAWHO.EXE HISTORY.TXT That's all! But please continue to read this file. ■ Added the [VERSION] command. This will display the JAwho version, copyright and register information, as well as the worldwide SkyShip BBS support and Portugal co-support The Image Bank BBS, telephone numbers and international network conferences. I think this command will not be listed in the Menu screen, but will be mentioned elsewhere in the future help procedures. ■ Corrected "Division by zero" run-time error. This was happening when JAwho did not found any item specified by the user in a search command. Then, by the time of displaying the statistics, some math operations were: 0 div 0. Now a check is taken, before performing those math operations. Many thanks to Mr.Tiago Pascoal, who detected this bug before I did. But, curiously, by the time I reed its message from SkyShip BBS, I already have detected and eliminated the bug. ------------------------------------------------------------------------------ JAwho v0.07: Feb 17, 1993 ------------------------------------------------------------------------------ ■ If you are updating from the previous version 0.06, you will only need to overwrite the following files: JAWHO.EXE JAWHO_M. JAWHO_M.TD HISTORY.TXT That's all! But please continue to read this file. ■ The program was displaying "JAwho v0.04" instead of "JAwho v0.06". This has been corrected, and in this version displays "JAwho v0.07". ■ More 16 commands were added to the Menu, which now displays 34 commands. This new commands are not yet available. The available commands still are the ones from version 0.06. ■ Increased the DOWNLOAD.TXT file buffer size from 2048 bytes to 4096 bytes. This should somehow increase speed. But not much. ■ Revised the critical routines which search for the ";" characters and positions in a DOWNLOAD.TXT entry line, using fast Assembler code. Performance increased about 36 %. Test results for a 100,000 times loop (same line): Old routines = 25.00 seconds (100 %) New routines = 16.04 seconds ( 64 %) ■ Minor speed enhancements in the routine that gets all DOWNLOAD.TXT entry line fields. ■ Revised the critical routines that generates strings filled with SPACES or BACKSPACES. Performance increased about 52%. Test results for a 2,000,000 times loop (always 16 characters): Old routines = 32.47 seconds (100 %) New routines = 15.60 seconds ( 48 %) ■ All source code concerning the process of search commands was revised, and, in some cases, totally rewritten. Some of them, source code was dramatically reduced, which means speed will have increased in those parts of the program. Source of all this procedures are now much more compact. ■ Revised the routine that searches the scan entries in a DOWNLOAD.TXT entry line, using fast Assembler code. Performance increased about 14%. Test results for a 1,000,000 times loop (always search for 3 characters): Old routines = 31.43 seconds (100 %) New routines = 27.20 seconds ( 86 %) ■ Revised the routine that concatenates the entry line string to be outputted each time a search match. Performance increased about 33%. Test results for a 50,000 times loop (always same string): Old routines = 30.22 seconds (100 %) New routines = 20.38 seconds ( 67 %) ■ Several other speed enhancements have been made. ■ JAwho will now display the following message (in red on black): "Corrupted entry!" when he founds that a DOWNLOAD.TXT entry line is invalid. Line entry number will also be displayed. This do not happens when the user performs a Raw search. In this case, data is not checked, because it is not necessary, and really increases speed. Besides, Raw searches are not the major features of JAwho. But, why not include Raw searches, as ProWho (ProRaw... eheheh) does ? ■ Changed the way [X] eXpert command works. Now it works exactly as PCB works. When you are in eXpert mode, and you enter [X] JAwho will force you press an [ENTER]. If you are NOT in eXpert mode, then no [ENTER] will be forced, because it returns immediately to the Menu command prompt. ■ The [M]ode (color/mode) is already finished and available. ■ JAwho now displays (and now in light_green_on_black color): "(10%) Entry #1,200..." instead of (was in light_gray_on_black color): "Entry #1,200..." The percentage means the percentage of bytes already reed from the DOWNLOAD.TXT file. I think this feature is very interesting, because lets the user know how much have been concluded in each search, and not only the line entry number of the file. In a text file such as DOWNLOAD.TXT is, it is impossible to know how many lines a text file have, except when you reach the EOF (End-Of-File) marker (which means that the very last byte has been reed). So, prior to anything, I check the size of the file, and then I keep an updated account of the number of bytes reed from the file. It's simple. In the previous versions, JAwho updates that "Entry #1,200" each 100 lines. I have changed this. Now updates are displayed each 200 lines. ■ Completely rewritten statistics! Added many new and fancy features! See for your self! You gonna get a hard-attack when you see then, eheheh! In Raw searches, this statistics are much less elaborated, because most of the data are not available. ------------------------------------------------------------------------------ JAwho v0.06: Feb 16, 1993 ------------------------------------------------------------------------------ ■ Corrected shared violation error when two nodes were accessing DOWNLOAD.TXT file. Bug was reported by Mr. Mário Pozzetti. ------------------------------------------------------------------------------ JAwho v0.05: Feb 16, 1993 ------------------------------------------------------------------------------ ■ Only one thing has changed in this release. JAwho will always start operate in non-expert mode, instead of reading PCBoard flag (and assume it). Several users experimented problems with this. They seem to not understand that they must type the [X] command in order to get the menu. And new users to the door doesn't not know the JAwho commands, off course. Mr.Mário Pozzetti (SysOp of SkyShip BBS) also suggested this. Many thanks to him. ■ I am looking for someone to help correcting my english in the future manual of JAwho... ------------------------------------------------------------------------------ JAwho v0.04: Feb 15, 1993 ------------------------------------------------------------------------------ ■ Many changes have been introduced, since last beta version. ■ JAwho is now based on ProKit v3.4 library instead od RMDoor v3.0. This is a major improvement!!! Many thanks to Mr.Mário Pozzetti (SysOp of SkyShip BBS) who tried to find some good Turbo Pascal library to use in JAwho. We discussed a lot about this subject. ■ JAW_TEST.BAT file The JAW_TEST.BAT file remains the same. Use this file to locally test JAwho from outside PCBoard environment. Off course, as usual, you will need to edit the file and specify the proper directories, for JAwho configuration file and PCBoard directory. ■ JAWHO. file This is the file PCBoard will copy to DOOR.BAT when running JAwho. You must edit this file in order to proper specify all directories passed as parameters to JAwho. In multi-node PCBoards systems, there is an easy way to avoid having as many files like this (and JAwho .EXE file) as nodes. Simply create an environment SET, such as this (for instance, for node #4): SET PCB_NODE=C:\PCB4 Or, for node #3: SET PCB_NODE=C:\PCB3 Create a SET (always with the same name, this is very important) in each computer, correctly specifying the local directory. Then, supposing JAwho is located in the server computer, where you probably put all your door programs (let us say C:\DOORS\JAWHO), change JAWHO. file as this: @echo off c:\doors\jawho\jawho.exe c:\doors\jawho\jawho.cfg %PCB_NODE% This will work fine, and you only need one JAWHO. for ALL nodes. ■ $DOOR.ERR file This is the JAwho error log file. The filename have been changed since last version (was JAWHO.LOG). Still is a text file, and data written to this file, is almost the same. ■ JAWHO.REG file The registration file. Remains exactly the same. ■ JAWHO.CFG This is the JAwho configuration file. The file now has a different name (was JAWHOCFG.CFG). Everything has changed. JAwho itself does not read (or check) this file. It is required by the ProKit library. As always, the name is it not important, because filename can be changed, as long you specify the correct parameter each time you call JAwho. This file has only one statement at the first line. It can be either INTERRUPT or BIOS. Nothing more is necessary to configure. Everything else has been removed. ■ JAWHO_I (and JAWHO_I.TD) files The JAwho door search Instructions screen file. This is NEW. This file will be displayed anytime a user runs a search command (except if user is in eXpert mode). The purpose of this file, is give the user a quick reference about the way he/she can make the search. So, this is not exactly a help file (help files are different things). This file is a PCBoard @Xcodes. You should not use ANSI codes. There is a very good TSR program, called PCBX.EXE that is perfect to capture TheDraw screens into @Xcodes files. Many thanks to Mr.Pedro Pinheiro (SysOp of Crazy Byte BBS), who gave me some ideas about this and other features of JAwho, while paciently testing my door at The Image Bank BBS. ■ All other @Xcodes files Remains all with the same purpose, but they are not anymore ANSI files, but @Xcodes files. I only changed the JAWHO_M Menu contents. ■ JAwho commands JAwho commands are now all working, except the [H], [US], [DS] and [AS]. The "|" character used to separate each search item was substituted by the ";" character. ■ I enhanced the statistics data, displayed after each search. Take a look. ■ There are lots of other new things, but most of them refers to the method of programming. I think (but I'm now really sure) that this version is slower than the last one. This, being true, is because of ProKit. I think RMDoor was faster. ------------------------------------------------------------------------------ JAwho v0.03: Feb 10, 1993 ------------------------------------------------------------------------------ ■ I have renamed the included file J.BAT to JAW_TEST.BAT. The purpose remains the same: testing JAwho outside PCBoard environment. ■ Corrected about a dozen bugs, concerning I/O errors. JAwho was not displaying, and not writing to the LOG file, the I/O error meaning. Instead, he displayed "Not an I/O error.". This happened in about a dozen places in the source. I forgot to change a parameter passed to the Error LOG procedure... ■ Corrected bug when a user enter the [Q]uit option. JAwho displayed "Invalid entry. Please try again @FIRST@..." ■ Added a new program command line parameter. Now the complete syntax is: JAWHO cfg_file [local] [pcb_dir] The third one is the new parameter. I added this to simplify the program test, while running without being under PCBoard environment. The program will determine the PCBoard directory (specific node or "home" directory - it doesn't matter) by the following possible sequence: a) Current directory This is be the best recommended way, because it always reflect the right directory (either a node specific or "home" directory - it doesn't matter). b) 2nd or 3rd Command line parameter. If you specify a 2nd parameter, JAwho will get it. Then, he determines if it is the "LOCAL" parameter or not. If is not, then JAwho will use this 2nd parameter as the PCBoard directory. This overwrites the current directory way. If the 2nd parameter is "LOCAL" then he finds out if you have specified a 3rd parameter. If you have, then JAwho will use this 3rd parameter as the PCBoard directory. This also overwrites the current directory way. Specifying the PCBoard directory in the command line, it is only recommended for testing JAwho outside PCBoard environment. I use this feature in the included JAW_TEST.BAT batch file, to test JAwho in this situation. c) PCB_DIR= Statement in the configuration file. If you specify this statement, JAwho will use it. It overwrites the a) and b) situations. You should not use this statement. JAwho should determine the PCBoard directory by getting the current directory. ■ During execution, the program may write to disk one or two temporary files, depending if you specify the "LOCAL" command line parameter or not. And because normally you don't specify this parameter, then two files will be written to disk. It always written a file with the EXACT name specified as the 1st parameter. Using the examples provided, this file is named JAWHOCFG (not the JAWHOCFG.CFG). This file is written in the directory you specify, and should be the JAwho directory. This file is not required by JAwho itself, but, witch is rather stupid, by the RMDoor initialization routines. An attempt is made to delete this file when exiting the program. If the file is not found, this has no consequences whatsoever (it will be deleted next time JAwho runs). A second file is temporary written to disk (except when you specify the "LOCAL" command line parameter). This file is always named PCBOARD.SYS, and is always written in the directory where your USERS file is located. As in the previous paragraph, this file is required by RMDoor initialization routines, to be located in the same directory where the USERS file is. This is even more stupid..., and JAwho itself doesn't required this thing to be made this way, of course. An attempt is made to delete this file when exiting the program. If the file is not found, this has no consequences whatsoever (it will be deleted next time JAwho runs). I think (and I'm almost sure) that both USERS and PCBOARD.SYS are not changed by the RMDoor routines. Tests I've made reflects that both files remain un-touchable. Again, I don't think this is a good approach, in the PCBOARD.SYS case, because if a user looses CARRIER the PCBOARD.SYS file contents should be changed, in order to reflect that (that's what they say in the PCBoard documentation). I will try to test this lost CARRIER situation as soon as possible. I think I can change the file contents after RMDoor des-initializes, and just before halting the program. ■ I have changed the JAWHO_M menu file. Looks very much the same, except when in color mode, all commands I have finished programming are displayed in yellow. This is a good way for you to each commands you can run. ■ Changed two names in the configuration file. Not really important to speak about. Only kind of a cosmetic change. ■ I have finished the [RC] command. This command works very much like ProWho does the job, only better. First, you can specify up to 5 scan entries (will be explained in detail when you enter the command). And second, it also displays the line number when he finds a match scan. Looks nice these way, I think. ■ Now that finished the first search command, I need to know is the search speed is faster enough... ■ Corrected bug when SysOp wants to shell to DOS. This was not working, and it is not really a bug, because I simply forgot to include a Turbo Pascal compiler directory, necessary for Turbo Pascal perform the shell function... Tests I have made tell that the program now requires about 93 KBytes of memory to run. ------------------------------------------------------------------------------ JAwho v0.02: Feb 8, 1993 ------------------------------------------------------------------------------ ■ Please read again ALL the notes in the INCLUDED FILES section. Some important things were changed. ■ I think now some of the last version problems have been removed. You can now run JAwho in multi-node systems, with no problem. But, the door still is in beta besting. ------------------------------------------------------------------------------ JAwho v0.01: Feb 6, 1993 ------------------------------------------------------------------------------ ■ This is the first version of the JAwho door. A beta version. ■ The program as not been fully tested. Be aware of that! :) ■ Put all files included in the archive in the same directory. JAwho does not require to be placed in a specific directory. You may choose any directory you want, as long as the configuration is ok. ■ RMDoor toolkit used for handling all communications procedures, is not registered. So, it displays a message saying that RMDoor is not registered. I will register this toolkit as soon as possible. ■ The only Main Menu commands working at this time are: [X]pert menus on/off [Q]uit ------------------------------------------------------------------------------ [end-of-file]