Warn the user about bad CHDs

[hrydgard]

If they're not created with "chdman createdvd", they will perform really badly.

See #18798

Sorry @TotalCaesar659 and @Saramagrean , another string for you :)

[TotalCaesar659]

It's alright, I'm already used to it ;-)

[nameless1]

So, it warns about bad chds that were made with createdvd... am I missing something?

E:\Playstation Portable\PSP Backups>chdman.exe info -i "Ape Escape on the Loose (USA).chd"
chdman - MAME Compressed Hunks of Data (CHD) manager 0.262 (unknown)
Input file: Ape Escape on the Loose (USA).chd
File Version: 5
Logical size: 749,240,320 bytes
Hunk Size: 4,096 bytes
Total Hunks: 182,920
Unit Size: 2,048 bytes
Total Units: 365,840
Compression: lzma (LZMA), zlib (Deflate), huff (Huffman), flac (FLAC)
CHD size: 279,415,049 bytes
Ratio: 37.3%
SHA1: aabdebdb87d0363c4ba911dc72819dc5e014ad95
Data SHA1: 373098a849dcdc573499a28c89c92b63376e666d
Metadata: Tag='DVD ' Index=0 Length=1 bytes

Edit: Looks like it might be the updated hunksize in the test build of chdman, tried an older verson of a chd produced before 2.62 and no label...

Edit 2: It's defiantly hunksize in the test version, lowering it to 2048 (i.e. original hunksize) clears the warning... and this version of chdman wont be stable till the end of february... so just an fyi I guess.

[hrydgard]

Yup it's the hunk size. No other hunk size than 2048 makes sense to use, since that's the sector size.

[pocafon]

How can we lower the hunk size to 2048 if it's not much to ask?

[hrydgard]

@pocafon using chdman createdvd will do it automatically.

You need a recent build of chdman though, such as the one shipped with the latest build of MAME.