1
clrmame Discussion / Re: may found bug
« on: Today at 12:04 »
ah...double files...not folders...ok...I will have a look ;-)
who in the world uses equally named files ;-)
who in the world uses equally named files ;-)
- 13 December 2018, 17:32
- 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.
2
clrmame Discussion / Re: may found bug
« on: Today at 10:01 »
Eh? Nope..not here. All folders remain as they should...
So..what did you do exactly again? ;-)
Let's start with your Folder 1 / 2 example again....and then you add the new dat where? And what do you do then?
So..what did you do exactly again? ;-)
Let's start with your Folder 1 / 2 example again....and then you add the new dat where? And what do you do then?
3
clrmame Discussion / Re: may found bug
« on: Yesterday at 21:13 »
http://mamedev.emulab.it/clrmamepro/binaries/cmpro20181212.rar
;-)
thanks for your reports by the way....
;-)
thanks for your reports by the way....
4
clrmame Discussion / Re: may found bug
« on: 11 December 2018, 22:33 »
hmmm...can't repeat this....what did you actually do? Can you describe it step by step, like, what was the initial folder structure, how and where did you add the first file, how/where did you place the update file etc....
5
clrmame Discussion / Re: may found bug
« on: 10 December 2018, 20:48 »
should be fixed...
http://mamedev.emulab.it/clrmamepro/binaries/cmpro20181210.rar
http://mamedev.emulab.it/clrmamepro/binaries/cmpro20181210.rar
6
clrmame Discussion / Re: may found bug
« on: 08 December 2018, 17:06 »
Thanks for reporting. I will have a look for now hit refresh.
7
clrmame Discussion / Re: filenames are too long
« on: 08 December 2018, 08:28 »
yes, added to the "Hints and Tricks - 1000 things you always wanted to know" thread
8
clrmame Discussion / #0021 - Long folder/ path names
« on: 08 December 2018, 08:27 »
Standard windows path length limit is something around 260 characters.
NTFS supports 32k, however to actually use them, you need to use a different rompath style, you need to prefix them with for example: \\?\e:\mame\roms\neogeo instead of just e:\mame\roms\neogeo
So if you already have a setup rompath where you picked a folder with the folder dialog, you can hit F2 to edit the path to add the pre-string \\?\ to it
NTFS supports 32k, however to actually use them, you need to use a different rompath style, you need to prefix them with for example: \\?\e:\mame\roms\neogeo instead of just e:\mame\roms\neogeo
So if you already have a setup rompath where you picked a folder with the folder dialog, you can hit F2 to edit the path to add the pre-string \\?\ to it
9
clrmame Discussion / Re: Latest "forum" build feedback
« on: 01 December 2018, 16:54 »
Thanks for the feedback....surely the profiler optimization is only for such 10000 dats guys out there....but I start to like it 
10
clrmame Discussion / Re: filenames are too long
« on: 17 November 2018, 13:12 »
so....your issue is...hmm..no issue anymore? ;-)
11
clrmame Discussion / Re: filenames are too long
« on: 17 November 2018, 09:17 »
Thanks for the datfile.....
I will have a look
I will have a look
12
clrmame Discussion / Re: filenames are too long
« on: 16 November 2018, 17:55 »
So any news on this?
I've did some tests with extremly long path/set/filenames with some custom made dats and working with the \\?\ prefix for all paths works fine here
I've did some tests with extremly long path/set/filenames with some custom made dats and working with the \\?\ prefix for all paths works fine here
13
clrmame Discussion / Re: filenames are too long
« on: 15 November 2018, 08:54 »
spaces in pathanmes aren't a problem
..maybe you don't follow the general storing method?
rompath\setname\file1...n for decompressed sets
rompath\setname.rar(.zip/.7z) where the archive then contains file1...n for compressed sets
so if you a rompath "\\?\g:\nintendoswitch\dlc 0000-0049\", and a set called xyz with a single rom called disc.iso, you should have them stored like:
"\\?\g:\nintendoswitch\dlc 0000-0049\xyz\disc.iso"
So...maybe you should a) send me the used datfile and b) let me know how the files are stored on your system ...so I can try to repeat the behaviour and the filestructure here...
..maybe you don't follow the general storing method?
rompath\setname\file1...n for decompressed sets
rompath\setname.rar(.zip/.7z) where the archive then contains file1...n for compressed sets
so if you a rompath "\\?\g:\nintendoswitch\dlc 0000-0049\", and a set called xyz with a single rom called disc.iso, you should have them stored like:
"\\?\g:\nintendoswitch\dlc 0000-0049\xyz\disc.iso"
So...maybe you should a) send me the used datfile and b) let me know how the files are stored on your system ...so I can try to repeat the behaviour and the filestructure here...
14
clrmame Discussion / Re: filenames are too long
« on: 15 November 2018, 08:25 »
Sure it supports it.
Go to settings and change your rompaths (e.g. hit F2 on your setup ones and add the prefix \\?\)
Go to settings and change your rompaths (e.g. hit F2 on your setup ones and add the prefix \\?\)
15
clrmame Discussion / Re: filenames are too long
« on: 14 November 2018, 12:27 »
The operating system limits the pathname length, not cmpro. In cmpro there is no limt for the filename.
Most likely your used rompath + setname hits the standard windows limit which is 260 characters.
NTFS supports 32k, however to actually use them, you need to use a different rompath style, you need to prefix them with for example: \\?\e:\mame\roms\neogeo instead of just e:\mame\roms\neogeo
Most likely your used rompath + setname hits the standard windows limit which is 260 characters.
NTFS supports 32k, however to actually use them, you need to use a different rompath style, you need to prefix them with for example: \\?\e:\mame\roms\neogeo instead of just e:\mame\roms\neogeo
16
clrmame Discussion / Re: Cmpro not fixed subfolder sets
« on: 07 November 2018, 22:08 »
Lost? Looks like a wrong size or checksum in mame‘s listxml output. That‘s all
17
clrmame Discussion / Re: Cmpro not fixed subfolder sets
« on: 07 November 2018, 19:17 »
so after checking your scenario I can say everything looks ok
In your set the parent part misses two files (2x 2097152 bytes long, crc 225c... and a1d1....)...you simply don't have them....so they are shown as missing
Regarding the clone, you do have the 2 files (2x 2097152 bytes long: crc d448... and c5af4...) but according to MAME'S database your files have the wrong file size (but the correct crc32). Fixing fails because cmpro can't find a 16777216 bytes block which matches the checksum.
Looks to be a bug in MAME since either the file size or the checksum is wrong....I guess they missed to also update the crc32 after reducing the size
In your set the parent part misses two files (2x 2097152 bytes long, crc 225c... and a1d1....)...you simply don't have them....so they are shown as missing
Regarding the clone, you do have the 2 files (2x 2097152 bytes long: crc d448... and c5af4...) but according to MAME'S database your files have the wrong file size (but the correct crc32). Fixing fails because cmpro can't find a 16777216 bytes block which matches the checksum.
Looks to be a bug in MAME since either the file size or the checksum is wrong....I guess they missed to also update the crc32 after reducing the size
18
clrmame Discussion / Re: Cmpro not fixed subfolder sets
« on: 07 November 2018, 07:59 »
well...I will have a closer look later today but actually it looks fine...
1) it seems to need the xt files in the root folder not in the mu100r subfolder....that's why it says missing
2) it seems that the 2 files have a wrong size and cmpro tries to fix it but fails...well..then cmpro wasn't able to find a datablock with the correct size and the correct checksum
so...at the first sight, no problem (with subfolders) but as I said, I will try to reproduce the scenario later on
1) it seems to need the xt files in the root folder not in the mu100r subfolder....that's why it says missing
2) it seems that the 2 files have a wrong size and cmpro tries to fix it but fails...well..then cmpro wasn't able to find a datablock with the correct size and the correct checksum
so...at the first sight, no problem (with subfolders) but as I said, I will try to reproduce the scenario later on
19
clrmame Discussion / Re: Need some advice on Mame folder structure
« on: 01 November 2018, 18:32 »
If cmpro does not offer to switch the merge modes it simply means that your datfile does not provide any parent/clone relationships at all. I assume that the provided dat was prepared to have no parent /clone relationships but be a kind of flat datfile which does represent split sets. So nothing unusual.
If you have separate dats for chds and roms it shouldn't be a problem. You only need to separate the chds and roms in different rompaths, too. So one rompath holds all chd subfolders with the chds...which can be used/setup in the chd-profile and a separate rompath holds the romset archives and is used in the roms-only-profile.
In MAME you then simply add both rompaths in the ini...
But generally speaking...if you use both anyway...why use external dats at all and not directly import the data from the MAME binary...
If you have separate dats for chds and roms it shouldn't be a problem. You only need to separate the chds and roms in different rompaths, too. So one rompath holds all chd subfolders with the chds...which can be used/setup in the chd-profile and a separate rompath holds the romset archives and is used in the roms-only-profile.
In MAME you then simply add both rompaths in the ini...
But generally speaking...if you use both anyway...why use external dats at all and not directly import the data from the MAME binary...
20
clrmame Discussion / Re: cmp 4.035 Rebuilder problem: does nothing not even writing logfile
« on: 30 September 2018, 18:33 »
I will have a look. Clrmamepro clears its temp folder (not the windows temp folder) on startup....it shouldn't do this anytime during working with it.
Update: I was right, only on cmpro startup the cmpro temp folder gets cleaned. Not during working with it. And again, it's the cmpro temp folder in the cmpro main folder. cmpro doesn't use the windows temp folder (%TEMP%) at all.
Update: I was right, only on cmpro startup the cmpro temp folder gets cleaned. Not during working with it. And again, it's the cmpro temp folder in the cmpro main folder. cmpro doesn't use the windows temp folder (%TEMP%) at all.