21
clrmame Discussion / Re: clrmamepro 4.029b released
« on: 17 June 2016, 09:34 »
what the hell is that? 
- 19 April 2024, 14:11
- Welcome, Guest
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.
22
clrmame Discussion / Re: 2 small issue
« on: 08 April 2016, 21:38 »
I just tried your newest version, and now it works perfectly!
Thank you again for your support.
Thank you again for your support.
24
clrmame Discussion / Re: 2 small issue
« on: 31 March 2016, 11:39 »
ah, OK.
Thank you for your answer on 1.
for 2 there is no rush. When you will have time.
In the meantime I turned off those sets manually, and I'm happy again.
Thank you for your answer on 1.
for 2 there is no rush. When you will have time.
In the meantime I turned off those sets manually, and I'm happy again.
25
clrmame Discussion / 2 small issue
« on: 30 March 2016, 19:44 »
1) exporting a datfile in old format can only be done if I first go to dir2dat, load a profile with "deprecated", and then go back to datfile export. Is there a way to directly export a datfile in old format?
2) On my dumping machine I'm creating a full unmerged collection on MAME roms. No samples, no CHD.
So I point profiler to MAME executable, go to scan - set information, and follow your instructions (%H=1;%P=1 Apply, Invert, check 'initial invert' checkbox). After scanning I get error that 7 CHDs are missing: ddrja, ddrjb, mfightcc, p911uc, thrild2c, tsurugie, tsurugij.
On a different machine I have fully merged collection (no samples, no CHD) and there are no problems.
So it looks like the problem on those 7 CHD exclusion is only in unmerged sets.
Thank you very much for your help.
2) On my dumping machine I'm creating a full unmerged collection on MAME roms. No samples, no CHD.
So I point profiler to MAME executable, go to scan - set information, and follow your instructions (%H=1;%P=1 Apply, Invert, check 'initial invert' checkbox). After scanning I get error that 7 CHDs are missing: ddrja, ddrjb, mfightcc, p911uc, thrild2c, tsurugie, tsurugij.
On a different machine I have fully merged collection (no samples, no CHD) and there are no problems.
So it looks like the problem on those 7 CHD exclusion is only in unmerged sets.
Thank you very much for your help.
26
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 22 January 2016, 21:36 »
That's perfect!
I can't wor the next release.
I can't wor the next release.
27
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 22 January 2016, 10:31 »The select sets settings in set info will be stored and reassigned even after an update....I didn't know about it! This is very convenient.
Does it store the selected sets (as a list of names), or does it store the setting itself and rebuilds the correct list at each update?
28
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 21 January 2016, 18:06 »
Thank you very much for this.
It's a little convoluted, but if it works it's OK.
What about making it some sort of radio button, just to make it "newbie" proof.
I know of a lot of people that do not collect CHDs, and they would love to have a simple way of discarding them from the internal DB of clrmame.
Also, if it's a setting, it wil get saved into ini and manteined while updating from one version to the next.
It's a little convoluted, but if it works it's OK.
What about making it some sort of radio button, just to make it "newbie" proof.
I know of a lot of people that do not collect CHDs, and they would love to have a simple way of discarding them from the internal DB of clrmame.
Also, if it's a setting, it wil get saved into ini and manteined while updating from one version to the next.
29
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 20 January 2016, 13:17 »
Thank you so much!
I can't wait for it.
I can't wait for it.
30
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 20 January 2016, 07:22 »
yes, your list is fully included into my list.
31
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 19 January 2016, 21:21 »
So, my list has the same sets as your plus:
ftaerobi
genpin
moepro
moepro88
moepro90
mpsaikyo
mptennis
nes_bandai_pt554
nes_jf13
nes_jf17_pcm
nes_jf19_pcm
nes_jf23
nes_jf24
nes_jf29
nes_jf33
smoepro
terao
ftaerobi
genpin
moepro
moepro88
moepro90
mpsaikyo
mptennis
nes_bandai_pt554
nes_jf13
nes_jf17_pcm
nes_jf19_pcm
nes_jf23
nes_jf24
nes_jf29
nes_jf33
smoepro
terao
32
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 19 January 2016, 21:06 »
Sorry, in the haste I made a mess.
Here is my correct list:
You are missing 112 of 35893 known MAME sets (+ BIOS sets)
2spicy
bbhsc
bhead2k
bhead2k2
bhead2k3
bhead2ka
bmiidxs
bntyhunt
carnking
chaosbrk
chaoshea
chaosheaj
chasehq2
cndypuzl
cr589fw
cr589fwa
flipmaze
ftaerobi
genpin
ghostsev
gobyrc
goketsuj
gtfore04
gtfore04a
gtfore05
gtfore05a
gtfore05b
gtfore05c
gtfore06
gvrxpsup
gvrxpsys
gwinggen
haremchl
homura
hotgmkmp
hyperv2
initiad4
initiad4c
kof98um
kollon
kollonc
lasstixx
lbvbiosu
lsrquiz
lsrquiz2
mahjngoh
mgnumber
mgprem11
moepro
moepro88
moepro90
mpsaikyo
mptennis
nes_bandai_pt554
nes_jf13
nes_jf17_pcm
nes_jf19_pcm
nes_jf23
nes_jf24
nes_jf29
nes_jf33
nfsug
nightrai
odeontw2
orbatak
otenamhf
otenamih
otenki
popn9
ppp2nd
primevah
psyvaria
psyvarrv
quake
quizard
quizard2
quizard2_22
quizard3
quizard3_32
quizard4
quizard4_40
quizard4_41
quizard_10
quizard_12
quizard_17
raiden3
raiden4
raycris
rcdego
samspsen
shanghss
shangtou
shikiga3
shikigam
sianniv
smoepro
soutenry
speeddrv
spicaadv
spuzbobl
spuzboblj
terao
tmosh
tokyocop
trbwtchs
usagi
usagiol
vtennis3
wontmuch
xiistag
zokuoten
zooo
Here is my correct list:
You are missing 112 of 35893 known MAME sets (+ BIOS sets)
2spicy
bbhsc
bhead2k
bhead2k2
bhead2k3
bhead2ka
bmiidxs
bntyhunt
carnking
chaosbrk
chaoshea
chaosheaj
chasehq2
cndypuzl
cr589fw
cr589fwa
flipmaze
ftaerobi
genpin
ghostsev
gobyrc
goketsuj
gtfore04
gtfore04a
gtfore05
gtfore05a
gtfore05b
gtfore05c
gtfore06
gvrxpsup
gvrxpsys
gwinggen
haremchl
homura
hotgmkmp
hyperv2
initiad4
initiad4c
kof98um
kollon
kollonc
lasstixx
lbvbiosu
lsrquiz
lsrquiz2
mahjngoh
mgnumber
mgprem11
moepro
moepro88
moepro90
mpsaikyo
mptennis
nes_bandai_pt554
nes_jf13
nes_jf17_pcm
nes_jf19_pcm
nes_jf23
nes_jf24
nes_jf29
nes_jf33
nfsug
nightrai
odeontw2
orbatak
otenamhf
otenamih
otenki
popn9
ppp2nd
primevah
psyvaria
psyvarrv
quake
quizard
quizard2
quizard2_22
quizard3
quizard3_32
quizard4
quizard4_40
quizard4_41
quizard_10
quizard_12
quizard_17
raiden3
raiden4
raycris
rcdego
samspsen
shanghss
shangtou
shikiga3
shikigam
sianniv
smoepro
soutenry
speeddrv
spicaadv
spuzbobl
spuzboblj
terao
tmosh
tokyocop
trbwtchs
usagi
usagiol
vtennis3
wontmuch
xiistag
zokuoten
zooo
33
clrmame Discussion / Re: Some questions in batch rebuilding
« on: 01 January 2016, 16:46 »In batchrun rebuilder, i don't understand why i can have "don't remove rebuilt source" and "always remove rebuild source", both unchecked, aren't both of them mutually exclusive?. What means when both are unchecked? sources are remove or not?They are not mutually exclusive!
If both are unchecked crlmame will remove or not-remove the sourcefiles according to the configuration of the single datfile that is loaded in that moment.
So basically the batcher option is an over-ride of the single datfile option.
34
clrmame Discussion / Re: fully merged set - problem with clone CHDs
« on: 09 December 2015, 09:45 »
OK, thank you for the explanation.
If you could add a new variable in the select sets field like:
1)"disable all CHD sets"
2)"disable CHD only sets"
3)"keep CHD sets"
that would be highly appreciated by all people who are not collecting CHDs
In the mean time I'll disable them one-by-one.
If you could add a new variable in the select sets field like:
1)"disable all CHD sets"
2)"disable CHD only sets"
3)"keep CHD sets"
that would be highly appreciated by all people who are not collecting CHDs
In the mean time I'll disable them one-by-one.
35
clrmame Discussion / fully merged set - problem with clone CHDs
« on: 08 December 2015, 20:34 »
Hi ppl,
I just updated my spare machine with MAME 0.168, started clrmame, pointed it to mame64.exe and set 2 rompath:
D:\mame-roms
D:\mame-chds
I'm not collecting CHDs on this machine, so in the second directory I only have a bunch of empty folder, with the right name to make clrmame happy and avoid complains about "missing chds".
My scanning setup is:
After scanning I get the following:
The error is the same on all sets.
If I move folder "chaosheaj" into folder "chaoshea" or if I altogether remove "chaosheaj", I get the following in both cases:
How do I solve the problem and get back to a perfect "no miss - no errors" report from clrmame?
TIA for your help
I just updated my spare machine with MAME 0.168, started clrmame, pointed it to mame64.exe and set 2 rompath:
D:\mame-roms
D:\mame-chds
I'm not collecting CHDs on this machine, so in the second directory I only have a bunch of empty folder, with the right name to make clrmame happy and avoid complains about "missing chds".
My scanning setup is:
After scanning I get the following:
The error is the same on all sets.
If I move folder "chaosheaj" into folder "chaoshea" or if I altogether remove "chaosheaj", I get the following in both cases:
How do I solve the problem and get back to a perfect "no miss - no errors" report from clrmame?
TIA for your help
36
clrmame Discussion / Re: Questions from a newbie...
« on: 20 October 2015, 09:50 »
1) the ROM folder containing a mixture of merged, unmerged and split sets should be used as the SOURCE directory in the REBUILDER; a newly created, empty folder should be your DESTINATION directory.
2) Yes, the DESTINATION will contain newly created zip files for ALL the sets it can create. Your DESTINATION folder will contain the BEST POSSIBLE collection of split sets made from your original SOURCE directory. If you flag "remove matched sourcefile" every file in SOURCE which finds a new home in DESTINATION will be cancelled from SOURCE. If you leave it unflaged your SOURCE will remain untouched.
3) They will all be of the same compression level.
4) it works for samples as it works for roms.
5) that's tricky! CHDs are a rather special format, and to be honest clrmame doesn't handle them very well.
You did right, it is always better to let clrmame create it's own datfile from MAME executable.
Give it a try, and ask again form more directions if you encounter problems.
2) Yes, the DESTINATION will contain newly created zip files for ALL the sets it can create. Your DESTINATION folder will contain the BEST POSSIBLE collection of split sets made from your original SOURCE directory. If you flag "remove matched sourcefile" every file in SOURCE which finds a new home in DESTINATION will be cancelled from SOURCE. If you leave it unflaged your SOURCE will remain untouched.
3) They will all be of the same compression level.
4) it works for samples as it works for roms.
5) that's tricky! CHDs are a rather special format, and to be honest clrmame doesn't handle them very well.
You did right, it is always better to let clrmame create it's own datfile from MAME executable.
Give it a try, and ask again form more directions if you encounter problems.
37
clrmame Discussion / Re: XP Users again
« on: 01 October 2015, 07:09 »
I just found an old XP laptop.
Installed ClrMAMEpro 4.024 (32bit) and it works perfectly, no problem of any kind in working with it.
Installed ClrMAMEpro 4.024 (32bit) and it works perfectly, no problem of any kind in working with it.
38
clrmame Discussion / Re: wrong merging logic with new MAME 0.162 (MESS/MAME together) - another bug
« on: 13 September 2015, 08:45 »
Nothing has changed in respect to MAME.
Let's assume that the MAME.EXE executable is in D:\MAME
You will need to put your ROMs (former MAME roms + former MESS bios) into D:\MAME\ROMS
Your samples (former MAME samples + former MESS samples) into D:\MAME\SAMPLES
Your CHDs can stay in the ROMS subdir, each of them in its own subdir; or alternatively you can group all of them into D:\MAME\CHDS, and add this path to mame.ini
Regarding software: put them into D:\MAME\SOFTWARE each system in its own subdir.
This should be enough to make it run correctly.
Let's assume that the MAME.EXE executable is in D:\MAME
You will need to put your ROMs (former MAME roms + former MESS bios) into D:\MAME\ROMS
Your samples (former MAME samples + former MESS samples) into D:\MAME\SAMPLES
Your CHDs can stay in the ROMS subdir, each of them in its own subdir; or alternatively you can group all of them into D:\MAME\CHDS, and add this path to mame.ini
Regarding software: put them into D:\MAME\SOFTWARE each system in its own subdir.
This should be enough to make it run correctly.
39
Undumped Wiki / Sega NAOMI - Oinori
« on: 23 August 2015, 17:18 »
Salve a tutti,
sembra che il gioco "Oinori Daimyojin Matsuri Festival" (http://mamedev.emulab.it/undumped/index.php?title=Oinori_Daimyojin_Matsuri_Festival) non esista. Si tratta di una traduzione in inglese sbagliata.
L'unico gioco è "Oinori Daimyojin Matsuri" (http://mamedev.emulab.it/undumped/index.php?title=Oinori_Daimyojin_Matsuri) già dumpato ed incluso in MAME.
Per vostro riferimento, la pagina ufficiale Sega è: http://sega.jp/arcade/matsuri/
Ed anche il post #89 di brolly in questo forum: http://www.hyperspin-fe.com/topic/390-official-sega-naomi-wheel-thread/page-5
sembra che il gioco "Oinori Daimyojin Matsuri Festival" (http://mamedev.emulab.it/undumped/index.php?title=Oinori_Daimyojin_Matsuri_Festival) non esista. Si tratta di una traduzione in inglese sbagliata.
L'unico gioco è "Oinori Daimyojin Matsuri" (http://mamedev.emulab.it/undumped/index.php?title=Oinori_Daimyojin_Matsuri) già dumpato ed incluso in MAME.
Per vostro riferimento, la pagina ufficiale Sega è: http://sega.jp/arcade/matsuri/
Ed anche il post #89 di brolly in questo forum: http://www.hyperspin-fe.com/topic/390-official-sega-naomi-wheel-thread/page-5
40
clrmame Discussion / Re: Windows XP Users
« on: 17 August 2015, 10:10 »
I'm on win95! You insensitive clod! 