EMULAB Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

The new forum is online, hope you enjoy it!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Firewave

Pages: [1]
1
Just an idea off the top of my head. A way to differ between CHD and non-CHD softlists (or the type in general). MESS has separate softlist for different devices like floppy, cassettes, harddisks. Might make no sense at all in the context of clrmame. Just thinking out loud here since I don't maintain the CHD (i.e. CD_ROM) softlists.

2
Ah, cool. Looking forward to that. I haven't spent any time on any forum in the past few months. Only take quick looks at the main page.

3
With all those changes going on with the MESS softlists all the time, it would be nice, if there could be some improvements made.

Everytime one of the .xml files changes I have to manually add it again in the profiler, select the correct folder, than ask, if I want it to be updated. It would be nice, if it would treat the .xmls like binaries, so you specifiy the source and when you open it and it has changed the cached data will be updated.

Another thing would be a "big" rebuilder. So instead selecting multiple sets and it will start the rebuilder for each of them, it will take all the data and only scan the filesystem once and rebuild them. I am quite aware, that this might be impossible, because of the different merge options, folders, settings etc. since I have a big folder with a lot of unknown roms in it and processing it over and over for each set feel unnecessary.

4
clrmame Discussion / Re: Rebuilder ignoring "isbios" sets
« on: 07 May 2011, 21:46 »
Yeah, I messed with those options a long time ago and most likely saved some outrageously wrong as the default. Never did a full rebuild and the sets didn't change after they became bioses.

5
clrmame Discussion / Re: Rebuilder ignoring "isbios" sets
« on: 07 May 2011, 20:26 »
Ah, I figured it out. It's the "Separate BIOS sets" option. I had to check it.

6
clrmame Discussion / Re: Rebuilder ignoring "isbios" sets
« on: 06 May 2011, 22:03 »
It's actually the -listxml output from the latest SVN binary, so there is no dat. The scanner complains about them missing, but the rebuilder ignores them. If I copy the sets over to the rom directory and run the scanner again it is happy.

7
clrmame Discussion / Rebuilder ignoring "isbios" sets
« on: 06 May 2011, 16:07 »
I just rebuilt my MESS set from scratch based on a complete set and it didn't rebuilt the cd32 and cdimono sets. These are the sets, which have the "isbios" flag set. I checked the "System..." settings in the Rebuilder and the checkboxes of the sets were set.

8
Since quite a while clrmamepro is reporting about files, that could not be removed by the rebuilder. A problem are archives within archives. Since the contents will be extracted to the temp folder of clrmamepro the files are found and removed without any problems, but they will stay in the original archive. Would be nice to have it warn about these as well if possible.

9
clrmame Discussion / Re: clrmamepro 3.134a released
« on: 25 June 2010, 15:02 »
III) The Rebuilder has two steps: 1. Counting files 2. Scan files. During the counting step the second field is the folder, that is being parsed and the third field says "Please Wait...". The final values of the counting step are stay the same during the scanning process, if no file ever matches.
Since the fourth field is only showing data when it processes it the other fields always showing the same values are a bit confusing.

IV) I didn't and it has archives in archives, but I run all my scan on that folder and it never went past 100%. In the case it happens I had multiple Add-Paths and the archives in archives were in the second Add folder. I will try to investigate.

10
clrmame Discussion / Re: clrmamepro 3.134a released
« on: 25 June 2010, 11:44 »
I)
Just a minor display issue I recognised while scanning the GBA set. The scanning dialog is not clearing the "Parent" field for sets, that aren't clones. So will see, that "lizzie" has the parent "lionking".

II)
And the issue with a set being shown as not completely missing on the first scan and then completely on the second ahppened to me with GBA as well Sad It was with the texashld set. Will provide data to test later.

III)
I just saw another small display issue. In the scanning dialog of the Rebuilder the "File" field was show the last folder, that was processed of the subfolders in the Add-Paths during the scan. It should be empty or also show "Please Wait..." like the "was rebuilt to" field.
Update: It seems both are actually being left-overs from the counting process. Maybe both should just be cleared.

