Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

*View All ThreadsShow in Flat Mode*


SubjectRe: clrmamepro 3.106a released Reply to this message
Posted byAAG111
Posted on10/17/07 12:37 PM




Hi

I'm having similar issues to this post

http://www.clrmame.com/cgi-bin/wwwthreads/showpost.pl?Board=clrmame&Number=3700&page=0&view=expanded&mode=threaded&sb=7#Post3700

but it also happens with version :-
cmp3105a
cmp3106
cmp3106a

(So not sure about which thread to add it to!!)

Anyway, I'm trying to update my mame32 roms from 112 to 119, using the dat file "MAME v0.119 (cm).zip" from

http://www.logiqx.com/Dats/MAMEBeta/MAMEBetaHistory.php

Scanning Sets, Roms using Merged sets, with all the "fix" checked.

You keep an being asked to delete the same files everytime you do a scan. Saying Yes to all, or yes individually makes no difference.

Here's a run when saying yes to individual files :-



"Do you want to delete

'D:\Emumlators\112-roms\roms\bgaregcn\snd.bin' ?

If 'backup' is enabled this file/folder will be stored in the backupfolder!
Wrong placed files will be automatically moved to the correct set."

Answer Yes the file is placed into
cmp3106a\backup\_tempmove\baraduke

You then get asked to delete :-


'D:\Emumlators\112-roms\roms\baraduke\bd1-1.1n' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1-2.2m' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_1.9a' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_10.8l' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_11.8m' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_12.8n' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_2.9b' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_3.9c' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_4b.3b' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_5.3j' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_6.4m' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_7.4n' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_8.4p' ?
'D:\Emumlators\112-roms\roms\baraduke\bd1_9.8k' ?
'D:\Emumlators\112-roms\roms\baraduke\cus60-60a1.mcu' ?

It then says "Fixing" for a few seconds, and starts again asking to delete "D:\Emumlators\112-roms\roms\baraduke\bd1-1.1n".

Scanners then moves onto the next set - and the backup dir is now empty.


Same thing happens with

'D:\Emumlators\112-roms\roms\astronp\pr-5276.bin' ?

and also

'D:\Emumlators\112-roms\roms\bgaregcn\prg1.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\prg_0.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\prg_0.rom' ?
'D:\Emumlators\112-roms\roms\bgaregcn\prg_1.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\prg_1.rom' ?
'D:\Emumlators\112-roms\roms\bgaregcn\rom1.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\rom2.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\rom3.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\rom4.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\rom5.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\snd.bin' ?
'D:\Emumlators\112-roms\roms\bgaregcn\u123' ?
'D:\Emumlators\112-roms\roms\bgaregcn\u65' ?

fixing

'D:\Emumlators\112-roms\roms\bgaregcn\prg1.bin' ?


Plus others.

Any ideas?



-
Entire Thread
Subject  Posted byPosted On
*clrmamepro 3.106a released  Roman10/16/07 06:02 PM
..Re: clrmamepro 3.106a released  AAG11110/17/07 12:37 PM
..*fixed[nt]  Roman10/18/07 07:00 PM
..*Re: clrmamepro 3.106a released  Roman10/17/07 02:25 PM
...*Re: clrmamepro 3.106a released  Bugfinder10/17/07 05:28 PM
...*Re: clrmamepro 3.106a released  AAG11110/17/07 04:19 PM
....*Re: clrmamepro 3.106a released  Roman10/18/07 05:46 AM