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

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.

1

clrmame Discussion / Re: Validating samples in clones

« on: 03 December 2020, 23:53 »

Nice tip for ClrMamePro! Looking through the set information is very helpful! I'm always learning something new about the software. That makes sense they have no split-sample sets, I'll have to remember that. On a side note I didn't know clones only listed the "non-merge" roms (in ClrMamePro--I'm so used to looking at the DAT which lists the clone and merge roms tagged accordingly) which makes sense really when merging, it's clever and easy to make a split-merge set or just merge that small list up to the parent.

With the OP it's exactly as you thought. When the sampleof tag is present but there's no sample list the clones display as if the clone has no samples.

I prefer to store my sets split-merge. I say this loosely as to not offend anyone but the Libretro community seems to mostly promote non-merged sets. In fact their cores can't handle merged sets and they will only run the parent from a merged set.

I remember when I discovered mame does hash matching first. I though what's the point of filenames for each set. I think the boundary extends as far as the <game>.zip file though but inside the zip I renamed every rom 1, 2, 3, 4, 5, 6, etc. up to about 26 and the game ran perfectly. I thought that's pretty nifty and was able to exploit that when using neogeo unibios. I was able to add multiple versions of unibios into one zip and just renamed the "equal name different hash" files. It works great.

I appreciate the help in understanding how the samples work and I hope you have a wonderful and safe holiday season! I'll keep an eye on the Sentinel!

2

clrmame Discussion / Re: Validating samples in clones

« on: 03 December 2020, 19:31 »

To add a little perspective some folks are making a modified DAT for mame4all like 0.37b5 or close to it and removed the samples from the clones thinking the sampleof tag would push the verification to the parent for both the parent and clone. It shows no errors so they think it’s right. I didn’t I think that it is right and started doing some research and then ended up here asking you because I know you would know the answer to these questions!

3

clrmame Discussion / Re: Validating samples in clones

« on: 03 December 2020, 19:25 »

Yes you are correct I used current MAME last night and used the -listxml parameter piped to a file and noticed that. I didn’t load it into ClrMamePro to see if it prompted a conflict. I think invaders is a sample of itself with no samples and the clones are sampleof=“invaders” but do have have samples listed.

Just to be clear so the clone will only verify the samples listed in its own  set and the sampleof tag is basically what the set will be named or what it’s expecting it to be named?

Using the case in the OP it doesn’t give an error because the clone doesn’t have any samples to verify so technically it is correct?

One last question from the example if I could. If the parent has a sample folder named dkong with actual samples and the clone has no samples but has the sampleof tag why not an error or why doesn’t it (the clone) remove the samples from the dkong folder if that makes sense.

4

clrmame Discussion / Re: Validating samples in clones

« on: 03 December 2020, 16:41 »

Roman, thanks a bunch for the help. I will mention the samples should be listed or remove the tag as it serves no real purpose.

I tried to find the answer then I churned it around for a while in my thoughts and still couldn’t come to a conclusion.

I thought if the parent is present and the samples are listed then they are verified by the parent. So I was looking at it thinking is the clone even doing anything in this scenario as the parent already did it and the clone has no information on the samples.

It seems like if nothing is listed in the clone (even with the tag) then it has no information for comparison and the tag is kind of like deprecated OR I thought it is passing all verification to the parent with the tag.

It reminded me of the chicken or the egg. Who’s doing the work, the parent or the clone. You can’t remove the parent or it changes the whole dynamic.

I removed the parent but left the clone with the sampleof tag and I would get “Missing alternative sample folder will be added as sample-only set”. Does that mean that ClrMamePro tried to correct it and the samples will be parsed with the same name as the clone so dkongpe would be the correct sample name vs actually being dkong due to the parent being not present. Basically it separates them?

After all that I thought there’s no clear error shown, in fact there’s no error shown at all in the example above plus it shows no samples missing. So I thought I need to ask someone that knows what’s happening under the hood so the DAT is built correctly.

