3.106a

misc: several updates to the window rendering system (incl. not stealing focus correct minimizing, warnings window only shows issues, etc.)
misc: allowing not existent sampleparents (invaders)


Roman Scherzer

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?

interesting.....can you please send me:

- cmpro.ini
- the belonging .cmp file for that profile (settings folder)
- the file in question itself
- what merge mode are you using? Which settings (ok I can see that from the *.cmp file)

If the clrmamepro mail address doesn't work, use roman.scherzer*AT*GMAIL*DOT*COM

I need some kind of minimal set to reproduce the issue...



Roman Scherzer

Will do - but I've just done some additional testing to make sure I could re-ceate this.

I am using "Merged sets".

I created a dir called roman & copied the 3 problematic zips into it :-

copy D:\Emumlators\112-roms\roms\baraduke.zip .
copy D:\Emumlators\112-roms\roms\astronp.zip .
copy D:\Emumlators\112-roms\roms\bgaregcn.zip .

I then set the roms path to this temp dir, used Merged sets and "fix" everything.

I got the recurring questions, but more interesting was the amount of files that are now in the temp dir. Here's ths list :-

astronp.zip
baraduke.zip
bgaregcn.zip
drgnbstr.zip
galaxyrp.zip
gekiretu.zip
genpeitd.zip
hopmappy.zip
metrocra.zip
pacland2.zip
quizdna.zip
roishtar.zip
rthundro.zip
skykidd.zip
skykiddo.zip
tceptor2.zip
wndrmomo.zip


wndrmomo.zip conatins cust60-60a1.mcu which is also in baraduke.zip.

Looks like it's splitting sets even though "merged sets" is selected !?!

(I'll zip up the other files you requested and mail them this evening).

Thanks

It seems the same kind of problems I detailed in my e-mail. When it reaches the parent, it starts adding files to the clone(s) and never gets to create the parent, but when it's the clone's time, it deletes all the files again. Same thing every time it's run.

thanks for your comments, I will check that maybe this evening since I'm currently on a business trip in Finland and Lithuania....


Roman Scherzer

>
> Hi
>
> I'm having similar issues to this post
>
http://www.clrmame.com/cgi-bin/wwwthreads/showpo> st.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?
>



Roman Scherzer