To compress or to binscii this is the question [message #373781] |
Wed, 19 September 2018 23:36 |
|
Originally posted by: Anthony Adverse
In the good ol' days for me, I used to just archive stuff with shrinkit and bang it on the BBS which anyone could download and presto away you went. In this day and age is this "safe" in terms of transfer errors, or should things still be compressed and binscii'd for choice?
Just thinking about what to do with the current BBS versions file archives.
A
|
|
|
Re: To compress or to binscii this is the question [message #373782 is a reply to message #373781] |
Thu, 20 September 2018 00:39 |
|
Originally posted by: fadden
On Wednesday, September 19, 2018 at 8:36:36 PM UTC-7, Anthony Adverse wrote:
> In the good ol' days for me, I used to just archive stuff with shrinkit and bang it on the BBS which anyone could download and presto away you went. In this day and age is this "safe" in terms of transfer errors, or should things still be compressed and binscii'd for choice?
BinSCII is only useful if you're transferring files through a mechanism that isn't 8-bit clean, like classic Usenet. Unless you're planning to post stuff on comp.binaries.apple2, there's no need for base64 encoding.
The contents of ShrinkIt archives are CRCed, so any errors will be noticeable. (If you want to test an archive, NuLib2 and CiderPress have a test feature. Or just try extracting everything.)
|
|
|
Re: To compress or to binscii this is the question [message #373784 is a reply to message #373782] |
Thu, 20 September 2018 01:37 |
|
Originally posted by: Anthony Adverse
> BinSCII is only useful if you're transferring files through a mechanism that >isn't 8-bit clean, like classic Usenet. Unless you're planning to post stuff on >comp.binaries.apple2, there's no need for base64 encoding.
Ta.
Well I guess everything out there is likely to be 8bit clean.. Only transfer types are likely to be either z-modem out of the BBS itself, or FTP... If I open that up. Z-modem over tcp seems to be pretty quick too :)
A
|
|
|