----------------------------------------------------------------------------------
@MSGID:
<788c610b-49bf-4d30-bbe3-87c8248de695n@googlegroups.com> 22dd77df
@REPLY:
<2c1ccdfe-80b5-4fa6-846f-7b2aeab71c70n@googlegroups.com> cda9b154
@REPLYADDR fadden <thefadden@gmail.com>
@REPLYTO 2:5075/128 fadden
@CHRS: CP866 2
@RFC: 1 0
@RFC-References:
<d68717c4-f51d-468d-8783-ba8b23b42ae2n@googlegroups.com> <37c4dd25-4807-479c-8e67-8843a2c81209n@googlegroups.com>
<aee45dcc-0acf-414c-ba8c-4b546e599b16n@googlegroups.com> 1@dont-email.me>
<15d71456-847f-49c7-a1d1-24aca0448a99n@googlegroups.com> <2c1ccdfe-80b5-4fa6-846f-7b2aeab71c70n@googlegroups.com>
@RFC-Message-ID:
<788c610b-49bf-4d30-bbe3-87c8248de695n@googlegroups.com>
@TZUTC: -0700
@PID: G2/1.0
@TID: FIDOGATE-5.12-ge4e8b94
On Tuesday, September 5, 2023 at 4:04:28 PM UTC-7, Antoine Vignau wrote:
> I`ve uploaded a couple of files at
https://www.brutaldeluxe.fr/public/applelink/
> The 2mg image has the ACU support in the II.FOLDER/ACU/ - This
is where you can pack & unpack files.
Yes, that`s it! Another victory in the fight against entropy. :-)
Thanks for tracking that down.
I ran some test files, and... it`s complicated. CRC-16/XMODEM is an
exact match for files up to 256 bytes, whether they`re SQueezed or
uncompressed (CRC is on the uncompressed data). When the original file exceeds
256 bytes, the CRCs no longer match.
I damaged some smaller files and confirmed that the errors were
detected when unpacking with ACU. However, when I damaged a larger file, I
found that ACU unpacked the file without complaint. The CRCs are different
for 256-byte and 257-byte files filled with a single value, so it`s not
stopping at 256. Some additional fiddling was inconclusive.
I`ll play with it some more, but it may just be broken.
--- G2/1.0
* Origin: usenet.network (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441