I seem to spend a lot of time using old versions lately on low spec hardware like the Pi and such as they run pretty decent. I just wish I could find a DAT with region info to take advantage of 1G1R.

5

clrmame Discussion / Validating samples in clones

« on: 03 December 2020, 02:58 »

Hi I was wondering if I could get some help understanding how ClrMamePro would process an old DAT with samples. It's for an old version of MAME (mame4all). I removed all the information except the samples for dkong and a clone (dkongpe) to focus on that part of the DAT if it helps.

If the clone, in this case, dkongpe doesn't list any samples i.e. - <sample name="run01.wav"/>, etc. but it does have the tag <sampleof=dkong> will it look to the parent (dkong) to validate the set? I tried it and it shows no missing but I can't help to think it's like a false-positive and not really validating it. I'm so used to seeing the samples listed out in the clones that it looks off to me to see no sample list and just the <sampleof=dkong> tag in the game header information but maybe it's fine to do it this way?

Another question if you used something like DATUtil for example to pull just clones will it fail with no samples actually listed and only the tag <sampleof=dkong>? Is their a more "correct" way to do it as in listing each sample file out in each clone or just using the <sampleof=dkong> tag for all clones?


   <game name="dkong">
      <description>Donkey Kong (US set 1)</description>
      <year>1981</year>
      <manufacturer>Nintendo of America</manufacturer>
      <sample name="run01.wav"/>
      <sample name="run02.wav"/>
      <sample name="run03.wav"/>
      <sample name="jump.wav"/>
      <sample name="dkstomp.wav"/>
   </game>
   <game name="dkongpe" cloneof="dkong" romof="dkong" sampleof="dkong">
      <description>Donkey Kong - Pauline Edition</description>
      <year>2013</year>
      <manufacturer>hack</manufacturer>
   </game>

6

clrmame Discussion / Re: malware on your download site

« on: 31 July 2018, 16:57 »

I understand what you're saying completely. I deal with them daily and new threats on edge devices with public facing services through government alerting and other channels watching for threats. No serious virus, trojan, malware or what not has gotten loose on my watch, knock on wood. I always send people their as a "neutral" place to get a second opinion with questionable files. I spent last 22 years working for the state mainly doing firewalls, routers, switches, VMWare and of course virus scan is mine too (uugh! and prior to that a whole lot of years at UPS doing the same. We use enterprise deployment tools pushing to 100's of PCs. I have a fairly complex hierarchy of policy inheritance in place for exceptions and other challenging requests. Unfortunately we aren't a large enough organization to have dedicated IT roles like a bank or something that employees 10's of thousands so we wear many hats on a daily basis.

7

clrmame Discussion / Re: malware on your download site

« on: 30 July 2018, 16:46 »

Roman, I am not sure if you ever heard of Virus Total https://www.virustotal.com. It's a handy site that allows you to upload fairly large executables (I believe it's up to 128MB now) and scans them with roughly 60 virus scan engines with current signatures from different vendors and gives you the results. It's interesting to see how some vendors report false positives and others clean. It's very easy to use with a drag-and-drop interface, URL or search. Actually you can use it to scan any file type.

All the main vendors are covered and the ones you never heard of too. The details tab has some good logistics information. I use it all the time if I have a "questionable" file. Once a file is uploaded and "finger printed" (SHA-256 hash calculated) you can link the results or if it's a file that's been uploaded prior it will just calculate the hash locally and link the last analysis so you know if a rescan with current signatures might detect something that wasn't prior. Anyway this thread came up while looking for something else and I thought it might be helpful if people have questions or if you haven't heard of it because I find it a very handy tool.

8

clrmame Discussion / Re: ROMs dumped from clones with matching hashes to BIOS files

« on: 11 July 2018, 22:55 »

Thank you Roman for the update and answering the questions! I appreciate it and have a wonderful evening.

9

clrmame Discussion / Re: ROMs dumped from clones with matching hashes to BIOS files

« on: 10 July 2018, 23:38 »

@coccola - Sorry it might be miscommunication here. The games work fine and nothing is broken. I think Roman knew that from the beginning, as he pointed out, that they should run fine and he was spot on.

