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

Pages: [1]
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
Just my 2 cents
I too use a Synology nas to keep rom files and I rebuild/fix via network share all the time.
Of course is slower than a local drive but not so much, something like minutes not hours
The only time i had experienced something similar the guilty was a very cheap network switch between the pc and nas.

D.

3
Hi
I just tried with the c64 set and seem working, I just had to clear the cache.

Thanks as always

4
Hi Roman, i have sent you a PM with a link
I have to add some more details i found.

My source roms are zip files containing all the necessary for rebuild a complete set and they came from a well know private torrent
If i leave the zip into my global add path and do a rebuild process with ZIP compression there are no error, BUT some file are missing in the destination, for example:

for the Commodore C64 - Graphics - [PRG] (TOSEC-v2020-10-27_CM) are
Overweight Iranian Forest Goats Are Usually Not Awakened by Unexploded Ordnance After 2AM (2020-01-11)(Pimmelschimmel).prg
Magic Spraycan Tells the LSD Pirate about a Robot in the Garden Stealing His Plants (2013-07-20)(Desire - Genesis Project).prg

for the Apple II - Compilations - Applications - [DO] (TOSEC-v2020-10-26) are:
COPYB (19xx)(Krakowicz) & Copy II Plus v4.3 (1982)(Central Point Software) & Copy II Plus Bit Copy Program v4.3 (1982)(Central Point Software).do
DiskQuik (1983)(Beagle Bros) & DOS Boss (1981)(Beagle Bros) & Pronto Create v1.3 (1982)(Beagle Bros) & Pronto Update (1983)(Beagle Bros) & DOS Boss II (198x)(Beagle Bros).do
Roots (1982-06)(Practical Computing) & Joystick Tester (19xx)(-) & Bessel Function Calculator (19xx)(-) & Katakana Program (19xx)(-).do
Wildcard Plus Disk Software (1983)(Elite Software) & Recupere DHGR Sauve par Copy (1991)(Deckard)(fr) & ADT v1.20 (1994-10-07)(Guertin, Paul).do

Like they are ignored in the scanning process.   If I unpack the source zip the missing files are rebuilt but only using 7zip compression because with zip the error "error while adding" pop up

Moreover for the Apple II example above even if unpacked, the file  DiskQuik (1983)(Beagle Bros) & DOS Boss (1981)(Beagle Bros) & Pronto Create v1.3 (1982)(Beagle Bros) & Pronto Update (1983)(Beagle Bros) & DOS Boss II (198x)(Beagle Bros).do     is still ignored during the scan process, I need to rename with a shorter path for being analyzed and rebuild

Hope to be enough clear in my description

D.


5
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.




6
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.

7
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


8
That was fast, are you even human?  :)
I'll try later and let you know.  Thanks

Davide

9
ehm.. with "sure you want to use that?" you mean the merged sets or the Hash Collision Name mode option?
because if you are referring to the option then probably i have not well understand how it's work this mode

Davide

10
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

11
I think you were right,   i have almost finished the rebuild with the version you linked me.

thanks again and sorry for not having noticed the problem in the other discussion

davide

12
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 

13
clrmame Discussion / Re: Feature Request - A "read only" rompath
« on: 24 November 2013, 23:07 »
Hi Roman, thanks for your answer

Correct,  actually I'm using the rebuilder with the delete option tuned on or off  depending on what romset I'm working on.
I thinked about the possibility of having this feature because during the weekend i updated my MAME roms to the last version and created a full set for FinalBurn Alpha while using the remove option turned on for reduce the number of files inside the work rom/download folder and easily analyze the leftovers...

The next step was looking at MESS but having already processed the temp folder many BIOS are missing (with mame rebuild) and some megadrive games too (fba).

Normally i have to launch the scan more times giving the path(s) and changing the status of the delete flag,  Using this "protected folder" allow me to do the rebuild in one run

Maybe is possible to to the same thing playing with the options of batchrun but i was not able to do as i wanted
 


About the compressor settings a global history list where you can select some memorized ones could be good too... the idea was have more choice of archiving parameters for people who want for example create a set of rom with low 7zip compression for use in a mamecab/emulation station/other and an high 7zip solid compression for a backup on a different storage


regards
Davide
 

14
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

Pages: [1]

Page created in 0.162 seconds with 20 queries.

anything