Timeline for Why does crc32 say some of my files are 'BAD'?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2022 at 23:11 | comment | added | Hubbitus | Bug reported upstream github.com/redhotpenguin/perl-Archive-Zip/issues/97 | |
| Nov 11, 2018 at 21:46 | vote | accept | EmmaV | ||
| Nov 11, 2018 at 21:45 | comment | added | EmmaV | I'll change to md5sum. | |
| Nov 11, 2018 at 21:34 | comment | added | Kusalananda♦ | @EmmaV The code of crc32 takes the ./ at the start of the filename into account when finding the hexadecimal number in the in the filename. Without ./, the regular expression does not match (since the 8-digit hex number is then not preceded by a non-hex digit) so that piece of the code that I quoted is not triggered. It's silly, really. Use another tool if you're able to. | |
| Nov 11, 2018 at 21:31 | comment | added | EmmaV | Thanks. Please can you explain why crc32 ./9836Feeding_the_dog_.mpeg results in BAD... but crc32 9836Feeding_the_dog_.mpeg doesn't? | |
| Nov 11, 2018 at 21:27 | history | edited | Kusalananda♦ | CC BY-SA 4.0 | added 306 characters in body |
| Nov 11, 2018 at 21:16 | history | edited | Kusalananda♦ | CC BY-SA 4.0 | added 90 characters in body |
| Nov 11, 2018 at 21:10 | history | answered | Kusalananda♦ | CC BY-SA 4.0 |