This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
file_transfers [2022/04/30 09:50] – admin | file_transfers [2022/04/30 10:15] (current) – admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== File Transfer ====== | ====== File Transfer ====== | ||
- | Minimum Upload Space ........ Space needed on the upload drive for | + | **Minimum Upload Space** |
- | uploads to be allowed (in Kb). | + | |
- | Download Hours .............. Pressing < | + | Space needed |
- | window which allows you to specify during | + | |
- | what hours a user can download files from | + | |
- | your system. | + | |
- | each day of the week, in half hour | + | |
- | increments. | + | |
- | flag in the user's record will override any | + | |
- | hours you may have set here. | + | |
- | Check Duplicate Uploads ..... If this option is set to " | + | **Download Hours** |
- | Menu Function 33 (Upload a File) will check | + | |
- | upon completion of any upload(s) for | + | |
- | duplicate files. | + | |
- | for duplicates prior to any upload(s) due | + | |
- | to any batch protocols the user may choose | + | |
- | to use. Use this option along with the | + | |
- | next two options (below) to decide how you | + | |
- | want your system to deal with any duplicate | + | |
- | files your users may upload. | + | |
- | Kill Duplicate Uploads ...... If set to " | + | Pressing < |
- | that already exists on your system | + | what hours a user can download files from your system. Hours are selectable for |
- | file index) then ProBoard will delete | + | each day of the week, in half hour increments. |
- | file from your upload directory (as | + | flag in the user's record will override any hours you may have set here. |
- | specified | + | |
- | menu entry or in PROCFG). | + | |
- | save the duplicate files rather than have | + | |
- | them deleted, | + | |
- | When does ProBoard delete the file? Great | + | |
- | question!! | + | |
- | ProBoard will delete any duplicate files | + | **Check Duplicate Uploads** |
- | immediately after checking for dupes, even | + | |
- | before the user is prompted to enter a file | + | |
- | description, | + | |
- | this option to " | + | |
- | You can also create | + | If this option is set to " |
- | | + | upon completion of any upload(s) for duplicate files. |
- | they do upload | + | for duplicates prior to any upload(s) due to any batch protocols the user may choose |
- | that ProBoard will display must be named | + | to use. Use this option along with the next two options (below) to decide how you |
+ | want your system to deal with any duplicate files your users may upload. | ||
- | ───────────────────────────────────────────────────────────────────────────── | + | **Kill Duplicate Uploads** |
- | | + | |
- | DUPESFND.A?? | + | |
- | " | + | |
- | C: | + | |
- | Ignore File Extensions ...... | + | If set to " |
- | ProBoard's duplicate checking | + | file index) then ProBoard will delete |
- | consider NEWFILE.ZIP and NEWFILE.ARJ to be | + | specified in the data line of your upload menu entry or in PROCFG). If you want to |
- | | + | save the duplicate files rather than have them deleted, set this option |
- | | + | When does ProBoard delete the file? Great question!! |
- | user uploads NEWFILE.ARJ, ProBoard will | + | |
- | | + | |
- | Be sure you understand this before | + | ProBoard will delete any duplicate files immediately after checking for dupes, even |
- | this option to " | + | before |
+ | this option to " | ||
- | Upload scanner .............. When uploads are received, ProBoard will | + | You can also create a text file to be displayed to your users in the event that |
- | run the command line specified here FOR | + | they do upload duplicate files. The file that ProBoard |
- | EACH FILE. The macro @< | + | |
- | replaced by the full name of the file to be | + | |
- | scanned (including drive and directory). | + | |
- | When the file is suspicious, the upload | + | |
- | scanner should do one of 2 things: | + | |
- | - Return with an errorlevel different | + | |
- | from 0. | + | |
- | - Create a semaphore file with a name | + | |
- | specified | + | |
- | If the file failed the virus scan (so if a | + | **Ignore File Extensions** |
- | semaphore file was created or an errorlevel | + | |
- | was returned), ProBoard will perform an | + | |
- | action on the file (defined in " | + | |
- | - None : No action (but upload | + | If this option |
- | | + | consider NEWFILE.ZIP and NEWFILE.ARJ |
+ | on your hard drive or CD-ROM drive and a user uploads NEWFILE.ARJ, | ||
+ | consider this to be a duplicate upload. | ||
- | - Move : The file is moved to a different | + | Be sure you understand this before setting this option |
- | area (specified in "bad file | + | |
- | area") | + | |
- | - Delete: The file is deleted | + | **Upload scanner** |
- | If you don't want to use the upload | + | When uploads are received, ProBoard will run the command line specified here FOR |
- | scanner, just leave the command line for | + | EACH FILE. The macro @< |
- | the upload scanner | + | scanned (including drive and directory). When the file is suspicious, |
+ | scanner | ||
- | Add Uploaders Name .......... If set to " | + | |
- | to FILES.BBS | + | Create a semaphore |
- | FILES.BBS. | + | |
+ | If the file failed the virus scan (so if a semaphore file was created or an errorlevel | ||
+ | was returned), ProBoard will perform an action on the file (defined in " | ||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | If you don't want to use the upload scanner, just leave the command line for | ||
+ | the upload scanner blank. | ||
+ | |||
+ | **Add Uploaders Name to FILES.BBS** | ||
+ | |||
+ | If set to " | ||
+ | FILES.BBS. |