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 - yerduaz

Pages: [1] 2
1
clrmame Discussion / Re: clrmamepro 4.038a released
« on: 11 August 2020, 21:08 »
Hi Roman,
you're right: the option was disabled. I have probably click on this checkbox inadvertently...
Anyway, sorry for the trouble and many thanks for the quick and efficient answer.

2
clrmame Discussion / Re: clrmamepro 4.038a released
« on: 11 August 2020, 15:55 »
Hi Roman,
it seems there is a small issue with clrmame 4.038/a regarding the update of dat files: when you place a new version of a dat file in the same directory as the old one and open it, you get the usual window "Found an updated DatFile" and the new dat file takes over the seetings of the old one (so far, so good...). However, the old dat file, instead of being removed, is resetted: it is still available physically and is listed in the Profiler, in the folder [NEW DATFILES].
Could you please take a look at this?

3
clrmame Discussion / Re: Scanning with "Missing" unchecked
« on: 17 December 2017, 22:09 »
Problem solved! Thank you for the fix on Sunday ;)

A little bit in advance: Frohe Weihnachten und einen guten Rutsch ins neue Jahr.

4
clrmame Discussion / Re: Scanning with "Missing" unchecked
« on: 17 December 2017, 17:12 »
Thanks for the quick reaction.

As requested, please find the dat in the MEGA directory provided above. However, i'm pretty sure this issue can be reproduced with any kind of dat...

To satisfy your curiosity, I'm using this option in case of a "delta-dat", meaning a dat which is nearly identical to another dat. In that case, I scan with the delta-dat the delta directory with the "missing" option unchecked to rename files and remove uneeded ones, then scan the basic directory without any fixing option just to create a fix dat, and finally re-scan the delta directory with the fix dat (this time with all options activated) to check if something is still missing. This process is a little bit tedious but prevent to have multiple copies of the same files. To give you a practical example, I use this with the ADVANScene dats as they are mostly identical to the No Intro dats.

5
clrmame Discussion / Scanning with "Missing" unchecked
« on: 17 December 2017, 10:14 »
Hi Roman,
it seems there is an issue with the latest clrMAME: when you scan a directory with the option "Missing" unchecked (all other options "Case", "Unneeded", etc., are selected though), clrMAME shows all scanned ROMs as having a wrong case.

I have uploaded 2 screenshots to illustrate the issue: https://mega.nz/#F!cpB2RLjB!9XV4poCLQLiPHTZBD5GH7Q

This problem can be reproduced with the latest version 4.033 as well as with the latest nighty build from 02.11.2017.

Can you please take a look at this?

6
clrmame Discussion / Re: Problem with parent - clone dat file
« on: 29 September 2014, 19:32 »
Thanks for the explaination.

Such a warning would be nice indeed.

7
clrmame Discussion / Re: Problem with parent - clone dat file
« on: 29 September 2014, 16:45 »
Thanks for your answer.

For info, this dat file is coming directly from the DoM of No-Intro (as P/Clone XML with "Default parent if there is no p/c info").

I agree with you that this dat file is "special" but it is not wrong either as it respects the xml/dat file format and keywords.
What I don't understand is why clrmame can't scan properly these roms with such dat file: either the release/region is disregarded (in this case, 2 sets containing 2 roms should be created) or the release/region is considered and one only set containing the 4 roms is created. Instead of this, every scan leads to unsuccessful results with wrong placed roms and "Great Golf (World) (Beta)" removed. It seems that the code is struggling with contradictoy instructions on how to handle this special case...

8
clrmame Discussion / Problem with parent - clone dat file
« on: 27 September 2014, 08:21 »
Hi Roman,

It seems there is a problem with parent - clone relationship in this dat file:
rom Great Golf (Japan) is parent
rom Great Golf (Korea) is clone of Great Golf (Japan)
rom Great Golf (World) is parent
rom Great Golf (World) (Beta) is clone of Great Golf (World)

When scanning with clrmame (4.015), it creates a container "Great Golf" (without country) and adds then removes some roms from this container. This behaviour repeats by every scan.

Can you plesae take a look at this ?


9
That was quick!

Thanks Roman.

10
Thank you Roman.

