Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
history:newfilebase [2022/01/02 14:12] – Some clean-up for wiki display digital manhistory:newfilebase [2024/09/14 13:50] (current) – [Long Filenames] Mention characters sets and case (in)sensitivity of filenames digital man
Line 64: Line 64:
 Similarly, a maximum length of 3 character archive "types" are stored per BBS Similarly, a maximum length of 3 character archive "types" are stored per BBS
 user record (for each user's QWK packet format and temp archive preference). user record (for each user's QWK packet format and temp archive preference).
 +
 +*Note*:
 +In Synchronet v3.20, the maximum length of configurable file extensions was
 +increased from 3 to 15 characters.
  
 Since support for the viewing and extraction of several common archive formats Since support for the viewing and extraction of several common archive formats
Line 69: Line 73:
 file extensions (e.g. ".tar.gz" instead of ".tgz") may still be successfully file extensions (e.g. ".tar.gz" instead of ".tgz") may still be successfully
 extracted or viewed. extracted or viewed.
 +
 +===== Filenames =====
 +Filenames should contain US-ASCII characters only. While some methods of adding files to filebases may support adding filenames
 +that include CP437 characters, that should be avoided/discouraged. The allowed filename characters for files uploaded by users
 +is configurable by the sysop in SCFG->File Options.
 + 
 +==== Case-insensitivity ====
 +The original case (upper/lower) of alphabetic characters in filenames is stored in the filebases
 +(index and header files), however, storage of the same (duplicate) filename, differing
 +only in case, is intentionally not supported.
  
 ===== Large Files ===== ===== Large Files =====
Line 97: Line 111:
 of 10 lines or 512 total characters. There is no technical limit to the length of 10 lines or 512 total characters. There is no technical limit to the length
 of extended file descriptions, though a limit of 4000 characters imported from of extended file descriptions, though a limit of 4000 characters imported from
-description files embedded in archives (e.g. ''FILE_ID.DIZ'') is being imposed.+description files embedded in archives (e.g. ''FILE_ID.ANS'', ''FILE_ID.DIZ'', or ''DESC.SDI'') is being imposed.
  
 ===== Batches ===== ===== Batches =====
Line 137: Line 151:
 ===== Tags ===== ===== Tags =====
  
-Individual files can now be tagged for easy searching/grouping. This feature+Individual files can now be tagged (with tag-words, ala hashtags) for easy searching/grouping. This feature
 will be utilized/enhanced more in the future. will be utilized/enhanced more in the future.
  
Line 190: Line 204:
  
 Formats fully supported: Formats fully supported:
-  * zip+  * zip (not all legacy compression formats, e.g. "implode", supported)
   * 7zip   * 7zip
   * gzipped-tar   * gzipped-tar
Line 207: Line 221:
 command-line need be configured. command-line need be configured.
  
-For listing the contents of archives, the new archive.js utility script may be+For listing the contents of archives, the new ''[[dir:exec]]/archive.js'' utility script may be
 installed as a "Viewable File Type" handler for the commonly supported file installed as a "Viewable File Type" handler for the commonly supported file
-extensions by running 'jsexec archive.js install'. This installs archive.js as+extensions by running 'jsexec archive.js install'. This installs ''archive.js'' as
 a final "fall-through" viewer for "*" files (all file types). a final "fall-through" viewer for "*" files (all file types).
  
Line 250: Line 264:
 modern world. Bye bye Bi-modem. :-( modern world. Bye bye Bi-modem. :-(
  
 +===== User-to-user File Transfers =====
 +
 +While user-to-user file transfers **are** supported in the new file base, the "to" users of existing user-to-user transfers (in the "user" file area, if you have one) will not be migrated by 'upgrade_to_v319' to the new filebase.
 +
 +A quick way to check if this will impact you is to see if you have a non-zero-length ''[[dir:data]]/xfer.ixt'' file. If you do, then you have some pending user-to-user transfers that you may want to deal with.
 ===== See Also ===== ===== See Also =====
   * [[:history:|history index]]   * [[:history:|history index]]

Trace: