Romcenter

Yes, Download Mage (http://www.dlmage.com) is excellent and I've used it for several years now. Small and very effective.

Yes, use the split-merged supplement (the name must match your MAME set). The dats are separate because they are different emulators. It provides more flexibility for people.

You are 5 versions behind then (v2.6 is the latest, you are on v2.1).

Try the laest version as it does not require xml2info.exe installed on your system.

Many of the Neo-Geo ROMs were redumped this year. The good news is that they can be rebuilt. From the following page, use the link on the line: 2 March 2003 - Updated for WinKawaks v1.49. Use ROMBuild [MAME v0.80 Special] to build the new Neo-Geo ROMs. http://www.logiqx.com/Dats/WinKawaks/WinKawaks....

I presume that you are talking about the ones that are for emulators such as Nebula, etc? They create ROM sets that in addition to a good MAME set are all that you need for a particular emulator (i.e. by defining two ROM paths in the emulator; one for MAME ROMs, one for supplement ROMs). Examples of...

You almost certainly don't have the correct equipment to undertake the process of 'dumping' ROMs. Your only option is to find them on the internet. Your favorite search engine will help you find them.

It seems like you have sorted your own problem before I saw it. :) Anyway, just to clarify something about XML vs. Listinfo: Listinfo was created many years ago and XML was introduced slightly over a year ago as a replacement. There was a long period during which both options were available, allowin...

It is good to know that v2.5 is working well for people.

I am still interested to know what was wrong with some people's XML that xml2info.exe had a problem with it though! If anyone has XML that doesn't work with xml2info.exe then I'd like to have a look at it.

Just replace the old datutil.exe in your RomCenter directory with the new one, no need for a new version of RomCenter.

You can also delete xml2info.exe if you like (wherever you installed it).

The filesize of the xml2info file is 132KB Why does the size of exe matter? I was asking about the size of the XML and wanted to be sure that it was a file of many MB rather than an empty/incomplete file. Anyway, it doesn't matter now because my XML parser is not strict like xml2info is and appears...

I have just released DatUtil v2.5 which has it's own internal XML parser (so that xml2info.exe is not needed anymore).

You can find it at http://www.logiqx.com

Please let me know if it works ok and if it solves any existing problems that you have with MAME imports.

it appears as though the xml2info.exe is corrupt. I've compiled 3 times with fresh Mingw packages (from M32FX site) and dlownloaded fresh sources. It just simply won't output a Dat at all. You misunderstood me, it isn't xml2info.exe that will be corrupt. It will be the -listxml output that is bad! ...

Sorry but I have no idea. It's going to boil down to the XML being bad I think. Did you compile MAME yourself or download it? If compiling yourself, make sure that you do a clean compile first (either using 'make clean' or deleting the 'obj' directory). If that doesn't work, see what xml2info does o...

I have created a proper data file for Nebula Jukebox now (including MAME supplements) and also updated the Nebula one slightly.

If anyone is interested in how these are created and validated, I have described the process in the Dat FAQs section of logiqx.com.

Logiqx

If you want to identify ROMs then you could always try using ZIPIdent too as that supports all formats of DatUtil and my other tools (RomCenter, CMPro, XML, etc). You've probably thought of that already though.

It's good to hear that you like DatUtil.

Sorry but its not intended for what you are trying to do. MAMEDiff has two purposes: 1) Tell you what has changed in a MAME release. This is a game level comparison and renames can be spotted because the comparison is intelligent (it actually does this with CRCs for the games themselves). The standa...

Then the problem is that your ROMs are not incorrect and need fixing. RomCenter may be able to do some of that fixing by renaming ZIPs and files inside them but some problems may require some re-downloading. Anyway, if you learn how to use RomCenter's fixing options then the datafile will be able to...

Out of interest, what were the builds that you originally linked to and what is different about them?

Sorry but ROM requests are not allowed on this board.

It is the other way around... you get a data file and then find the ROMs that it specifies. Which data files are you trying to use?

That sounds like a RomCenter bug then.

sg-01-0 has the same CRC as one of the resource ROMs but shootgal does not use the resource. The ROM must go in shootgal.zip because MAME will not load it from the resource.

I think it will be far simpler for you to include DatUtil and xml2info with RomCenter. Having two extra steps in the install could make life difficult for users. ;) Now that you mention the source, it is really small now so it would be nice if you can include the whole package. Would it be possible ...

It sounds like you have got ROMs incorrectly named then. That kind of thing shows up more visibly in CMPro. The only difference that there should be is for galpanib, jdreddb, natodefa and vapotrp. Those 4 games don't actually have any ROMs of their own (all come from the parent) but CMPro wants/crea...

To be honest, I'd prefer not to distribute xm2info with my tools as I don't want to end up doing re-releases for xml2info updates or have lots of copies of xml2info on my machine. Most users of my tools can be considered quite technical so they will do something like putting xml2info in their path a...

You should look a bit harder. There was a MAME v0.84 datafile posted in this forum, listed in the RomCenter arcade datafiles section and on my site.

I notice that it was generated with DatUtil 2.0 but says 'Generated with DatUtil 1.32' in the comment. ;) It's nice that DatUtil 2.0 is now released because by default it does everything that I used to do in steps: 1) Apply old fix-merging twice (the simple algorithm meant it needed running twice). ...

Well done. Just a couple of clarifiers for everyone: 1) Moving the space by the redirection character isn't really necessary. I'd just replace 'info' with 'xml<space>'. 2) You can still pass -m to DatUtil (it just won't do anything with it). So, in theory you just need a 4 character change to the ex...

Ah, I know why... I did not think my idea through fully! You need a new version of RomCenter because it currently runs 'mame -listinfo' and uses DatUtil to interpret the output. RomCenter now needs to run 'mame -listxml' and use DatUtil to interpret it ('mame -listinfo' does absolutely nothing now)....

MAME v0.84 has just been released and listinfo support has now been removed. You will therefore need the new version of DatUtil to handle the XML output of MAME. 1) Download DatUtil v2.0 from my website and copy datutil.exe into your RomCenter folder. 2) You also need to copy xml2info.exe into your ...

I tried sending you an e-mail at the weekend but I think it is probably lost amongst the spam.