i like romcenter very much, because it's very easy to handle, much more than crlmame. thats the reason why i still use rc. but the only problem i think this tool has, is the incompatibility to clr dat files. yes i know there is a converter out now, but it's not very userfriendly to convert all dat files, all the time if there is a new version out. rc has too less dat files. and all dats which are coming out are for clr only. i know it is't possible to use 100% the clr dat file because of some missing features in rc, but it would be very nice to use the crl dat file without converting them first. only file name, size and crc check is enough for use the crl these dats. thats my whishes to rc programmer if he has time again. all in all you programmed a very great tool which is self-describing. much thanks for this, bye SyNTaXer
It might make sense to have an import function that uses DatUtil to convert from ClrMamePro format (or XML) to RomCenter format. This could work in a similar way to the MAME import which already uses DatUtil, just the new option would be from a data file directly rather than an EXE. Maybe something for the to-do list Eric?
I'm planning to add a 'load...' action in the menu to load a datafile (rc or clr). I could remove the datafile combo box and part of the datafile manager...
Tell me what you think.
The REBUILD function of clr would be nice, not only to rebuild an entire romset but also to add new roms from various paths as indicated in another thread.
RomCenter wrote:Do you have an idea of how you want to use it ?
Can you describe the way you want it to work ?
The way REBUILD works is that it allows multiple paths and a destination path to rebuild entire NEW roms sets from scratch which in itself is one very long process! This effectively will create NEW ZIP files containing all the correct roms and build a clean NEW set in the destination folder.
Another use of REBUILD in clr is to add new roms to the destination folder in the same way as above.
Simply tell it the destination folder and add additional paths containing new roms and allow it to merge and create NEW zip files to the destination folder.
Its a nice automatic function that can create sets or add new roms to an existing folder without much knowledge and should be easy for newbies too.
Hi, people, I´m new and I have another Idea, first than nothing, I speak spanish, and I´m still learning english, and I´m not really good, but...
My ideas are this:
1 - If there exist a "missing rom", rc search always in the listed directories to find it, but never in the Achive folder. You can add an option "Always check in the Archive folder" so if It´s enabled, rc will search the rom also in the Archive folder, what you think? It´s a good idea?
2 - This I consider a GREAT idea, IPS Patchs. I´m sure you know that the IPS patch convert a file with a crc, into another file with a diferent crc, my idea is folder IPS, containing the patchs, whit name "inputCRC_outputCRC.ips" (or .exe). With an button "Check IPS patchs", and this option must do this:
1) Check the missing roms of the zip files in the directories
2) If there are one, wich CRC is the same than the outputCRC of a
patch, search between all the files in the listed directories (including unkonw roms and all kind of files), to find one with the same CRC than the outputCRC of the current ips patch.
3) If there existe the file, then show the missing rom as "Avaible via IPS patch".
The first, I think is really easy, the second, much more hard, but grater too.
i've a new suggestion for a upcoming romcenter version. it's not a big one, but could be very useful. it would be very nice to see shared network drives in romcenter if adding a source directory to scan it.
It's not I don't want to, but it is a lot of work to maintain all contributions, and I (still) want to spend my free time on programming, and not administrating.
).
"That Which Does Not Kill Us Makes Us Stronger"..Friedrich Nietzsche.