IV)
Yet another issue. For some reason the scanning progress in the Rebuilder went past 100% and showed 6% when it was actually finished. Never saw that before. Will investigate.

11
clrmame Discussion / Re: clrmamepro 3.134 released
« on: 04 June 2010, 20:41 »
Ah, that makes sense. Good you were able to reproduce it.

I am still looking at the other issue as I am not able to reproduce it anymore and I was able to do so easily before. Something weird is, that I suddenly had a file named "monacogp_30254.zip" in the backup folder and there was never such a filename in any of the dats.

12
clrmame Discussion / Re: clrmamepro 3.134 released
« on: 31 May 2010, 11:58 »
Thanks for the fixes. Did you include a fix for the 0-byte files with the rebuilder yet?

There are also still issues when updating an xml. In this case it's the sg1000.xml. After I updated it it showed a set as incomplete during the first run and completely missing during the second one (monacogp).
While trying to investigate the issue I ran into the next problem. I reverted to the old version of the XML and during the scan it showed a set as missing, that isn't even in it (monacogpa). Clearing the cache fixed the problem.
I attached both XMLs.

Update:
Regarding the first issue here's the result after the first scan:

Monaco GP (Jpn) [folder: monacogp - size: 40kb]
missing rom: monaco gp [24k].bin [size: 40960] [CRC32: 8572d73a] [SHA1: bea768b27c09bec805f0c70545d2f1435e3a3ddf]

After second scan:

Monaco GP (Jpn) [folder: monacogp - size: 40kb]
missing set: Monaco GP (Jpn)
missing rom: monaco gp [24k].bin [size: 40960] [CRC32: 8572d73a] [SHA1: bea768b27c09bec805f0c70545d2f1435e3a3ddf]

Update 2:
The first issue is not fixed by clearing the cache.

13
clrmame Discussion / Re: clrmamepro 3.133b released
« on: 25 May 2010, 04:04 »
I will prepare the data for the issue later.

I ran into a possible other issue. When you are rebuilding a set and the disk runs out of space it asks you, if you want to stop processing the roms. If you do some clrmamepro will leave a 0-byte file (I think in case, that it was trying to pack the first/only file in the archive - was rebuilding n64 stuff).

14
clrmame Discussion / Re: clrmamepro 3.133b released
« on: 21 May 2010, 09:16 »
I reproduced the other issue I was having.
I was updating the SCV set in MESS the way I described. It was just a changed set name and I had a complete set. I ran a "New Scan" and it showed the renamed set is missing a rom, but not the complete set (although it just contains the single rom). I checked the archive and it was renamed and it had the proper file inside. Then I once again chose "New Scan" and suddenly I had no missing roms anymore without changing the archive. So something is fishy there.

15
clrmame Discussion / Re: clrmamepro 3.133b released
« on: 21 May 2010, 08:47 »
What's the 'official' way? I use "Add DatFile..." to load the updated version and it detects, that there is already a file with that name and asks me, if I want to replace it. Since it won't detect changes to the .xml by itself I see no other way.

16
clrmame Discussion / Re: clrmamepro 3.133b released
« on: 20 May 2010, 14:04 »
not repeatable here...and very unlikely. cmpro stores the crc32 of the datfile in the cache file, too (and actually it's named after its crc32). If you change the dat in any way, its crc32 will change (assuming that the chance of hitting a hash conflict here is minimum) and the dat is read in instead of using the cache.

OK, tested it again and it worked fine. Only thing I recognized, that the state in the Profiler still showed green, although it is actually undetermined. Unfortunately I didn't check the "Scan" state, which should also be invalid in that case.

17
It would be nice, if a warning would be reported when a file was matched, but it could not be removed, because the file was nested, unsupported or because of an error. It's pretty annoying to look into the logfile to find out, which file was matched and could not be removed.

18
clrmame Discussion / Re: clrmamepro 3.133b released
« on: 18 May 2010, 01:21 »
Regarding the softlist support - it seems, that changes to the .xml are not being detected and even when I update it with "Add DatFile..." I still need to clear the cache, so it will use the new data.

Pages: [1]

Page created in 0.121 seconds with 20 queries.

anything
anything