I would suggest that this is a case where there's no reason MAME shouldn't just do the right thing: if there's any kind of non-filesystem related reason a diff chd doesn't open (version mismatch, damaged header, whatever), delete it and create a new one. Obviously if some error comes back from the underlying OS (bad path or I/O error or whatever) then you'd show a message and halt.
|
Index 
Flat 
Re: Problem with WarGods chd?
Reply
