On Thu, Mar 28, 2002 at 12:51:47PM +0100, Matthias Saou wrote:
> Once upon a time, Nathan wrote :
>
> > Merged means roms don't repeat in the child set if the parent set uses
> > those roms as well. Consider the parent set "puckman" and a clone such
> > as "pacman". Before merging
> >
> > puckman: namcopac.6e namcopac.6f namcopac.6h namcopac.6j
> > pacman.5e pacman.5f 82s123.7f 82s126.4a 82s126.1m 82s126.3m
> >
> > pacman: 82s123.7f 82s126.4a 82s126.1m 82s126.3m
> > pacman.6e pacman.6f pacman.6h pacman.6j pacman.5e pacman.5f
> >
> > And after merging
> >
> > puckman: namcopac.6e namcopac.6f namcopac.6h namcopac.6j
> > pacman.5e pacman.5f 82s123.7f 82s126.4a 82s126.1m 82s126.3m
> >
> > pacman: pacman.6e pacman.6f pacman.6h pacman.6j
> >
> > Merged sets reduce disk usage.
>
> How is this merging done? Is it xmame that tells who can (or is supposed
> to) be the parent of who?
Romulan gets all the parent information from "xmame -listinfo".
> I've tried to used romalizer yesterday for the
> first time... seems like it doesn't like me having to give it the full path
> to xmame.xgl to work, and always gives an error message. But I have been
> able to see with it (or maybe another of the tools, I played with lots ;-))
> that some zip files I have contain duplicate files, thus merging them could
> be a good idea.
I'm not sure how romalizer works, but merging is definitely a good idea.
--
The more I know about the WIN32 API the more I dislike it. It is complex and
for the most part poorly designed, inconsistent, and poorly documented.
- David Korn
_______________________________________________
Xmame mailing list
[EMAIL PROTECTED]
http://toybox.twisted.org.uk/mailman/listinfo/xmame
