3.106

misc: Linux WINE: changed systime convertion to work flawlessly (www profiler)
misc: Linux WINE: launch button bar isn't hidden anymore (but minimized). This increases compatibility and even fixes some MS Windows issues.
misc: Linux WINE: changed warnings window. It will now automatically appear if something appears in it. You can still minimize it then.
misc: several windows correctly appear at the front now.
misc: treectrl and listctrl bitmaps are now 24bit and different
misc: F2 (edit label) functionality to several list and tree controls
misc: listing corrupt containes (corrupt chds, zips...) in the stats
misc: disabled "Possible missing alternative samples folder" in the database checker MAME doesn't load samples from a parentset when no sampleof tag is given. In consequence you may need some more samplesets for MAME now.



Roman Scherzer

I am having some strange problems with this version. Here's what it seems to happen: I run it and have my sets deemed OK (0.120). Then the next time I run it, it asks if it's OK to delete some files from dsfdct, wschampa, royalmah, yukon1 perhaps others. I click OK (note I do have a backup folder but nothing new is being saved there) then the next time I run it, some files from other sets are missing. I have no clue about what's wrong there.

Update: every time I run it always asks the same questions. I am updating from 0.119u4 to 0.120. Those questions are:

Do you want to delete 'C:\mame\roms\dsfdcta\gc910jc.u1' ?
Do you want to delete 'C:\mame\roms\dsfdcta\gc910jc.u6' ?
Do you want to delete 'C:\mame\roms\dsfdcta\ge887ja_gn887ja.u1' ?
Do you want to delete 'C:\mame\roms\dsfdcta\ge887ja_gn887ja.u6' ?

Do you want to rename all wrong named roms in 'C:\mame\roms\royalmah.zip'?

Do you want to delete 'C:\mame\roms\royalmah\1.c110' ?
Do you want to delete 'C:\mame\roms\royalmah\1.p1' ?
Do you want to delete 'C:\mame\roms\royalmah\10' ?
Do you want to delete 'C:\mame\roms\royalmah\18s030n.6k' ?
Do you want to delete 'C:\mame\roms\royalmah\2.c109' ?
Do you want to delete 'C:\mame\roms\royalmah\2.p2' ?
Do you want to delete 'C:\mame\roms\royalmah\20' ?
Do you want to delete 'C:\mame\roms\royalmah\3.c108' ?
Do you want to delete 'C:\mame\roms\royalmah\3.p3' ?
Do you want to delete 'C:\mame\roms\royalmah\30' ?
Do you want to delete 'C:\mame\roms\royalmah\4.c107' ?
Do you want to delete 'C:\mame\roms\royalmah\4.p4' ?
Do you want to delete 'C:\mame\roms\royalmah\5.p5' ?
Do you want to delete 'C:\mame\roms\royalmah\6.p6' ?

Then it spents a lot of time on wschamp, comes with these:

Do you want to delete 'C:\mame\roms\wschampa\as1001m01.u38' ?
Do you want to delete 'C:\mame\roms\wschampa\as1002m01.u39' ?
Do you want to delete 'C:\mame\roms\wschampa\as1003m01.u40' ?
Do you want to delete 'C:\mame\roms\wschampa\as1004m01.u41' ?
Do you want to delete 'C:\mame\roms\wschampa\as1005m01.u18' ?
Do you want to delete 'C:\mame\roms\wschampa\as1006e02.u06' ?
Do you want to delete 'C:\mame\roms\wschampa\as1007e02.u07' ?

After it goes on yukon1:

Do you want to delete 'C:\mame\roms\yukon1\xbl.12h' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.2h' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.3k' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.4k' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.5k' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.6k' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.7k' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.8k' ?
Do you want to delete 'C:\mame\roms\yukon1\xbl.9h' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1h' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1k' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1l' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1m' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1n' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1p' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1r' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1s' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.1t' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2k' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2l' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2m' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2n' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2p' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2r' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2s' ?
Do you want to delete 'C:\mame\roms\yukon1\yua-1.2t' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.10c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.10d' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.11c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.11d' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.1b' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.1c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.3a' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.3b' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.3c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.4a' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.4b' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.4c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.4d' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.6a' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.6b' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.6c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.6d' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.7b' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.7c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.7d' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.8b' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.8c' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-1.8d' ?
Do you want to delete 'C:\mame\roms\yukon1\yul-20.1a' ?

I reply Yes to all the above questions and they are asked again every time I run Scan. It turns out that none of those files were actually deleted or renamed at all. No new zipped files are created on 'C:\mame\roms'.

