Well yes, since cmpro does a "chdman verify -i %1" command which would fail on deltas....it would require "chdman verify -i %1 -ip %2" where %2 gets replaced with the parent chd filename...but that's currently not supported (but on the to do list).
So...for delta the deep check won't work....but as I said: currently nobody is using delta chds since there are some open issues with them on chdman side, see https://github.com/mamedev/mame/issues/11675
Hi Roman, in the course of investigating some of the malformed delta chd creations, I tried to use cmpro to do validity checks on my existing chds and hit this problem above w/ a new commandline param needed for delta chd verification. Is that feature mature enough to release into a full build at this point? Thanks -
I wasn't aware of that. I understand the concept of a "standalone" set, which creates a non-merged set including everything, such as BIOS and devices. However, I'm curious if there are plans to offer more flexibility in the future. For instance, I prefer having a split set with separate BIOS files but not separate device(s). Take my supermodel3 emulator, for example. It's itching for a split ROM set with devices included. Sure, I could roll up my sleeves and do it manually, but where's the fun in that? Let's automate the spice!