Really the whole paragraph is incorrect. The games do not need the files to be present in the clone to work as stated. They will look to the parent/BIOS and use hash matching. Basically you don't even need them to be named correctly and name them anything you want and it will still work. I guess I was just pointing on how they are parsed and it's not really a bug, well maybe, depending on how you interpret the DAT information.

Yes sir I definitely know who Roman is and I do sing his praises and love his responses. Cool, calm and collect. Maybe he has to pistol whip the radical purveyor occasionally. I've been at this desk for 22 years and I believe he has been developing ClrMamePro for 20 or 21 years, I think something like that. I read a lot more than I post here. Anyway I have no doubts I couldn't even remotely match his institutional knowledge of MAME nor dictate his autonomy over ClrMamePro. I happened upon the issue by mere chance and decided to share it as I always have found Roman to be a reasonable well written man. And...viola, look at us now with an awesome update on the horizon to quiet the masses about these few, but nonetheless monumental, games!

Anyway, joking aside, I appreciate it and I am definitely not trying to rub you the wrong way by any means so I'll let that go now.

@Roman - Thank you for the update. I think it sounds perfect and look forward to the release. Is there a difference between a merge tag and element?

10

clrmame Discussion / Re: ROMs dumped from clones with matching hashes to BIOS files

« on: 09 July 2018, 15:09 »

@coccola - Thank you for the information I appreciate it. I do find that information on different forums frequently. That's what I was hoping to avoid, needing to manually process files and let ClrMamePro do it's thing. Technically, depending on the emulator, they wouldn't need to be added as stated in the paragraph to work even. If the PGM BIOS is located in the ROMs folder or "search path" it will work. Basically it will find the ROMs in the parent or BIOS. I think Roman's last post was more the direction I was hoping for, basically looking at how the DAT/ROMs are processed.

@Roman - I am glad there's others that take the weekend off too. When I was young taking time away from a computer was unheard of and now it's the opposite. Being older I actually spend my weekends with family/friends, doing "chores", honey-do-lists, etc. Basically spend time away from a PC. Well at least most weekends unless it's old school gaming in a group setting always seems to be a hit at social/family gatherings!

11

clrmame Discussion / Re: ROMs dumped from clones with matching hashes to BIOS files

« on: 06 July 2018, 23:27 »

Hi Roman and thank you for the reply. Yes I see your points and they make perfect sense in how they may be interpreted in more than one way and also end up with duplicate files possibly. You're right they do run fine. I spent a few hours yesterday going through the DAT and testing it to understand what was happening.

I've seen people giving out wrong information on what's happening on other forums. These "errors" (as they call them) have been in several versions of the lr-fbalpha DAT now so the posts are far and wide. They didn't bother to view the DAT and see what's happening and just tell people to manually add the "missing" files. Maybe there's no answer here but just an awareness.

I completely became aware when I had upgraded from a really old version and extra files where being removed between the two versions. I went back to the old version for testing and it does indeed leave them in the archive in non-merged mode and removes them in current ClrMamePro in non-merged mode. Just to clarify has the processing changed between versions and it's not a setting I am missing correct?

There's 3 files are listed below.

BIOS (pgm.zip):
<rom name="pgm_t01s.rom" size="2097152" crc="1a7123a0"/>
<rom name="pgm_m01s.rom" size="2097152" crc="45ae7159"/>
<rom name="bios.u42" size="131072" crc="517cf7a2"/>

CLONE (thegladpcb.zip):
<rom name="pgm_t01s.u72" size="2097152" crc="1a7123a0"/>
<rom name="pgm_m01s.u4" size="2097152" crc="45ae7159"/>
<rom name="bios.42" size="131072" crc="517cf7a2"/>

I do have another example but it's also from the same parent/BIOS set just a different clone.

BIOS (pgm.zip):
<rom name="pgm_p02s.u20" size="131072" crc="78c15fa2"/>