a) be sure to use an official mame.exe to get the data from if I look at the official database I see that the mentioned files as indeed not needed.

b) looks like they can't be removed (e.g. because the files are in use and shared by other applications). In this case you should see a warning in the warnings window in the scanner. I will do some checks what is shown when they can't be removed.
Although they should at least already have a [not fixed] postfix in the scanresults tree listing.


Roman Scherzer

> a) be sure to use an official mame.exe to get the data from if I look at the
> official database I see that the mentioned files as indeed not needed.

I compile my own unmodified builds from official source downloaded from mamedev.org.

> b) looks like they can't be removed (e.g. because the files are in use and
> shared by other applications). In this case you should see a warning in the
> warnings window in the scanner. I will do some checks what is shown when they
> can't be removed.
> Although they should at least already have a [not fixed] postfix in the
> scanresults tree listing.
>
> Roman Scherzer

I don't get any warnings, the files can be freely deleted by hand, for example. The first time I run CLRMAMEPRO 3.106, in the scanresults they show as fixed, however they are not. Every time I run CLRMAMEPRO, the MAME 0.120 profile has a "forbidden" sign over it. What does that mean anyway?

I closed the program and just ran it again while typing this reply. Answered Yes to all "delete" and "rename" questions. Here is the scan result - note I unchecked the "You want to scan" options: Samples and CHD. For an unkown reason Come on Baby still appears as normal ROMset even though it's a CHD. Also while it was scanning and fixing wschampa I noticed inside "backup\_tempmove\wschampa" some 7 files that were stored there, then deleted - I assume they should be recompressed inside wschamp, but they never did as wschamp was never created inside mame\roms. Looking at the files dates, they are being handled by CLRMAMEPRO as their date and time stamps are close to the time I ran the program. So they were modified, but how come royalmah is always with wrong names?

