> > Management of zipped sets is up to individual users and archivers. MAMEDev only
> needs
> > your new, unique ROMs
>
> wrong.
>
> obviously including old dumps with your new dumps is bad, but it makes our work
> adding a set to a driver far far easier if we get details of exactly what was dumped,
> not just what is new \ unique. The number of times I've wanted to scream at somebody
> for only listing what MAME didn't recognize, and leaving me not knowing which other
> roms were on that PCB is far too high.
>
> 'As is' (with correct names from the PCB) happens to be far better than tampered
> with.
I see what you're saying Haze. So if I include in the text file what board (in this case the CPU board) with model no. (for example, 834-5667-01) and the location of the roms (although i've named the rom dumps with their name from the label and the board location) and that these are the main (i think) 68000 code roms then that would be what you're looking for?
Also, I think i'll dump and check the other roms, just to make sure they're not different. They have the same labels as the other roms in the original zip, so I would assume they are the same, but it's probably best I dump them and check to make sure. Only thing I will say is that they are coming from a faulty board (won't boot) although I have got 2 or 3 other faulty (they have different faults) Rev. A boardsets which I could dump the roms from and compare. If they all match then I would guess they are all fine.
Edited by tb2000 (09/01/07 01:19 PM)
|
Previous 
Index 
Next 
Flat 
Re: Adding new versions of games to drivers
Reply
