707
edits
ROM images: Difference between revisions
Jump to navigation
Jump to search
Swap MD5 and SHA1 in example commands
(→Spectrum peripherals: Swap MD5 and SHA1) |
(Swap MD5 and SHA1 in example commands) |
||
| Line 5: | Line 5: | ||
FCS32 and SHA1 are given here as these are what MESS uses. FCS32 in this instance refers to the 32-bit CRC standardised as ISO 3309, ISO/IEC 13239:2002 and ITU-T V.42, most notably used as the Ethernet Frame Check Sequence (FCS), which has a polynomial representation of 0x04C11DB7 in normal form. It is also used for zip and gzip files, and within UDI disk images. | FCS32 and SHA1 are given here as these are what MESS uses. FCS32 in this instance refers to the 32-bit CRC standardised as ISO 3309, ISO/IEC 13239:2002 and ITU-T V.42, most notably used as the Ethernet Frame Check Sequence (FCS), which has a polynomial representation of 0x04C11DB7 in normal form. It is also used for zip and gzip files, and within UDI disk images. | ||
On Unix-like systems, Jacksum will produce an FCS32 sum when using | On Unix-like systems, Jacksum will produce an FCS32 sum when using: | ||
jacksum -x -a fcs32 FILES | |||
and rhash will do so when using: | |||
rhash --lowercase -C FILES | |||
To produce a line similar to that needed for this article, with minimal editing, one can use: | |||
jacksum -a crc32+sha1+md5 -F "|#FILENAME||#FILESIZE||#CHECKSUM{0}||#CHECKSUM{1}||#CHECKSUM{2}" FILES | |||
or: | |||
rhash -p "|%20f||%s||%c||%h||%m\n" FILES | |||
Note that checksums can be freely shared on the Internet without concern over copyright, as these simply provide a mechanism for determining validity of ROM dumps that you already have. | Note that checksums can be freely shared on the Internet without concern over copyright, as these simply provide a mechanism for determining validity of ROM dumps that you already have. | ||