CLONE (dmnfrntpcb.zip):
<rom name="pgm_p02s.u42" size="131072" crc="78c15fa2"/>

   <game isbios="yes" name="pgm">
      <description>PGM (Polygame Master) System BIOS [BIOS only]</description>
      <year>1997</year>
      <manufacturer>IGS</manufacturer>
      <rom name="pgm_t01s.rom" size="2097152" crc="1a7123a0"/>
      <rom name="pgm_m01s.rom" size="2097152" crc="45ae7159"/>
      <rom name="pgm_p01s.u20" size="131072" crc="e42b166e"/>
      <rom name="pgm_p02s.u20" size="131072" crc="78c15fa2"/>
      <rom name="ddp3_bios.u37" size="524288" crc="b3cc5c8f"/>
      <rom name="bios.u42" size="131072" crc="517cf7a2"/>
   </game>
   <game name="dmnfrnt" romof="pgm">
      <description>Demon Front (V105)</description>
      <year>2002</year>
      <manufacturer>IGS</manufacturer>
      <rom name="v105_16m.u5" size="2097152" crc="bda083bd"/>
      <rom name="t04501.u29" size="8388608" crc="900eaaac"/>
      <rom name="a04501.u3" size="8388608" crc="9741bea6"/>
      <rom name="a04502.u4" size="8388608" crc="e104f405"/>
      <rom name="a04503.u6" size="8388608" crc="bfd5cfe3"/>
      <rom name="b04501.u9" size="8388608" crc="29320b7d"/>
      <rom name="b04502.u11" size="2097152" crc="578c00e9"/>
      <rom name="w04501.u5" size="8388608" crc="3ab58137"/>
      <rom name="dmnfrnt_igs027a.bin" size="16384" status="nodump"/>
      <rom name="v105_32m.u26" size="4194304" crc="c798c2ef"/>
      <rom name="pgm_t01s.rom" merge="pgm_t01s.rom" size="2097152" crc="1a7123a0"/>
      <rom name="pgm_m01s.rom" merge="pgm_m01s.rom" size="2097152" crc="45ae7159"/>
      <rom name="pgm_p01s.u20" merge="pgm_p01s.u20" size="131072" crc="e42b166e"/>
      <rom name="pgm_p02s.u20" merge="pgm_p02s.u20" size="131072" crc="78c15fa2"/>
      <rom name="ddp3_bios.u37" merge="ddp3_bios.u37" size="524288" crc="b3cc5c8f"/>
      <rom name="bios.u42" merge="bios.u42" size="131072" crc="517cf7a2"/>
   </game>
   <game name="dmnfrntpcb" cloneof="dmnfrnt" romof="dmnfrnt">
      <rom name="demonfront_v107-u43.bin" size="2097152" crc="671d8a31"/>
      <rom name="t04501.u29" merge="t04501.u29" size="8388608" crc="900eaaac"/>
      <rom name="a04501.u3" merge="a04501.u3" size="8388608" crc="9741bea6"/>
      <rom name="a04502.u4" merge="a04502.u4" size="8388608" crc="e104f405"/>
      <rom name="a04503.u6" merge="a04503.u6" size="8388608" crc="bfd5cfe3"/>
      <rom name="b04501.u9" merge="b04501.u9" size="8388608" crc="29320b7d"/>
      <rom name="b04502.u11" merge="b04502.u11" size="2097152" crc="578c00e9"/>
      <rom name="w04501.u5" merge="w04501.u5" size="8388608" crc="3ab58137"/>
      <rom name="dmnfrnt_igs027a.bin" merge="dmnfrnt_igs027a.bin" size="16384" status="nodump"/>
      <rom name="demonfront_v107-u62.bin" size="4194304" crc="cb94772e"/>
      <rom name="pgm_t01s.rom" merge="pgm_t01s.rom" size="2097152" crc="1a7123a0"/>
      <rom name="pgm_m01s.rom" merge="pgm_m01s.rom" size="2097152" crc="45ae7159"/>
      <rom name="pgm_p02s.u42" size="131072" crc="78c15fa2"/>
   </game>

