> OK thanks Roman - it was the 'can't access file' bit that threw me
>

well...that's what the chd routine returns....hmm..maybe the file is locked by a different task. But then this should also happen when you don't run a full chd integrity check, so I assume the chd is indeed corrupt...

You can try a
chdman -verify 929jbb02.chd
to see the result of chdman.


Roman Scherzer