Print

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

[actombo]

that program is awesome... and ive been using it for nearly its begining. thanks Roman.

i upgraded to WinXP two months before, i was using Win98 (it was capable what i need, but not any more) while clrmame hasnt supported for a long time and i stucked old version of clrmame which was quiet adequate.

Yesterday i tried version 4.05 with data for mame0.146, scan result was a long list..
i downloaded some update packs and meanwhile i thought it was a good idea to establish new HDD for only mame. I constructed necessary folder tree corresponding to system (with bios names) but i forgot the match "standard" folder for standard roms in system tab for rebuild.

and clicked to rebuild...
after 1 hour, despite i saw most of my standard roms found as "matched" and "created" nothing was there in target "standard" folder in new HDD. i couldnt find any trace of all those roms. i lost nearly 20 GB roms (nothing to worry i downloaded all over again ).

but now i hesitate to use clrmame with possibility of rom loss.
what was wrong...
1. is it possible clrmame deletes matched roms with the checking of "remove matched sourcefiles"  even it doesnt create or move any roms in rebuild mission.
2. is that a fault; although clrmame says there are "skipped" roms, remains nothing in source folder again with the checking of "remove matched sourcefiles".

thanks in advance, all for better clrmame

[Roman]

there is no known thing like a rom loss during rebuild. if you set up a destination rebuilder path, the files should be there. if you ticked the usage of system default paths, the files should be in the assigned ones.

there is one rebuilder advanced option though which allows the pure deletion of matched files but it's not enabled by default and you're prompted first.

so currently I don't know what happened on your system. you can send me the cmpro.ini file and the belonging .cmp file (settings folder) so I can have a look at your settings.

[Roman]

after checking your settings you can let it run again with some more files and check again or run sysinternals' processmonitor to see where cmpro tries to write files to....

[actombo]

i sent that two files to [email protected].

im using sysdefpaths. i think "Remove Matched Sourcefiles" option was changed during i couldnt follow the version changes of clrmame for a long time. i suppose  "matched" criteria is prevail for deleting source file, successful moving action is not so important. but in past i was using this option like cut&paste option which is copy first, paste, then delete source.

i tried rebuilding again, there is nothing remain in sourcefolder despite clrmame said some of them are "skipped".   

[Roman]

Thanks for the files...however I don't see anything spooky in there and rebuilding with your config works fine. Are all files affected or only some? The P:something folders are they all empty afterwards? Is P: something special like a network drive, readonly device, etc?
As I said, try again with a handful files and maybe run processmonitor to see what is happening.....and turn on logging in the rebuilder to see what's going on there...

[actombo]

i only forgot to match "standard" sysdef to "P:\standard" folder ... so only standard folder roms were affected. no problem with rest. other P:\* folders have roms in it.

P: is the map drive name of a partition of USB external HDD.
Problem is clrmame says its created and matched, although nothing created on target (it is ok internally, cause the target folder is fuzzy) and then deletes source files cause its matched (it is ok internally, remove matched sourcefile is checked) but considering both situations it cannot be said ok cause without moving action rebuilder works as shredder.

you may say it is not a fault of rebuilding, i can say nothing. but i think "matched" term with "remove sourcefile" option should be used as "investigate"&"define"&"cut"&"paste". any problem in this chain should terminate the "remove sourcefile" option.

sorry for explanation, you are the boss. you will say last word. this is my idea after losing 20 GBs of roms.

i will try processmonitor... but now the important thing is double check the sysdefpaths whether it corresponds to any solid place on HDD:)     

[Roman]

Actually system default paths *are* checked if they do exist...this includes the one for standard. If it doesn't existst, rebuild won't start and you're prompted. So I wonder how you could run a rebuild without having standard correctly assigned.

"matched" means that the found file in the source was matched against a file in the currently loaded datfile. It only gets rebuilt if it wasn't rebuilt before. If it was matched successfully and rebuilt already, it gets removed with the 'remove matched sourcefile' option.

still can't repeat any kind of rom loss...