Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

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.

1

clrmame Discussion / Different dat with the same name

« on: 08 April 2022, 18:53 »

Hi Roman
Some recent no-intro dat have the same name of redump's dat one, like Acorn Archimedes or Apple Machintosh even if they are in different paths/folder
When adding one clrmame report that is either an update or an existing one to be replaced
What's the best method to manage this? Maybe manually editing the dat file or there is a better way?

Any suggestions?

D.

2

clrmame Discussion / Error in rebuilding some TOSEC dat with long path and zip compression

« on: 05 January 2021, 18:10 »

Dear Roman
I was updating various TOSEC sets and I have faced a problem with some dats
For example when I try to rebuild this ones (but probably there are more):

Apple II - Compilations - Applications - [DO] (TOSEC-v2020-10-26)
Apple II - Compilations - Games - [DO] (TOSEC-v2020-10-26)
Apple II - Compilations - Games - [DSK] (TOSEC-v2020-10-26)
Apple II - Compilations - Various - [DSK] (TOSEC-v2020-10-26)
Commodore C64 - Graphics - [PRG] (TOSEC-v2020-10-27_CM)

I get an error windows "Want to stop - Error while adding ........ blah blah" and a 0 byte file is created.  I'm sure is something related to a too long destination path name because I tested using a shorter one and it worked. However the the error only occurs when using zip compression, choosing 7zip or no compression at all the set is rebuild with no warnings

I was using version 4.039, but with 4.040 is the same

Regards
D.

3

clrmame Discussion / Clear the status (green or red) of a profile

« on: 30 June 2018, 22:19 »

I was manually checking some TOSEC dats and I found that some kind of feature could be useful for easy way to keep track of the one done and the ones still to process

Do it make sense to you or have any better idea or suggestions on how to do?

Regards
D.

4

clrmame Discussion / Problem in rebuilding MAME set over an exFAT volume

« on: 28 July 2017, 22:22 »

Hi, i found a bizarre behaviour in rebuild a MAME set over an exFAT volume.

Actually I'm using a dual Xeon 24 core total and 128 GB of ram and 3 Hard Drive.
The first one (C:) contains the OS, Windows Server 2016
The second one (D:) has all the WIP roms
The last one (E:) is the target for the rebuilder of clrmamepro 

The same test has been replicated using a different pc equipped with an i7, 32GB of memory and 3 Hard Drive (new ones) and with both windows 10 / 8.1 as operating system

It happens that the rebuild end correctly and from the scanner seem all ok too, but when checking the zip files, using the test function of 7z itself or different tools like total commander, and average of 10 / 15 archive results as corrupted
What is strange is that after running the rebuilt more times (deleting the zip before each run of course) the corrupted archive are not always the same, nor their number that can be more or less.
Also the zip size or the number of files in it, don't appear to be a discriminating factor as you can get bigger files or small ones broken.

Usually I'm running CMPro from a 48GB ramdisk (a bit smaller one on the i7 pc) using the free ImDisk (http://www.ltr-data.se/opencode.html/) , but even disabling it and executing from the hd don't change the results.
I also checked to exclude the cmpro task from the antivirus and the rebuild destination

However there are no problem if I rebuilt to 7z over exFAT volume, or if the same disk is formatted again in NTFS



PS. I also tried in using different allocation unit size for the exFAT volume, and I've been able to rebuild a complete TOSEC set, but no luck with MAME


Davide

5

clrmame Discussion / Merged sets and Super Kaneko Nova System BIOS

« on: 10 March 2015, 18:46 »

Hi Roman, sorry to bother you again

I was trying to rebuild the MAME roms switching from a split sets to a merged one
When the process end and i do a scan, i get this warning on SKNS rom
 