I don't know if you heard of RetroPie (using a Raspberry Pi) and the emulator is called lr-fbalpha (Libretro core) using Retroarch as the frontend. Here's the [Github page][https://github.com/libretro/fbalpha/tree/master/dats] with the DATs I used based off FBA 0.2.97.43.

I don't know of any MAME examples. I did look at 0.198 of the same games and none of these examples are valid and it looks much cleaner in there now.

Kind off topic but I was wondering is it possible to tell which merge files belong to the parent and which ones to the BIOS or do you need to check each "ROM" entry to really know? I always look at the Clone/Parent/BIOS unless there is none. I tried building some ROM sets out of zips with DatUtil and it works great for "flat" sets but I was trying to figure out a way to use it to build a DAT with merge information but had no luck. I suppose the program needs a way to know the parent/clone/bios relationships. Can you pull a parent and all clones (possibly the BIOS) in ClrMamePro. I know I build fix DATs of missing ROMs frequently and that works great.

Are files flagged as "no dump" or "bad dump" processed the same as regular ROMs at default settings?

I know there's a reason here I am sure but when you disable separate BIOS sets it still complains they are missing when you actually check it as an option, how come?

Anyway thank you for all you do and I often sing your praises on other forums. Oh and I always think of the Sentinel now when I visit! Have a great weekend!

12

clrmame Discussion / ROMs dumped from clones with matching hashes to BIOS files

« on: 06 July 2018, 15:58 »

I was wondering if you could take a look at the example below. When I run this DAT through ClrMamePro (Non-Merged Sets) it discards the ROM's in thegladpcb that have an equal hash but a different name from the BIOS ROM files. Their is no merge information so it seems like it should work. I am running 4.034 64-bit. I have a few ROMs from the current FBA (lr-fbalpha) that are doing the same thing.

When running 4.023 32-bit it does keep the equal hash files in Non-Merged mode. I don't know if I set something differently in that version or if it just worked differently back then. I spent quite a while trying to figure out if there's an option I was missing to get the current version working the same.

```
<game isbios="yes" name="pgm">
      <description>PGM (Polygame Master) System BIOS [BIOS only]</description>
      <year>1997</year>
      <manufacturer>IGS</manufacturer>
      <rom name="pgm_t01s.rom" size="2097152" crc="1a7123a0"/>
      <rom name="pgm_m01s.rom" size="2097152" crc="45ae7159"/>
      <rom name="pgm_p01s.u20" size="131072" crc="e42b166e"/>
      <rom name="pgm_p02s.u20" size="131072" crc="78c15fa2"/>
      <rom name="ddp3_bios.u37" size="524288" crc="b3cc5c8f"/>
      <rom name="bios.u42" size="131072" crc="517cf7a2"/>
   </game>
   <game name="theglad" romof="pgm">
      <description>The Gladiator - Road Of The Sword / Shen Jian (V101) [Incomplete Dump]</description>
      <year>2003</year>
      <manufacturer>IGS</manufacturer>
      <rom name="v101.u6" size="524288" crc="f799e866"/>
      <rom name="t04601.u33" size="8388608" crc="e5dab371"/>
      <rom name="a04601.u2" size="8388608" crc="d9b2e004"/>
      <rom name="a04602.u4" size="8388608" crc="14f22308"/>
      <rom name="a04603.u6" size="8388608" crc="8f621e17"/>
      <rom name="b04601.u11" size="8388608" crc="ee72bccf"/>
      <rom name="b04602.u12" size="4194304" crc="7dba9c38"/>
      <rom name="w04601.u1" size="8388608" crc="5f15ddb3"/>
      <rom name="theglad_igs027a_execute_only_area" size="392" status="nodump"/>
      <rom name="theglad_igs027a_v100_overseas.bin" size="15992" crc="02fe6f52"/>
      <rom name="v107.u26" size="2097152" crc="f7c61357"/>
      <rom name="pgm_t01s.rom" merge="pgm_t01s.rom" size="2097152" crc="1a7123a0"/>
      <rom name="pgm_m01s.rom" merge="pgm_m01s.rom" size="2097152" crc="45ae7159"/>
      <rom name="pgm_p01s.u20" merge="pgm_p01s.u20" size="131072" crc="e42b166e"/>
      <rom name="pgm_p02s.u20" merge="pgm_p02s.u20" size="131072" crc="78c15fa2"/>
      <rom name="ddp3_bios.u37" merge="ddp3_bios.u37" size="524288" crc="b3cc5c8f"/>
      <rom name="bios.u42" merge="bios.u42" size="131072" crc="517cf7a2"/>
   </game>
   <game name="thegladpcb" cloneof="theglad" romof="theglad">
      <rom name="glad_v100.43" size="524288" crc="bcf3b172"/>
      <rom name="t04601.u71" size="8388608" crc="e5dab371"/>
      <rom name="a04601.u30" size="8388608" crc="d9b2e004"/>
      <rom name="a04602.u31" size="8388608" crc="14f22308"/>
      <rom name="a04603.u32" size="8388608" crc="8f621e17"/>
      <rom name="b04601.u40" size="8388608" crc="ee72bccf"/>
      <rom name="b04602.u41" size="4194304" crc="7dba9c38"/>
      <rom name="w04601.u8" size="8388608" crc="5f15ddb3"/>
      <rom name="igs29.bin" size="2097152" crc="51acb395"/>
      <rom name="thegladpcb_igs027a_execute_only_area" size="392" status="nodump"/>
      <rom name="thegladpcb_igs027a_v100_japan.bin" size="15992" crc="d7f06e2d"/>
      <rom name="igs_v100.62" size="2097152" crc="0f3f511e"/>
      <rom name="pgm_t01s.u72" size="2097152" crc="1a7123a0"/>
      <rom name="pgm_m01s.u4" size="2097152" crc="45ae7159"/>
      <rom name="bios.42" size="131072" crc="517cf7a2"/>
   </game>
```

13

clrmame Discussion / Re: MAME 0.106 CHDs version mismatch

« on: 31 March 2014, 22:44 »

SHOOT, you weren't supposed to give me the answer...YET! It took me a bit but I did actually find the game with your hints this past weekend! I watched a few video's and also a remake of the game!

I really love some of the old C64 games like Legacy of the Ancients, The Legend of Blacksilver, Questron, Phantasie Series, Alternate Reality: The City/Dungeon, etc. but there is one game that I never could solve nor find a walk through for and it still stumps me to this day. I tried to figure it out a few years ago again but had no luck. I bet I spent a good few months on and off for several hours using freeze states in CCS64.

Have you ever heard of Gemstone Healer? I so want to solve that game but I can't figure it out. The placement order of the gemstone pieces on the alter with the other items. I have screenshots of all the pieces of every item in the dungeon, I made a map (the dungeon name is the random seed for the map so it's easy to get the same dungeon). I tried everything I could think of and I just can't figure out what the solution is.