The ones I really miss are nitdbl, wh1 P ROMs and cannonbp color proms. All other Amiga CD32 and Konami Viper are not there because I have them in a separate, removable HD (that's why I unchecked CHDs).

Cannon Ball (Pacman Hardware) [folder: cannonbp - parent: cannonb - size: 21kb]
wrong crc32: colorprom_1 [wrong: 2fc650bd] [right: 08f8ae7e]
wrong crc32: colorprom_2 [wrong: 63efb927] [right: 359a15dc]

Candy Puzzle (v1.0) [system: Amiga CD32 Bios - folder: cndypuzl - size: 1mb]
missing set: Candy Puzzle (v1.0)

Code One Dispatch [system: Konami Viper BIOS - folder: code1d - size: 256kb]
missing set: Code One Dispatch

Code One Dispatch (ver B) [system: Konami Viper BIOS - folder: code1db - parent: code1d - size: 256kb]
missing set: Code One Dispatch (ver B)

Come On Baby [folder: comebaby - size: 64kb]
missing set: Come On Baby

Dance Dance Revolution (GC845 VER. JAA) [system: System 573 BIOS - folder: ddrja - parent: dstage - size: 17mb]
missing set: Dance Dance Revolution (GC845 VER. JAA)

Dance Dance Revolution (GC845 VER. JAB) [system: System 573 BIOS - folder: ddrjb - parent: dstage - size: 17mb]
missing set: Dance Dance Revolution (GC845 VER. JAB)

Harem Challenge [system: Amiga CD32 Bios - folder: haremchl - size: 1mb]
missing set: Harem Challenge

Laser Strixx [system: Amiga CD32 Bios - folder: lasstixx - size: 1mb]
missing set: Laser Strixx

Laser Quiz [system: Amiga CD32 Bios - folder: lsrquiz - size: 1mb]
missing set: Laser Quiz

Laser Quiz '2' Italy (v1.0) [system: Amiga CD32 Bios - folder: lsrquiz2 - size: 1mb]
missing set: Laser Quiz '2' Italy (v1.0)

Magic Premium (v1.1) [system: Amiga CD32 Bios - folder: mgprem11 - size: 1mb]
missing set: Magic Premium (v1.1)

Mocap Golf [system: Konami Viper BIOS - folder: mocapglf - size: 256kb]
missing set: Mocap Golf

Nightmare in the Dark (bootleg) [system: Neo-Geo - folder: nitdbl - parent: nitd - size: 14mb]
missing rom: 260-c1bl.bin [size: 2097152] [CRC32: b4353190] [SHA1: 90d5352e243a05f5c2be4fa7475667bb56e78016]
missing rom: 260-c2bl.bin [size: 2097152] [CRC32: 6e27511f] [SHA1: 1fc5cf7786ad0f0bc7b1623acabe605ad04af3c1]
missing rom: 260-c3bl.bin [size: 2097152] [CRC32: 472cf075] [SHA1: 7cdd25019e37a3d127e68a4179c051881df19afa]
missing rom: 260-c4bl.bin [size: 2097152] [CRC32: 4c3926e6] [SHA1: 7fc54a9886dbef911f7b226e3cd20081c535e989]
missing rom: 260-p1bl.bin [size: 524288] [CRC32: 1a05bd1b] [SHA1: 7bbddef842d50b0778711063af695b168a76ff61]
missing rom: 260-v1bl.bin [size: 2097152] [CRC32: 79008868] [SHA1: 90bd6aaefd37341297ab1f4ae7246e52facd87d0]
missing rom: 260-v2bl.bin [size: 2097152] [CRC32: 728558f9] [SHA1: 309aa7c933c199b2e540a601b363e7af8744fe00]

Police 911 2 [system: Konami Viper BIOS - folder: p9112 - size: 256kb]
missing set: Police 911 2

Pop'n Music 9 [system: Konami Viper BIOS - folder: popn9 - size: 256kb]
missing set: Pop'n Music 9

ParaParaParadise 2nd Mix [system: Konami Viper BIOS - folder: ppp2nd - size: 256kb]
missing set: ParaParaParadise 2nd Mix

World Heroes (set 1) [system: Neo-Geo - folder: wh1 - size: 12mb]
missing rom: 053-p1.bin [size: 524288] [CRC32: d42e1e9a] [SHA1: 9d1911fe4bf6202466ec45557dd008cbf01ca9c6]
missing rom: 053-p2.bin [size: 524288] [CRC32: 0e33e8a3] [SHA1: 4b7086edb504f3c30529d51ba8f453d48eba5164]

> I don't get any warnings, the files can be freely deleted by hand, for example.

That doesn't play a role. If files are in use / locked (e.g. by virusscanner), cmpro list them in the warnings window. Since the warnings window code changed in 3.106 I will have another look at it.


> Every time I run CLRMAMEPRO, the MAME 0.120 profile has a
> "forbidden" sign over it. What does that mean anyway?

It's the red dot which you know from pre-3106 releases it means you're missing files.

> I closed the program and just ran it again while typing this reply. Answered Yes
> to all "delete" and "rename" questions. Here is the scan result

it would be interesting to have a screenshot of the popping up messages.



> unchecked the "You want to scan" options: Samples and CHD. For an unkown reason
> Come on Baby still appears as normal ROMset even though it's a CHD.

It's not. ComeOnBaby got a chd AND a romset (which is a full no dump though).

> Also while
> it was scanning and fixing wschampa I noticed inside "backup\_tempmove\wschampa"
> some 7 files that were stored there, then deleted - I assume they should be
> recompressed inside wschamp

They are temporary. You can't say weather they are picked up for later use or not. Depends on used merge modes and several other things.


>So they were modified, but how come royalmah is always with wrong
> names?

That's what I want to investigate.

> separate, removable HD (that's why I unchecked CHDs).

Well...they appear as missing set because you scan for sets...this has nothing to do with not-scanning for chds. these sets are chd-only sets. If you don't have the chd, you miss the set.

Rest of the result looks ok, the 2 proms from u4 and the neogeo changes from 120.


Roman Scherzer

...and please send me the zip which causes problems.


Roman Scherzer

what's interesting: The mentioned royalmj (and clones) set didn't change from 119u4 to 120. Is it possible that you accidently switched merge modes in between?
...and please test an official MAME binary just to be sure ;)


Additionally:
1) send me the zipfile (before doing 2-3)
2) for a test, turn on settings->compressor->Full Zip Structure Scan (slower zipscanner but detects some bad zipstructures)
3) try to rezip the file in question manually (decompress, delete zip, compress files to new zip)



Roman Scherzer

> what's interesting: The mentioned royalmj (and clones) set didn't change from
> 119u4 to 120. Is it possible that you accidently switched merge modes in
> between?

I thought it only messed with royalmah but there is no royalmaj in my ROMS folder. Where did it go?! And no, I didn't change merge settings, that's for sure.

> ...and please test an official MAME binary just to be sure ;)

Will do after a short while.

> Additionally:
> 1) send me the zipfile (before doing 2-3)
> 2) for a test, turn on settings->compressor->Full Zip Structure Scan (slower
> zipscanner but detects some bad zipstructures)
> 3) try to rezip the file in question manually (decompress, delete zip, compress
> files to new zip)
>
> Roman Scherzer