Super Kaneko Nova System BIOS [system: Super Kaneko Nova System BIOS - folder: skns - size: 3mb]
wrong name: E:\MAME\Roms\skns\cyvernj\sknsj1.u10 [wrong: cyvernj\sknsj1.u10] [right: sknsj1.u10]
wrong name: E:\MAME\Roms\skns\galpani4k\sknsk1.u10 [wrong: galpani4k\sknsk1.u10] [right: sknsk1.u10]
wrong name: E:\MAME\Roms\skns\galpans2a\sknsa1.u10 [wrong: galpans2a\sknsa1.u10] [right: sknsa1.u10]
wrong name: E:\MAME\Roms\skns\puzzloopu\sknsu1.u10 [wrong: puzzloopu\sknsu1.u10] [right: sknsu1.u10]
unneeded file: E:\MAME\Roms\skns\galpanisj\sknsj1.u10
unneeded file: E:\MAME\Roms\skns\galpanisk\sknsk1.u10
unneeded file: E:\MAME\Roms\skns\puzzloopa\sknsa1.u10
unneeded file: E:\MAME\Roms\skns\puzzloopj\sknsj1.u10
unneeded file: E:\MAME\Roms\skns\puzzloopk\sknsk1.u10
unneeded file: E:\MAME\Roms\skns\sarukani\sknsj1.u10
unneeded file: E:\MAME\Roms\skns\sengekisj\sknsj1.u10

The rebuilt was done to a new empty path and i have used this settings:

Misc Profiler Options -> Parsing Options -> Parser ROM 'merge' tags: enabled   (default)
Misc Profiler Options -> Parsing Options -> Parser DISK 'merge' tags: enabled  (default)
Misc Profiler Options -> Hash collision -> Naming Pattern: %f\%1   (default)
Misc Profiler Options -> Hash collision: All Clones in Relationship

Settings -> Full Merge Mode: Hash Collision Name

While the content of the zipped file is:

This is the content of the compressed file

sknsa1.u10
sknse1.u10
sknsj1.u10
sknsk1.u10
sknsu1.u10
cyvernj\sknsj1.u10
galpani4k\sknsk1.u10
galpanisj\sknsj1.u10
galpanisk\sknsk1.u10
galpans2a\sknsa1.u10
puzzloopa\sknsa1.u10
puzzloopj\sknsj1.u10
puzzloopk\sknsk1.u10
puzzloopu\sknsu1.u10
sarukani\sknsj1.u10
sengekisj\sknsj1.u10

what i'm doing wrong for getting this kind of error?

Thanks
Davide

6

clrmame Discussion / cmpro 4.017 x64 crash during rebuild

« on: 05 March 2015, 14:29 »

Hi to all,
I'm trying to do a full mame 0.159 set  rebuild, but cmpro process keep crashing during the scannig/rebuilding of the source folder.
This happens only with the last  4.017 64 bit version,  while i can finish the process with no problem using the previous version or with the 4.017 32 bit ones.

I did various try,  and happens if i update the old installation or with a brand new one configuration.
The task goes in error even before starting the rebuild (eg while scanning directory containing non mame roms) but also if i point the source path  directly to the folder containing only the rom for mame.
also i exclude a corrupter archive as ALL the rom are already unzipped

anyone else got the same problem?

PS.  i did the test only on windows 8.1 x64 as i don't have a pc with seven at the moment

regards
Davide 

7

clrmame Discussion / Feature Request - A "read only" rompath

« on: 24 November 2013, 16:57 »

Hi Roman,
Until now i used ClrMamePro mostly for MAME, but lately i started to play with other romset and emulators... MESS, Tosec, No-Intro, etc.

Working with different collections i think that could be useful a setting where it is possible to define a "read only" path where searching  for rom, but NOT delete them regardless the flag  'remove matched sourcefiles' in the rebuilder windows.
This can be really handy if you want, for example, rebuild a set for a new version of HBMAME starting from an existing MAME ones you already have,  plus dowloaded archives... or FinalBurn Alpha starting from a MAME + downloaded files, or a No-Intro from Tosec + download, etc. etc.
In this way while rebuilding you can clean your download/temp rom directory from multiple copies of the same file, but leave untouched the good sets you already have.

Hope to have explained mi idea, sorry but english is not my first language


PS. have a couple more of user defined setting for the compressor would be nice too... people can have different configuration for the same kind of archive,  like 7zip with or withoud solid compression

Thanks
Davide