Ok I know that's way off topic but I still love the old C64 games.

14

clrmame Discussion / Re: MAME 0.106 CHDs version mismatch

« on: 28 March 2014, 15:57 »

Hey Roman, you're the best! I changed the version to 3 where you specified. Then I had to run chdman from the command line to get the correct syntax. Basically version .106 doesn't like the verify but -verify and all is currently verifying nicely now. Thank you Roman and have a super weekend.

Oh, I know you said your Avatar is from a game. I still have no clue which, any chance for a small hint?!

15

clrmame Discussion / MAME 0.106 CHDs version mismatch

« on: 27 March 2014, 20:51 »

I was hoping for some clarification on MAME 0.106b CHDs. When I run them through ClrMamePro EVERY CHD shows "required chd version mismatch: <rom name> [found version: 3] [required version: 5]".

I am not sure but I don't think version 5 CHDs were used in 2006 so I think it's an error? Maybe the newer versions of ClrMamePro don't "recognize" the older CHDs?

I did use the executable to build the DAT and I also tried -listxml from the command line and still the same results.

Is anyone able to shed some light on it.

Thank you!

Edit: I am using version cmpro 4.014a!

16

clrmame Discussion / Re: MAME ROM's and CHD's in separate subdirectories

« on: 04 November 2011, 23:34 »

