I tried NES Cart Database's tool, but the converted are not recognized by the new No-Intro NES(20070407). Also it is for the USA roms only.
Is there a good way to convert iNes headered NES/FC roms to Unif format, and still be recognized by the NoIntro dats?
===============================================
Re: What would be best way to convert iNes to Unif? \ Elbart on 9th April 2007, 22:09 wrote:
1) Why would you want to convert them?Is there a good way to convert iNes headered NES/FC roms to Unif format, and still be recognized by the NoIntro dats?
2) And yes, there are several tools out there, but then they wouldn't be recognized by the dats unless you add a rule to the header-xml to ignore the unif-header for these converted roms.
===============================================
Re: What would be best way to convert iNes to Unif? \ kshin98 on 10th April 2007, 01:02 wrote:
1) Because Unif is supposed to be a better format to replace the old iNes header. It is said to be more accurate, and to have more info about the cart. I would like to have all my nes roms converted to Unif, and recognized by the No-Intro dat.
2) Y~K's xml header seems not to support the UNIF. I may wait ultil someone writes it. What would be the best tool to convert and where can I get it?
===============================================
Re: What would be best way to convert iNes to Unif? \ Yakushi~Kabuto on 10th April 2007, 09:53 wrote:
CM can not support UNIF at its current state. Because UNIF is not really a header but rather a format, and a sucking one.
UNIF adds variable lenght bytes at the begining, at the end AND in the middle of the file. The variable lenght is a first problem for CM altho it can probably be implemented. However CM currently can definately not skip the bytes in the middle of the file, so we're stuck regarding UNIF support.
===============================================
Re: What would be best way to convert iNes to Unif? \ BootGod on 10th April 2007, 12:30 wrote:
It's not for USA roms only, just happens to mostly only work them at the moment. UNIF needs data that cannot be determined from an INES file, so the program can only convert files that it has info on in the DB.I tried NES Cart Database's tool, but the converted are not recognized by the new No-Intro NES(20070407). Also it is for the USA roms only.
CM can not support UNIF at its current state. Because UNIF is not really a header but rather a format, and a sucking one.
I must be one of the only people that actually likes the UNIF format! It has its flaws, but they could be worked out. There actually is a recent INES 2.0 proposal on the table that looks pretty good (and backwards compatible), but after the spec was "finalized" I never heard much more about it 