ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / MISC / FCE10.ZIP / FCE.DOC < prev next >

Wrap

Text File | 1991-08-30 | 28.0 KB | 802 lines

FCE: File Comment Extractor DOS Edition, Version 1.0 ──────────────────────────────── (C) Copyright 1991 by Andy Hakim All Rights Reserved R E F E R E N C E M A N U A L For a quick summary of options, type FCE at the dos prompt. TABLE OF CONTENTS ADDRESSES .............................................................. 1 SOFTWARE LICENSE ...................................................... 1 NOTATIONS/TERMINOLOGY .................................................. 1 WHAT IS FCE? .......................................................... 2 WILL FCE BE USEFUL TO YOU? ............................................ 2 SEARCH STRATEGY ........................................................ 3 SYSTEM REQUIREMENTS .................................................... 3 TEXT FILES ............................................................ 4 COMMAND LINE SYNTAX .................................................... 4 <inputfile> ...................................................... 4 <wildcards> ...................................................... 4 <scanfile[.lst]> .................................................. 4 [outputfile] ...................................................... 4 [options] ........................................................ 4 COMMAND LINE OPTIONS .................................................. 5 /? ................................................................ 5 /F=# .............................................................. 5 /T=# .............................................................. 5 /M ................................................................ 5 /C ................................................................ 5 /O ................................................................ 5 /S ................................................................ 6 /I<F,E> .......................................................... 6 /CLS=# ............................................................ 6 /CO<O,S>=# ........................................................ 6 /FL<I,S>=# ........................................................ 6 /C=<file[.cfg]> .................................................. 7 /EMS=# ............................................................ 7 COMMAND LINE EXAMPLES .................................................. 8 FILE PROCESSING SCREEN ................................................ 9 ERROR MESSAGES ........................................................ 9 PROJECT HISTORY ........................................................ 10 SOURCE CODE ............................................................ 10 TRADEMARKS ............................................................. 10 REVISION HISTORY ...................................................... 11 FCE version 1.0 Reference Manual Page: 1 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ADDRESSES ─────────────────────────────────────────────────────────────────────────── Comments, suggestions, or questions? You can contact me via: US Mail │ FCE Development │ P.O. Box 70392 │ Houston, TX 77270-0392 │ Telephone │ (713) 880-3059 │ Electronic Mail │ st144@menudo.uh.edu (Internet addresses) │ cosc12r2@jetson.uh.edu │ Bulletin Board │ Sand's BBS │ (713) 961-1604 │ 2400/9600/14400 baud, HST/v.32 │ Username: Andy Hakim SOFTWARE LICENSE ─────────────────────────────────────────────────────────────────────────── FCE (DOS Edition, v1.0) is a free, public domain program. There is no registration process or monetary fee required in order to use it. You may freely distribute FCE to others as long as: ■ Only the original files are distributed ■ No changes are made to any files ■ No money is charged for the program FCE, its documentation, and all related files are (C) Copyright 1991 by Andy Hakim. All Rights Reserved. The author of this program is not liable for any damage caused by its use. By using this program, you agree to the above conditions. If you find FCE useful, I would appreciate it if you let me know. NOTATIONS/TERMINOLOGY ─────────────────────────────────────────────────────────────────────────── The following notations are used in this documentation: <> describes a required parameter [] describes an optional parameter {} describes a default parameter Do not type <>, [], or {}, only the information inside them. You should be familiar with basic DOS concepts such as wildcards, paths, subdirectories and text files. If those concepts are foreign to you, refer to your DOS manual. There are also many books written on understanding DOS. FCE version 1.0 Reference Manual Page: 2 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ WHAT IS FCE? ─────────────────────────────────────────────────────────────────────────── FCE is an abbreviation for File Comment Extractor. It is a utility that compares two text files that contain filenames and comments, and tries to match filenames. On a successful match, the comment is copied from the scan file to the output file. For example: Contents of file one (files you have downloaded from a bbs): ┌─────────────────────────────────────────────────────────────────────────┐ │ SOLAR .ZIP │ │ 386UTILS.ZIP │ │ MICRODRW.ZIP │ │ MOUSEADJ.ZIP │ └─────────────────────────────────────────────────────────────────────────┘ Contents of file two (a file list from your favorite bbs) ┌─────────────────────────────────────────────────────────────────────────┐ │ MOUSEADJ.ZIP Mouse adjustment utility │ │ GUMBY .ZIP Doubles your cpu speed (386/33 -> 386/66)! │ │ MICRODRW.ZIP Micro Draw -- easy to use drawing program │ │ POKEY .ZIP Use modem lights as infrared signals! │ │ 386UTILS.ZIP Useful utilities for 386 based pc's │ │ PRICKLE .ZIP Store up to 5mb on a 360k floppy -- works! │ └─────────────────────────────────────────────────────────────────────────┘ FCE's Output: ┌─────────────────────────────────────────────────────────────────────────┐ │ SOLAR .ZIP │ │ 386UTILS.ZIP Useful utilities for 386's │ │ MICRODRW.ZIP Micro Draw -- easy to use drawing program │ │ MOUSEADJ.ZIP Mouse adjustment utility │ └─────────────────────────────────────────────────────────────────────────┘ If you are familiar with database operations, you may recognize that FCE is similar to a JOIN function. FCE's advantage is that it operates on text files and saves you the trouble of converting the file to your database, defining fields, creating indexes, etc. It also offers many features that may be hard or cumbersome to duplicate in a database. WILL FCE BE USEFUL TO YOU? ─────────────────────────────────────────────────────────────────────────── It all depends on how you categorize your files (if at all), and the number of files you acquire over a given period of time. The main purpose of FCE is to save you the time and drudgery of entering comments for each file, not to mention the trouble of figuring out what some of the filenames are. FCE reads and creates text files. Therefore it is very easy to search, manipulate, or transfer information using viewing programs, text editors, and word processors, etc. If you organize your file lists as text files you will find FCE much more helpful. FCE can also be used to compare two file lists and mark filenames that are duplicates. The output can be sent to a separate output file. See the last example in COMMAND LINE EXAMPLES. FCE version 1.0 Reference Manual Page: 3 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ SEARCH STRATEGY ─────────────────────────────────────────────────────────────────────────── Before you use FCE, you will need a copy of a file list from some BBS or an anonymous FTP site, preferably from the board/site that you got the files from. Usually, sysops have a text file containing a list of all files avaiable on their system. If they dont, you can probably do a text file capture on all available files. This will serve as your scan file. Note: FCE defaults to PC Board formatted lists. By the way, dont expect a 100% success rate! On the other hand, if you start seeing rates of 0 - 10% MAKE SURE THE COLUMN OFFSETS/LENGTHS ARE SETUP CORRECTLY. SYSTEM REQUIREMENTS ─────────────────────────────────────────────────────────────────────────── ■ Any IBM PC or compatible running MS-DOS 2.0 or higher ■ Any video card, EGA/VGA recommended ■ Minimum of 200k of free conventional RAM ■ Optional: Hard disk, any size ■ Optional: EMS memory, as much as possible ■ Optional: Disk cache software ■ Optional: Ram disk software EGA/VGA: FCE uses various features that are available on EGA or VGA display cards. You can use other displays, but the screen will not look snazzy. Hard Disk: FCE accesses the disk frequently and needs space to store temporary files. A hard disk offers better performance and greater storage space. Conventional Memory: You can use the dos CHKDSK command to see how much free memory is available on your system. If there is not enough memory, FCE will inform you. More memory allows you to use larger scan files. Expanded (EMS) Memory: EMS memory is automatically detected and used. The EMS driver should meet LIM v3.2 (or higher) specifications. More EMS memory allows you to use larger scan files. Disk Cache: Using a disk cache may dramatically decrease the file processing time. There are many commercial and public domain disk cache programs available. Ram Disk: Using a ram disk will also decrease the file processing time. For maximum performance you should log on to the ram disk before running FCE (this is because temporary files are created on the currently logged drive.) FCE version 1.0 Reference Manual Page: 4 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ TEXT FILES ─────────────────────────────────────────────────────────────────────────── FCE is a line oriented text file processor, that is: it operates on text files, and each line in the text file is treated as a distinct entity. Lines may be of different lengths but all fields (ie: filenames, comments, dates) must be in consistent locations. For example, all comments must be one below the other. There is no need to edit text files. Blank lines, headers, footers, titles, and high order characters are ignored. Input files do not occupy system memory and therefore can be of any length. Each line in a scan file occupies 4 bytes of conventional memory, and N+5 bytes of conventional or EMS memory. N is the filename length specified by the /FLS=# option (see COMMAND LINE OPTIONS). A machine with 500k free and no EMS (under default options) can handle files of about 20,000 lines. With approximately 1.5mb of EMS memory, FCE can handle files of about 100,000 lines. COMMAND LINE SYNTAX ─────────────────────────────────────────────────────────────────────────── There are two basic formats that can be used to start FCE: FCE <inputfile> <scanfile[.lst]> [outputfile] [options] or: FCE <wildcards> <scanfile[.lst]> [outputfile] [options] <inputfile> ASCII text file containing filenames that need to be identified. This parameter is required if <wildcards> are not specified. <wildcards> Generates a file list (similar to DIR) and appends it to inputfile. If inputfile is not specified, FILELIST.TXT is created. Multiple wildcards may be used (ex: *.zip *.arc *.doc). This parameter is required if <inputfile> is not specified. <scanfile[.lst]> ASCII text file containing filenames and comments. A .LST extension is assumed if none is specified. This parameter is always required. [outputfile] ASCII text file that will contain new information created by the search. This parameter is optional. If it is not specified the <inputfile> will be used as the output file. [options] Options are used to set various settings. See the section labeled COMMAND LINE OPTIONS for more information. Any valid dos device and/or pathname [d:][path] may precede a file name or wildcard parameter. FCE version 1.0 Reference Manual Page: 5 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ COMMAND LINE OPTIONS ─────────────────────────────────────────────────────────────────────────── Options allow you to customize various setting. Options are not case sensitive, may be specified in any order, may not be abbreviated, must be preceded by slash (/) or minus (-), and must be separated by a space ( ). /? (/HELP, or FCE with no options) Displays help screens. There are three help screens which can be viewed by pressing the <space> bar. After you cycle through the help screens, you return to the dos prompt. You can also quit any help screen by pressing <esc>. /F=# Sets the fuzzy match minimum percentage. A fuzzy match, also called a partial match, occurs when some (but not all) characters in the two filenames are the same. A percentage is calculated by dividing the number of characters that match consecutively by the total number of characters in the filename. For example, a fuzzy match on TFE10 and TFE20 yields a percentage 60. If you set /F=100, only identical matches will be considered "good". If you set /F=0, all matches will be considered "good". By default /F=75 which picks up many filenames are vary only slightly (ie: version numbers). /T=# Sets the tab expansion length. Tab characters (ASCII code 9) are automatically expanded into spaces. By default, tab stops are set at 8 characters apart. If you do not want to expand tabs, use /T=1. /M Displays minimal information. No statistics are shown, and no EGA/VGA display tricks are used. Only a few basic messages are displayed as work progresses. This option causes text to be sent DOS's standard output device and uses BIOS screen writes. Output can be redirected using > or >>. For example, of you want absolutely no output from FCE, redirect it to the NUL device (consider it a black hole): FCE MYFILES.TXT BBSLIST > NUL Use this option if you experience problems under Desqview of Windows. /C Filenames are considered case sensitive. Normally, both UPPER and lower case is considered the same. /O Overwrites old comments in the input file with new comments in the scan file. Normally, as a safety measure, if a comment exists in the input file the new comment is not copied. If a comment does not exist in the scanfile and the filenames match, nothing is done. /S Strips leading and trailing spaces from filenames before a comparison takes place. Normally, no striping is done. FCE version 1.0 Reference Manual Page: 6 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ /I<F,E> Translates to /IF for Fuzzy match or /IE for Exact match. The appropriate type of match is marked in the output file with an asterisk character. The * is placed immediately before the comment field of the output file. More specifically, it is placed one character behind the value given by /COO=# option. A match is treated as EXACT when all characters in both filenames are identical. A match is treated as FUZZY when the filenames match only match partially. The partially matched value must meet or exceed the fuzzy value specified by the /F=# option. Example: ┌──────────────────┘ GREATTAG.ZIP 9349 03-26-90 *Allows you to sign your message CORE292.ZIP 37718 10-04-90 *Coretest version 2.92 /CLS=# Sets the comment length in scan file. If the length is 0 no comments are copied. If the length is greater than the actual length of the comment, spaces are added at the end of the line. The default length is 45. ─────────────────────────────────────────┐ ┌────────────────────┴─────────────────┐ GREATTAG.ZIP 9349 03-26-90 Allows you to sign your message CORE292.ZIP 37718 10-04-90 Coretest version 2.92 /CO<O,S>=# Translates to /COO=# for output file or /COS=# for scan file. Sets the comment offset (starting column) of the appropriate file. The default offset is 34. ──────┐ │ GREATTAG.ZIP 9349 03-26-90 Allows you to sign your message CORE292.ZIP 37718 10-04-90 Coretest version 2.92 /FO<I,S>=# Translates to /FOI=# for input file or /FOS=# for scan file. Sets the filename offset (starting column) of the appropriate file. The default offset is 1. ┌────────────────┘ GREATTAG.ZIP 9349 03-26-90 Allows you to sign your message CORE292.ZIP 37718 10-04-90 Coretest version 2.92 /FL<I,S>=# Translates to /FLI=# for input file or /FLS=# for scan file. Sets the filename length of the appropriate file. The default offset is 8. ┌──────────────────────────────────────────────────────────┘ ┌──┴───┐ GREATTAG.ZIP 9349 03-26-90 Allows you to sign your message CORE292.ZIP 37718 10-04-90 Coretest version 2.92 FCE version 1.0 Reference Manual Page: 7 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ /C=<file[.cfg]> Reads options from a configuration file. A .CFG extension is assumed if none is specified. The config file is a text file that contains a list of options each on a new line. Every line in the config file is treated as a separate parameter just as though it was typed on the command line. A space ( ), period (.) or semicolon (;) in the first column of a config line indicates that the entire line is to be used as a comment. Comments may also be used after an option by separating them by at least one space. For example: ┌─────────────────────────────────────────────────────────┐ │; A SAMPLE FCE CONFIG FILE │ │/f=35 ; this sets fuzzy level to 35% │ │/cls=60 ; this sets comment length to 60 characters │ └─────────────────────────────────────────────────────────┘ There are several config files included with this copy of FCE. They contain field offsets and lengths for various BBS systems and internet host systems. You can TYPE them from dos. /EMS=# Restricts expanded memory usage to # Kbytes. Normally, EMS is used only as a last resort. At a maximum, FCE will use up about 2 megabytes of EMS. If you want to disable all EMS related routines, use: /EMS=0. FCE version 1.0 Reference Manual Page: 8 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ COMMAND LINE EXAMPLES ─────────────────────────────────────────────────────────────────────────── Many combinations of the command syntax are possible. You can try out some of the following examples. The sample files MYFILES.TXT and BBSFILES.LST are included in this package. FCE MYFILES.TXT BBSFILES.LST Compares all filenames in myfiles.txt to those in bbsfiles.lst. Because no output file is specified, the input file myfiles.txt becomes the output file. FCE MYFILES.TXT BBSFILES Compares all filenames in myfiles.txt to those in bbsfiles.lst. The extension ".lst" is added automatically. FCE C:\DL\*.ZIP BBSFILES Directory listing of all *.zip files is stored in filelist.txt which serves as the inputfile and output file. FCE C:\DL\*.ZIP BBSFILES FINAL.TXT Directory listing of all *.zip files is stored in filelist.txt which serves as the inputfile. Output is stored in final.txt. FCE C:\DL\*.* C:\OLD\*.* C:\NEW\*.* BBSFILES FINAL.TXT Directory listing of all file of the directories \dl \old \new are stored in filelist.txt which serves as the input file. Output is stored in final.txt. FCE MYFILES.TXT C:\DL\*.* BBSFILES FINAL.TXT The input file myfiles.txt is appended with a listing of all files in c:\dl. The new version of myfiles.txt is compared to filenames in bbsfiles.lst and the output is stored in final.txt. FCE MYFILES.TXT BBSFILES.LST /C=PCBOARD.CFG Reads configuration file pcboard.cfg which contains parameters for scanfile. FCE MYFILES.TXT BBSFILES.LST /IM /F=50 /COS=30 Indicates exact matches, sets fuzzy match level to 50%, and sets the comment offset in scanfile to 30 characters. FCE BBSFILES.LST MYFILES.TXT NEEDHAVE.TXT /IF /CLS=0 Compares filenames in bbsfiles.lst to myfiles.txt and creates a file called needhave.txt. An asterisk is placed beside each filename that matches. The /CLS=0 option insures that no comments will be copied. Notice that the order of the input and scan file have been reversed. In this way, FCE can also be used as a file comparison utility. FCE version 1.0 Reference Manual Page: 9 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ FILE PROCESSING SCREEN (not available if you use the /M option) ─────────────────────────────────────────────────────────────────────────── The screen is organized into three windows: information, statistics, and output. The output window, though not labeled, is the one in the center of the screen. The bottom line of screen displays the name of the task currently being executed: analyzing, indexing, sorting, searching, and copying. At the bottom right of the screen there are various spinning symbols informing you that work is in progress. They are pretty neat looking... if you have an EGA/VGA display. The icon rotation speed is synchronized with the system clock so that it does not vary with the CPU speed. Information on statistics: Exact Matches: Count of identical matches Fuzzy Matches: Count of partial matches (meeting /F=# value) Lines Written: Count of modified lines written to the output file Lines Analyzed: Count of lines looked at in input file Success: Percentage of matching filenames ERROR MESSAGES ─────────────────────────────────────────────────────────────────────────── Error messages are reported on the screen as well as in the ERRORLEVEL system variable in dos. A successfull run will set ERRORLEVEL to 0. 1: SCAN FILE TOO LARGE The scan file contains too many lines. You must split the file into a smaller size. 2: INSUFFICIENT CORE/EXPANDED MEMORY The scan file contains too many lines. You can either split the file into a smaller size or remove some memory-resident programs. 3: CANNOT ACCESS INPUT FILE The file does not exist, or there is some other access problem. 4: CANNOT ACCESS SCAN FILE The file does not exist, or there is some other access problem. 5: CANNOT CREATE TEMPORARY FILE There is some problem while trying to create the file. There may not enough free disk space on the currently logged drive. 6: CANNOT CREATE OUTPUT FILE There is some problem while trying to create the file. There may not enough free disk space on the currently logged drive. An invalid filename and/or path may have been specified. 7: CANNOT ACCESS INPUT FILE The file does not exist, or there is some other access problem. 8: CANNOT ACCESS CONFIG FILE The file does not exist, or there is some other access problem. 9: INVALID COMMAND LINE OPTION An invalid option has been specified on the command line. FCE version 1.0 Reference Manual Page: 10 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ 10: INVALID CONFIG FILE OPTION An invalid option has been specified in the config file. 11: DISK READ/WRITE FAILURE A disk error has occurred. There may not be enough disk space. 12: EXPANDED MEMORY CORRUPT There is problem with the EMS system. Reboot and try again. Or disable the EMS option by specifying /EMS=0. 13: INVALID PATHNAME OR FILESPEC An invalid pathname or wildcard combination has been specified. 14: GUMBY ERROR Critical Error: Please contact the author if you see this message. PROJECT HISTORY ─────────────────────────────────────────────────────────────────────────── FCE was originally written because I was transferring some archives to a different tape format, and I did not feel like retyping each comment. A friend suggested that it may be a handy tool. After some additions, FCE v1.0 "became". This was a part time project for me, and as such I do not have any plans to expand it. However, I will fix bugs and minor annoyances... time permitting. SOURCE CODE ─────────────────────────────────────────────────────────────────────────── FCE was written using Borland C++ v2.0. If you would like to purchase a copy of the source code, please contact me at the addresses listed at the start of this document. The source code contains ORIGINAL techniques relating to: ■ EGA/VGA font redefinition ■ Database style indexed retrieval system ■ Non-recursive Quick Sort algorithm ■ Fuzzy search algorithm ■ Interrupt driven spinner routines ■ EMS interface library ■ Other interesting C tools... The program is written in standard C with some inline assembly language. It should be compatible with Microsoft C after minor modifications. TRADEMARKS ─────────────────────────────────────────────────────────────────────────── Desqview is a trademark of Quarterdeck Systems. Borland C++ is a trademark of Borland International. Windows and Microsoft C are a trademarks of Microsoft Corp. FCE version 1.0 Reference Manual Page: 11 ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ REVISION HISTORY ─────────────────────────────────────────────────────────────────────────── August 30, 1991 Version 1.0 Initial Release