> > > Because all CHD's have no extension in the drivers? ;-)
> >
> >
> > exactly
>
> I still think this change is a poor design choice by the MAME Dev's. I see no
> reason why the disk tag doesn't work in the same way as the rom tag where rom
> names can be anything and front ends don't have to assume what it is. Now we
> have to assume that the token following name of every disk line needs a .chd
> appended. What if when cd images are implemented they wanted to name cd images
> .? It seems limiting and requires front end using the listinfo interface assume
> too much. So much for consistency.
>
> Cheers,
> Tim
>

Well...I think it's alright to remove all .chd extension from the driver (and so from -listinfo). The files themselves of course KEEP .chd. Well...You can see .chd as a filetype and so it can be removed from the driver information (though it should be done with samples, too). CD Images will be chd since, chd = compressed hunks of data and not compressed harddisk.

Roman Scherzer
ClrMamePro