Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / UPCHK700.ZIP / UPSETUP.HLP < prev next >

Wrap

INI File | 1996-03-07 | 33.5 KB | 905 lines

[]INTRO Welcome to UpCheck, the premium upload scanning package. This setup program has context sensitive help, so if you get stuck while configuring this package, press "F1" from just about anywhere and a help screen will be presented for you. The setup program is also equipped with a configuration testing feature, so if you want to quickly see if your configuration is most likely correct, simply select the "Test Configuration" option from the main menu. Also, be sure to check out the companion utility called UPUTILS.EXE This package has many many features that can make the maintenance of your file collection a breeze. I hope you enjoy this package. Pete Rocca Multiboard Communications Centre support@multiboard.com []SYSTEM INFORMATION Sysop & System name ■ This is where you place your sysop name and your system name. Serial & Registration ■ When you register, this is where you place your registration information to active the registered features. Please note that all four pieces of information must match your registration key information exactly, including upper and lowercase. []FILE INFORMATION Duplicate database ■ This is the full path and file name of the file that stores the duplicate file signatures. This file should not be manually edited as it is handled by Upcheck. Badfiles database ■ This is the full path and file name of the file that contains a list of files that are unwanted in recompressed archives. This is the file that you would place the names of unwanted BBS advertisements and other such files to be removed before Upcheck recompresses the archive. Statistics file ■ This is the full path and file name of the file that stores the information on the number of passed and failed files. This file should not be manually edited as it is handled by Upcheck. Log file ■ This is the full path and file name of the log file that should be created. The log file will contain all the information about files that are passed and failed, and who uploaded them. You can point your log file to add to your main BBS log file if you wish. Advertising file ■ This is the file that you want copied into a passing archive. For example an advertisement file or such. If you do not wish to add an advertisement file, then simply leave this field blank. Advertising file .. copy to {+} ■ This is the name that you want your added file to be called in the archive. An example might be that you wanted the file copied from "C:\BBS\TEXT\BBS.AD" into the newly created archive and call it "CALLHERE.TXT". ■ When unregistered, this name is forced "CALLME.BBS" Commenting file ■ This is the name of the file that you want as your ZIP file comment. If you do not want ZIP file commenting, then simply leave this field blank. Semaphore path ■ When posting online failure messages in RemoteAccess mode, you should point this path to the same path as you have setup in the "RACONFIG.System.Paths.Semaphore" field. UpUtils work path ■ When extracting and working with archives in UpUtils, you can specify a work path that it should use. This is good for using a local drive for faster access when running on a network. Description files ■ UpUtils has a useful feature called "YANK". This is the ability to search standard text files for descriptions in case the file does not have a FILE_ID.DIZ, or any other self-description type files within it. ■ If the "/Y /I" parameters of UpUtils are on, then it will scan these text files for a description that matches the filename and then insert it into the file database. ■ This is useful for downloading files from other systems, as you can insert descriptions from capture logs, FILE_ID.1 type descriptions or another BBS's filelist. ■ Line noise and most other nonsense is filtered out. Please note that although this WILL save you much time and effort, occasionally you may get a wrong description. The reason for this is that there might be a file called STAR.ZIP on one system, that is a completely different file than a STAR.ZIP on another system. ■ The file names entered in these five slots will be the textfiles that UpUtils looks in to search for a matching description. For more information read the "Searching in text for descriptions" section of the documentation. []EXTERNAL SELECT Decompression ■ In this section you will be able to define all of the command line options for your external decompression programs. Recompression ■ In this section you will be able to define all of the command line options for your external compression programs. Scanning ■ In this section you will be able to define your virus scanning program, as well as options on when Upcheck should call it. []EXTERNAL 1 These are the external packages that will be used to decompress archives that are processed. They should all exist on your system where stated and have all the correct and valid command line parameters. If you do not have the decompression program required to decompress a certain type of archive, UpCheck will not be able to handle that type of file should it be uploaded. In addition, if you define the GUS unpacker and specify in the Control Options to execute GUS on unknown archive types, then this program will be called when UpCheck encounters an unknown archive type. []EXTERNAL 2 These are the external packages that will be used to recompress archives that have been processed. They should all exist on your system (or at least the ones you will use to recompress files) where stated and have all the correct and valid command line parameters. []EXTERNAL 3 Scan ■ This is the full path and file name as well as the parameters for your scanning program. ■ If you specify "OFF" without the quotes and in uppercase, UpCheck will bypass the virus scanning. Type ■ If your scanning program needs to be called in each subdirectory created in the archive, then you should select "Call scanner in each subdirectory", otherwise if the scanning program can auto- matically scan subdirectories, then you should select "Scanner scans subdirectories itself" []LIMITING OPTIONS Maximum file age in days ■ This is the maximum number of days old that the archive contents can be before being considered too old. Maximum percent of old files ■ This is the percentage of files that can be considered too old before considering the entire archive to be too old. Maximum percent of duplicates (Files) ■ This is the percentage of files that can be found to be duplicates before the entire archive is considered to be a duplicate. ■ This is good at about 80% usually as it allows room for advertising files that you may not have marked in your bad files file, and the next feature will usually do the better test. Maximum percent of duplicates (Size) ■ This is the percentage of size that can be found to be duplicates before the entire archive is considered to be a duplicate. ■ This is good at a value around 25%. This is different over the other duplicate check as it works like this... JUNKY!.BBS 1000 bytes - dupe junk file README.HA 1000 bytes - dupe junk file MISSED.IT 1000 bytes - dupe junk file VALUED.EXE 70000 bytes - real program If this had been the contents of the archive the percentage of files duped would have been 75%, but the duped bytes only about 5% Has you can see, that with good setting for both files and bytes, you can be sure that rarely will you get a duplicate file passed, nor fail an original one. Minimum size to record ■ Any files smaller that this size are not to be included in any of the checks or the data base of signatures. ■ For example, if this value is 1000 then any files that smaller than 1000 bytes will be skipped during processing. This is used for people who have a large file system and would rather save the space and time of a smaller duplicate database then to concern themselves with watching for small duplicate files. This can also be set to a value near 2000 if you find that a lot of BBS ads get passed you, and you don't want them to effect the users chances of failing uploads. Allow RIP graphics emulation ■ When set to yes, UpCheck will auto-detect if a user has RIP capabilities and display RIP graphics to them. Minimum baud for ANSI graphics ■ If you feel that the display of UpCheck is too slow at low speeds, you can specify the lowest possible baud rate that can get the ANSI display. If you put 2401 here, only users that are calling at speeds greater than 2400 baud will be able to get the ANSI screen otherwise they'll get the ASCII display. Minimum graphics resolution {+} ■ You can specify the minimum resolution that an uploaded graphic can be. If the GIF/JPG is not within the specified range, it will fail due to "unsupported graphic resolution" Maximum graphics resolution {+} ■ You can specify the maximum resolution that an uploaded graphic can be. As above, if it is not in range, it will fail the file. []CONTROL OPTIONS Unsupported file types ■ When set to "Continue processing", any files that cannot be determined as being an ARC/ARJ/LHA/LZH/PAK/ZOO/ZIP/UC2/SQZ/GIF JPG/SFX type file will be checked for date/duplicate validity. ■ When set to "Fail immediately", unknown archive types will be failed. This is a good way to prevent files being uploaded in an uncompressed or unsupported format. ■ When set to "Execute GUS", the command line in the decompression section labeled "GUS" will be called on the archive to attempt to unpack it. If it can be unpacked processing will continue as normal otherwise the file will be failed. Allow non-self-extracting EXE files ■ If a file with an .EXE extension is processed and not a self- extracting file, you can have it failed by selecting "No". This will stop people from uploading just the EXE of a file that should be archived in its complete form. Extract and scan embedded archives ■ When set to yes, UpCheck will extract the embedded archives found within the main archive and process them with date, duplicate and virus scanning for each level found. Recompression type ■ You can have UpCheck recompress the archive file when done in whatever format you wish. If you select "Same" it will use the same format as the original archive. Recompress self-extracting EXE files ■ If you wish to recompress self-extracting files into the format defined in "Recompression type" then select yes. Recompress same type archives ■ If you wish to recompress files that are of the same type that come in then select yes. For example, if your recompression type is ZIP and a ZIP file is uploaded, you can avoid having UpCheck recompress it by selecting no. ■ On a side note, not recompressing the file will save processing time, however if UpCheck does not recompress the file, it can not perform a number of its functions. Some of those include the removal of files in the UPCHECK.BAD file as well as the addition of your own advertising file if specified. Keep original archive name ■ When set to yes, UpCheck will not rename the archive with the proper extension if the original one is invalid. For example a ZIP file with the extension Z01 would not be renamed back to ZIP ■ This cannot selected when "Recompression type" is not "Same" Clean high-ascii from descriptions ■ If you choose, UpCheck will strip all of the high-ascii characters from imported descriptions. Security level to force pass {+} ■ If this is not set to zero, then any user who has this security level or higher will always get credited for the file. If for instance, your co-sysop and registered users upload you something, even if it fails the test, it will say "Thank you for the upload" and let the BBS give them the credit. ■ If you specify, UpCheck will still send you a message, informing you of the fail. Security flag to force pass {+} ■ This is similar to the security to force a pass, but it uses the user's flag settings instead. Remember that the only supported drop file that supports the flag settings is the RemoteAccess 2.x EXITINFO.BBS file. Continue process after old date ■ If after a file fails the age check, you might want to continue processing to see if it fails any of the other checks. A good reason for this might be if you wanted to determine if the file was an "oldie but goodie" file, but needed to know if it was also a duplicate. Redate archive file date ■ If you wish to redate the new archive file with anything other than the current date and time, you can select from a number of options here. Swapping method ■ Here you can specify what type of media and which order you want to use for swapping to when loading external programs. This is to increase the amount of conventional memory that will be available to the virus scanner and the archivers. ■ XMS/EMS and your HDD are all valid media types. If swapping to disk, UpCheck will look for a TMP or TEMP enviroment variable and use that path for its swapfile, otherwise the current path is used. ■ Remember that your mode should always include HDD (disk) support in case of a lack of EMS/XMS available at the time of scanning. Define bad extensions {+} ■ Here you can specify extensions that you do not want to be able to be uploaded. If a file uploaded consists of nothing but these types of files the archive will be failed. If the file contains a fair amount of these files, it will be passed, but you can specify in the "Extended Options" to warn you of such a file. ■ For example, if you didn't want graphics files to be able to be credited, you could set the extensions to BMP/RLE/GIF/PCX/JPG/PIC and even if a user uploaded these files in an archive it would detect them and take action accordingly. []EXTENDED SELECT Extended options ■ You can select which BBS framework UpCheck should integrate into... * RemoteAccess 1.x * RemoteAccess 2.x * PCBoard 15.x * ProBoard * Generic FILES.BBS * TriBBS * Custom file format ■ The integration includes support for posting messages to the sysop and users if selected, as well as inserting the file description into the file listing or file database. []EXTENDED 1 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Use path matchup file ■ Normally Upcheck will use the FILES.BBS file located in the same directory as the file that was processed. If for some reason the FILES.BBS files will be located in different directories, then you should setup a matchup file that matches directories with the appropriate file to update. For more information about matchup files, please see the documentation. Use path matchup file .. file name ■ This is the file name of the matchup file if you are using one. Hudson message path ■ This is the full path to the Hudson message base. This is where your MSGTXT.BBS file is located. Hudson area number ■ This is the board number you want Upcheck to post its messages into. Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. Send online message ■ If you wish to send the user an online message immediately, you can do so by selecting yes here. []EXTENDED 2 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Path to FILES.RA ■ This is the path to your FILES.RA configuration file. Path to file database ■ This is the path to your RA 2.x FDB. This is the directory that will have your IDX, HDR and TXT subdirectories in it. Message format ■ This is the message format you wish Upcheck to use when posting its messages. Message path ■ For Hudson, this is the path to your MSGTXT.BBS file. For JAM, this is the directory that holds the JAM message base you wish to post to. Message board ■ For Hudson, this is the message board you wish to post to. It should be in the range of 1 to 200. For JAM, this is the filename of the JAM base you are posting to. For example, if you were posting to the JAM base of "C:\RA\JAM\PRIVATE", then "PRIVATE" would be the message board, and "C:\RA\JAM\" would be the message path. Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. Send online message ■ If you wish to send the user an online message immediately, you can do so by selecting yes here. []EXTENDED 3 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Use path matchup file ■ Normally Upcheck will use the file listing name file located in the same directory as the file that was processed. If for some reason the file listing will be located in a different directorys, then you should setup a matchup file that matches directories with the appropriate file to update. For more information about matchup files, please see the documentation. Use path matchup file .. matchup file name ■ This is the file name of the matchup file if you are using one. Use path matchup file .. file list name ■ This is the file name of listing file to create. For example, if you are writing to the file "C:\PCB\DIR0" then "DIR0" would be the file list name. Message path ■ This is the path that holds your message text file. Message board ■ This is the filename of the message base you are posting to. For example, if you were posting to "C:\PCB\GENERAL\MSG", then "MSG" would be the message board, and "C:\PCB\GENERAL\" would be the message path. Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. []EXTENDED 4 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Use path matchup file ■ Normally Upcheck will use the FILES.BBS file located in the same directory as the file that was processed. If for some reason the FILES.BBS files will be located in different directories, then you should setup a matchup file that matches directories with the appropriate file to update. For more information about matchup files, please see the documentation. Use path matchup file .. file name ■ This is the file name of the matchup file if you are using one. Message format ■ This is the message format you wish Upcheck to use when posting its messages. Message path ■ For Hudson, this is the path to your MSGTXT.BBS file. For JAM, this is the directory that holds the JAM message base you wish to post to. Message board ■ For Hudson, this is the message board you wish to post to. It should be in the range of 1 to 200. For JAM, this is the filename of the JAM base you are posting to. For example, if you were posting to the JAM base of "C:\RA\JAM\PRIVATE", then "PRIVATE" would be the message board, and "C:\RA\JAM\" would be the message path. Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. []EXTENDED 5 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Use path matchup file ■ Normally Upcheck will use the file listing name file located in the same directory as the file that was processed. If for some reason the file listing will be located in a different directorys, then you should setup a matchup file that matches directories with the appropriate file to update. For more information about matchup files, please see the documentation. Use path matchup file .. matchup file name ■ This is the file name of the matchup file if you are using one. Use path matchup file .. file list name ■ This is the file name of listing file to create. For example, if you are writing to the file "C:\BBS\FILES.BBS" then "FILES.BBS" would be the file list name. Message format ■ This is the message format you wish Upcheck to use when posting its messages. Message path/program & board ■ Hudson: path = path to the MSGTXT.BBS file board = board number to post to in the range of 1-200 JAM: path = path of JAM base board = filename of JAM base PCBoard: path = path of message text file board = filename of message text file External: path = full path/filename of the external program to call to post the message. If simply called, Upcheck will add the filename to post, followed by the user name. For example: POSTIT.BAT Might end up: POSTIT.BAT c:\44634.TMP Pete Rocca Optionally, you can use the %TO, %FROM and %FILE parameter metastrings to customize where the parameters are placed. For example: POSTIT.BAT -TO "%TO" -FILE %FILE Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. []EXTENDED 6 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Use path matchup file ■ Normally Upcheck will use the file listing name file located in the same directory as the file that was processed. If for some reason the file listing will be located in a different directorys, then you should setup a matchup file that matches directories with the appropriate file to update. For more information about matchup files, please see the documentation. Use path matchup file .. matchup file name ■ This is the file name of the matchup file if you are using one. Use path matchup file .. file list name ■ This is the file name of listing file to create. For example, if you are writing to the file "C:\BBS\FILES.LST" then "FILES.LST" would be the file list name. Message program ■ This is the filename and any parameters of the file to run that will post your messages. It is suggested that you run a batch file in order to get the most flexibility out of where to place the parameters for your 3rd party message posting application. If simply called Upcheck will add the filename to post, followed by the user name. For example: POSTIT.BAT Might end up: POSTIT.BAT c:\44634.TMP Pete Rocca Optionally, you can use the %TO, %FROM and %FILE parameter metastrings to customize where the parameters are placed. For example: POSTIT.BAT -TO "%TO" -FILE %FILE Might end up: POSTIT.BAT -TO "Pete Rocca" -FILE c:\44634.TMP Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. []EXTENDED 7 Insert description ■ If you wish Upcheck to attempt to find and insert the FILE_ID.DIZ or DESC.SDI/DESC.SDN description into your FILES.BBS, then select yes here. Add uploader name, archive information and graphics information ■ If you wish Upcheck to add this extended information to the file description, you can select for it to do so. For the graphics information, it will insert the resolution of GIF and JPG files. Use path matchup file ■ Normally Upcheck will use the file listing name file located in the same directory as the file that was processed. If for some reason the file listing will be located in a different directorys, then you should setup a matchup file that matches directories with the appropriate file to update. For more information about matchup files, please see the documentation. Use path matchup file .. matchup file name ■ This is the file name of the matchup file if you are using one. Use path matchup file .. file list name ■ This is the file name of listing file to create. For example, if you are writing to the file "C:\BBS\FILES.BBS" then "FILES.BBS" would be the file list name. Message format ■ This is the message format you wish Upcheck to use when posting its messages. Message path/program & board ■ Hudson: path = path to the MSGTXT.BBS file board = board number to post to in the range of 1-200 JAM: path = path of JAM base board = filename of JAM base PCBoard: path = path of message text file board = filename of message text file External: path = full path/filename of the external program to call to post the message. If simply called, Upcheck will add the filename to post, followed by the user name. For example: POSTIT.BAT Might end up: POSTIT.BAT c:\44634.TMP Pete Rocca Optionally, you can use the %TO, %FROM and %FILE parameter metastrings to customize where the parameters are placed. For example: POSTIT.BAT -TO "%TO" -FILE %FILE Send user message ■ If you want Upcheck to post the user a "failure" message when they upload a file that fails the testing, then select yes. Send sysop message ■ If you want Upcheck to post the sysop about a user's failed upload then select yes. Send personal reply ■ Normally the messages posted by Upcheck are addressed "from" Upcheck, however if you want the messages to come from the sysop and user names directly, you can do so. This usually makes it easier to respond to the user/sysop if you choose to. Custom editing ■ Here you can define your own text based file format by answering a few simple questions Upcheck will ask you. []MODIFY STATISTICS Bytes read and written ■ Bytes read is the total of the original file sizes of the passed archives before recompression. The bytes written value is the total after compression, therefore you can tell how much you have saved using a new compression program, and removing unwanted files. Passed, errored, old, virus, duplicate files ■ This is the total number of files that have failed, categorized by their failure reason. Write these statistics to disk ■ If you modify these statistics, they will not be updated to disk until you select this option. []