Sure, keep an eye at your inbox.

> Additionally:
> 1) send me the zipfile (before doing 2-3)

Am I supposed to send you zipfiles?

clrmame@clrmame.com:
216.144.214.104 failed after I sent the message.
Remote host said: 550 zip files are not accepted here

try roman.scherzer*at*gmail*dot*com
or upload it somewhere where I can grab it.


Roman Scherzer

royalmah is a clone of royalmj. Depending on your set merge mode you either have it separated or included in the parent.


Roman Scherzer

> I am having some strange problems with this version. Here's what it seems to
> happen: I run it and have my sets deemed OK (0.120). Then the next time I run
> it, it asks if it's OK to delete some files from dsfdct, wschampa, royalmah,
> yukon1 perhaps others. I click OK (note I do have a backup folder but nothing
> new is being saved there) then the next time I run it, some files from other
> sets are missing. I have no clue about what's wrong there.
>
> Update: every time I run it always asks the same questions. I am updating from
> 0.119u4 to 0.120. Those questions are:
>
> Do you want to delete 'C:\mame\roms\dsfdcta\gc910jc.u1' ?
> Do you want to delete 'C:\mame\roms\dsfdcta\gc910jc.u6' ?
> Do you want to delete 'C:\mame\roms\dsfdcta\ge887ja_gn887ja.u1' ?
> Do you want to delete 'C:\mame\roms\dsfdcta\ge887ja_gn887ja.u6' ?
>
> Do you want to rename all wrong named roms in 'C:\mame\roms\royalmah.zip'?
>
> Do you want to delete 'C:\mame\roms\royalmah\1.c110' ?
> Do you want to delete 'C:\mame\roms\royalmah\1.p1' ?
> Do you want to delete 'C:\mame\roms\royalmah\10' ?
> Do you want to delete 'C:\mame\roms\royalmah\18s030n.6k' ?
> Do you want to delete 'C:\mame\roms\royalmah\2.c109' ?
> Do you want to delete 'C:\mame\roms\royalmah\2.p2' ?
> Do you want to delete 'C:\mame\roms\royalmah\20' ?
> Do you want to delete 'C:\mame\roms\royalmah\3.c108' ?
> Do you want to delete 'C:\mame\roms\royalmah\3.p3' ?
> Do you want to delete 'C:\mame\roms\royalmah\30' ?
> Do you want to delete 'C:\mame\roms\royalmah\4.c107' ?
> Do you want to delete 'C:\mame\roms\royalmah\4.p4' ?
> Do you want to delete 'C:\mame\roms\royalmah\5.p5' ?
> Do you want to delete 'C:\mame\roms\royalmah\6.p6' ?
>
> Then it spents a lot of time on wschamp, comes with these:
>
> Do you want to delete 'C:\mame\roms\wschampa\as1001m01.u38' ?
> Do you want to delete 'C:\mame\roms\wschampa\as1002m01.u39' ?
> Do you want to delete 'C:\mame\roms\wschampa\as1003m01.u40' ?
> Do you want to delete 'C:\mame\roms\wschampa\as1004m01.u41' ?
> Do you want to delete 'C:\mame\roms\wschampa\as1005m01.u18' ?
> Do you want to delete 'C:\mame\roms\wschampa\as1006e02.u06' ?
> Do you want to delete 'C:\mame\roms\wschampa\as1007e02.u07' ?
>
> After it goes on yukon1:
>
> Do you want to delete 'C:\mame\roms\yukon1\xbl.12h' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.2h' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.3k' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.4k' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.5k' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.6k' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.7k' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.8k' ?
> Do you want to delete 'C:\mame\roms\yukon1\xbl.9h' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1h' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1k' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1l' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1m' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1n' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1p' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1r' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1s' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.1t' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2k' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2l' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2m' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2n' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2p' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2r' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2s' ?
> Do you want to delete 'C:\mame\roms\yukon1\yua-1.2t' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.10c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.10d' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.11c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.11d' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.1b' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.1c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.3a' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.3b' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.3c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.4a' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.4b' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.4c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.4d' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.6a' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.6b' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.6c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.6d' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.7b' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.7c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.7d' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.8b' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.8c' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-1.8d' ?
> Do you want to delete 'C:\mame\roms\yukon1\yul-20.1a' ?
>
> I reply Yes to all the above questions and they are asked again every time I run
> Scan. It turns out that none of those files were actually deleted or renamed at
> all. No new zipped files are created on 'C:\mame\roms'.
>



Roman Scherzer