Hey Roman, that really helped a lot in understanding the program. I just wanted to say thank you very much! I have been using the program for years but I mostly just follow the tutorials and don't vary beyond that. Basically just a lurker in the forums.

The eye avatar you use is like a trade mark that I always associate with your name and a good thing. I know you probably have explained things over and over 100's of times and it can be a thankless "job" I am sure, but I just want to say thank you very much and have a great weekend!

17

clrmame Discussion / Re: MAME ROM's and CHD's in separate subdirectories

« on: 03 November 2011, 22:30 »

Thanks Roman for the great explanation, that really helped a LOT in understanding things! You're also right in that wasn't what I was wanting it to do. Can I ask one more question?

If you don't use 'System Default Paths' in the Scanner and you don't use them in the Rebuilder what happens when you drag-n-drop files on the scan Results window?

I see the 'Destination' under the Rebuilder shows the first ROM path that I chose under 'Settings'. Is that setting/path doing anything at all in that scenario?

Or does it just use the paths from 'Settings' and leave them in there original locations?

What happens if it's a new set in that scenario? Does it have a default location (like the first path in the Settings/ROM-Paths) to rebuild/create the set?

I hope that makes sense!

18

clrmame Discussion / Re: MAME ROM's and CHD's in separate subdirectories

« on: 03 November 2011, 20:33 »

Thanks for the reply Roman, I appreciate it.

I guess the separation is more from when downloading the ROM's, CHD's and LD-CHD's. They are separate torrents for each so when I join the torrent I know where to download them. I guess it wouldn't matter if it's one large subdirectory since I don't think the torrent would remove "extra" files?

I know I am completely green when it comes to understanding what you wrote so can I give you my example.

What I do is download the newest ClrMamePro which I do before updating the ROM's each time. I add 3 directories to Settings/ROM paths. ROMs, CHDs, LD-CHDs and 1 to the Samples subdirectory called Samples.

Under Rebuilder it shows the 1st listed ROM path in Destination but use system default paths is unchecked. Then I run the scanner with Sets, ROMs, Samples and CHDs checked and all the Fix options checked, (I guess I am not quite sure what the difference is between a Set and a ROM) and also I always click Auto-detect under Scanner/Systems, not sure if that's needed. Lastly the Hash & CHD/Run Analysis and Fix File (If Possible). It's a "habit" at this point that I always do by default for everything I scan. After it runs I dump the update packs on it and let it fix the sets.

After it completes it copies almost everything over to the ROMs folder but it does leave a few CHD's in the CHD folder. I am not sure but I think that's new or possibly different in the newest version?

When you say using or not using System Default Paths is that the option under Rebuilder? Also I didn't quite understand when you said if the set is not available, the 1st rompath is used?

Sorry if these are newbie questions since most tutorials don't quite explain the options but just the basic functionality. I looked for an answer but figured this would be the best place to try and understand how it works.

19

clrmame Discussion / MAME ROM's and CHD's in separate subdirectories

« on: 03 November 2011, 15:47 »

I was wondering if you could help me with some settings in ClrMamePro? Prior to version 4 I had my sets separated like Pleasursdome for downloading into ROMs, CHD's and LD-CHD's.

When I run version 4 it seems to put all the files into one directory (ROM's). I wasn't sure what I was doing, so I manually cut/pasted the files back into the folders and ran it again and lost and handful of CHD's on the 2nd or 3rd run (insanity theory).

I had a backup and just cut/pasted all the existing files along with the deleted files into working ROM's directory and it finally completed fine.

I don't mean to be long winded but is there a switch or option to keep the files separated in the directories but still check it like version 3.x or is the separation really not necessary?

I am sorry if this is a repeat topic and thank you for the help!