> Thanks B2K24 for pointing that out; Version 0.145u1 to be exact.
>
> Are the other version number changes that well defined or specified at all though?
> Hence from my original post:
> 0.77u1 - New CHD format and management tools hdcomp is now chdman
> 0.80u3 - Preliminary CD-ROM support for CHDMAN.
> Would these signify a CHD version changes? If so would that be v2 and v3?
>
> Cheers.
Everything should be well defined all in the previous whatsnew.txt
Quote:
0.130u1
-------
IMPORTANT NOTE: The CHD format has undergone a change with this
release. The main reason for this change is to include some of the
key metadata into the hashes for the CHDs. This ensures that the
metadata is valid and prevents abuse.
The first impact you will find is that all of your CHD differencing
files are invalid. Just delete your "diff" directory contents
entirely.
The second impact is that all your existing CHDs will warn you that
they have incorrect hashes. This is expected. Your old CHDs should
still work fine, so if you can live with the "bad ROM" warnings, you
don't really need to do anything. However, if this bugs you or you
want to be "clean", you can update your CHDs, using this command
line:
chdman -update
for each one of your CHDs. This will take a while, but will produce
CHDs that match the new checksums posted in the drivers.
Updated CHD format to version 4. Checksums are now computed and
stored separately for raw data and metadata, and metadata is now
checksummed by default. [Aaron Giles]
Updated chdman to support a generic metadata addition system:
chdman -addmetatext []
chdman -addmetabin []
[Aaron Giles]
Changed the CHD verify interfaces to pass back a structure containing
all the necessary data for verification and fixing. [Aaron Giles]
|
Index 
Flat 
Re: Timeline of CHD versions? [Updated]
Reply