I presume that the best workaround for now is to deselect "Scanner->Fix->Case" and rename the file manually.

11
I'm using 7z 9.25 alpha (64-bit).

7z options are:
Compress: a -y -r -ms=off -mx9 %1 %2
Delete: d -y -ms=off -mx9 %1 %2
Rename: not activated.

12
clrmame Discussion / Crash with lower case / upper case in 7z
« on: 04 February 2014, 21:10 »
Hi Roman,

I have a problem with the latest version of ClrMame: it crashes when it tries to change the lower case / upper case of files within a 7z.
ClrMame does not crash in any other case of renaming (adding/changing/removing any character) or when renaming a zip file.
For example:
Rename "simple Example.rom" into "simple example.rom" -> crash
Rename "simple Example.rom" into "simples examples.rom" -> no crash

Can you please take a look at it.

13
Thank you Roman.

I will check this on a future MESS version.

14
Interestingly, after adding another dat file, created from a xml file, the problem is gone: the dialog "Systems and assigned System-Default-Paths" now display the expected data: [STANDARD] <not assigned>.

After resetting the "corrupted" dat file with "Reset Profile(s)...", they also have the default values in the dialog mentioned above.

What puzzle me is: clrmame must have read these values from somewhere and I couldn't find them in any file (ini, xml, txt, cmp, cfg).
So either they are in "cache" or "hashes", or clrmame read some information from the previously loaded dat file, or I simply oversaw something...

15
clrmame Discussion / Default value for Misc_SoftwareLists
« on: 05 July 2013, 16:58 »
Hi Roman,
I currently have a problem with the default value for the parameter "Misc_SoftwareLists" in the file "datfile.cmp" within the "settings" folder.

When loading a new datfile, this parameter should be normally empty. However, since I filled this parameter for scanning MESS, now, for every new loaded datfile, the parameter "Misc_SoftwareLists" is automatically filled with the values I used to set for the MESS.cmp file.

It seems the default value for the parameter "Misc_SoftwareLists" has been overwritten for any reason, but I can't find in which file these data are written so that I could reset the default value of this parameter.

Can you please help ?

16
clrmame Discussion / Re: cmpro 4.08b released
« on: 25 October 2012, 06:16 »
Hi Roman,

thank you for the bugfix related to 7z/utf8.
It now works perfectly for me.

17
clrmame Discussion / Re: cmpro 4.08a released
« on: 19 October 2012, 05:52 »
Hi Roman,

please find hereafter the files:
http://speedy.sh/QgUv5/clrmame-7z-utf8.7z

Thank you for your help.

18
clrmame Discussion / Re: cmpro 4.08a released
« on: 18 October 2012, 21:24 »
Hi Roman,

I have a problem when scanning a 7zip file containing a UTF-8 file (.dsk): clrmame will not recognize the name of the .dsk file (which is already correct) and will propose to rename this file. If confirmed, the renaming does not occur (so the .dsk file still has the correct name) and, therefore, clrmame will retry to rename this file again by the next scan...
Interestingly, the file name of the .7z file itself (also UTF-8) is recognized and doesn't make any problem.

This problem does not occur with zip or rar files.

Please find attached the concerned 7z file and the according dat file.
Sorry, don't know why but I currently get an error message when trying to upload any file...

Configuration:
clrmame 4.08a (64-bit)
7zip 9.25 alpha (64-bit)

19
clrmame Discussion / Re: cmpro 4.08 released
« on: 30 September 2012, 09:18 »
@Roman: thank you for fixing this issue in 4.08a

@oxyandy: thank you for mentioning the compatibility problem with of the last 7z with t7z. In my case, 7z 9.28a (x64) doesn't work either with t7z 0.9.1. I had to switch back to 7z 9.25a to have t7z recognize the compression method.

20
clrmame Discussion / Re: cmpro 4.08 released
« on: 29 September 2012, 11:56 »
Sure, RTFM... :P

Nevertheless, I consider this as rather dangerous as, knowing that several people does not read the whatsnew, this option really can lead to a permanent loss of the impacted archives. Maybe a check of the 7z version and a warning window would be appropriate...

Pages: [1] 2

Page created in 0.124 seconds with 19 queries.