1
clrmame Discussion / Re: Can't get Software List paths set up properly
« on: 05 June 2021, 17:35 »
I do not touch the Software List folders after download. Aren't those pre-ordered as per the torrent structure?
- 18 April 2024, 05:44
- 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 / Can't get Software List paths set up properly
« on: 04 June 2021, 18:09 »
I checked the documentation but it gives an 404 error.
I'm unable to properly set-up the folders to check my software lists: I assign my MAME folder to the STANDARD variable and click on auto-assign.
As a result, all the systems get either assigned my ROMs or my CHDs folder.
I have a ROMs, a CHDs, a Software List ROMs and a Software List CHDs folder inside my MAME folder.
I tried to restrict the search my choosing the Software List folders as STANDARD base folder, but the folder select dialog does not let me drill down the MAME folder.
I could probably move those folders a level up, but I want to keep everything nicely contained in one MAME folder on my external drive.
I'm unable to properly set-up the folders to check my software lists: I assign my MAME folder to the STANDARD variable and click on auto-assign.
As a result, all the systems get either assigned my ROMs or my CHDs folder.
I have a ROMs, a CHDs, a Software List ROMs and a Software List CHDs folder inside my MAME folder.
I tried to restrict the search my choosing the Software List folders as STANDARD base folder, but the folder select dialog does not let me drill down the MAME folder.
I could probably move those folders a level up, but I want to keep everything nicely contained in one MAME folder on my external drive.
3
clrmame Discussion / Re: ClrMAME 64 bit crashes under Wine
« on: 07 September 2019, 20:50 »
Thanks for your suggestions, Starshadow, but Wine still crashes after I click on the OK button in the initial Welcome window.
Seems like a macOS specific bug of Wine.
Seems like a macOS specific bug of Wine.
4
clrmame Discussion / Re: ClrMAME 64 bit crashes under Wine
« on: 06 September 2019, 17:43 »
Thanks, no pressure, clrmamepro runs fine under full virtualisation anyway 
Just wanted to mention it here in case someone had the same (or a similar) problem and found a solution.
Just wanted to mention it here in case someone had the same (or a similar) problem and found a solution.
5
clrmame Discussion / Re: ClrMAME 64 bit crashes under Wine
« on: 06 September 2019, 16:41 »
In the past I only used the 32 bit versions which worked perfectly fine under any Wine and macOS combination.
It's only the 64 build that throws an exception (on macOS 10.14, the current one, and a beta of 10.15, the next one which ditches 32 bit support). I only tested the lates build 4.15 of Wine for the 64 bit build.
It's only the 64 build that throws an exception (on macOS 10.14, the current one, and a beta of 10.15, the next one which ditches 32 bit support). I only tested the lates build 4.15 of Wine for the 64 bit build.
6
clrmame Discussion / Re: ClrMAME 64 bit crashes under Wine
« on: 06 September 2019, 15:02 »
If you mean the one from May of this year, then yes.
7
clrmame Discussion / ClrMAME 64 bit crashes under Wine
« on: 05 September 2019, 21:12 »
As a happy user of clrmamepro on macOS using Wine for the last several years, I've recently been trying out the 64 bit version with the impending release of macOS 15 which no longer will support any 32 bit executable.
Sadly, even under the latest version of Wine (4.15), at launch the "Welcome to clrmamepro" message is displayed, but clrmamepro crashes as soon as I click the OK button. Other programs (e.g. mame64b itself) run fine under Wine.
I've added the backtrace to this post. If there is anything I can do to debug this issue Roman, I'll gladly try to help.
Sadly, even under the latest version of Wine (4.15), at launch the "Welcome to clrmamepro" message is displayed, but clrmamepro crashes as soon as I click the OK button. Other programs (e.g. mame64b itself) run fine under Wine.
I've added the backtrace to this post. If there is anything I can do to debug this issue Roman, I'll gladly try to help.
8
clrmame Discussion / Re: Scanning does not start
« on: 05 October 2016, 20:04 »
I took your advice and went to the WINE site to explain the bug. There I noticed they had an up-to-date build for macOS (I'd always used WineBottler, a nicely packaged version with additional features like easy environment set-up, but alas a few versions behind).
So I tried WINE 1.9.19 anyway, and there it worked! So I will use that version until WineBottler is updated.
Sorry for bothering you Roman and, once again, big thank you for your help and of course CMP Pro
So I tried WINE 1.9.19 anyway, and there it worked! So I will use that version until WineBottler is updated.
Sorry for bothering you Roman and, once again, big thank you for your help and of course CMP Pro
9
clrmame Discussion / Re: Scanning does not start
« on: 05 October 2016, 19:30 »
And here are my results:
- Scan MFC button: stops at 25'782 files, no output in text box
- Scan button: stops at 25'781 files, no output in text box
- Scan MFC button: stops at 25'782 files, no output in text box
- Scan button: stops at 25'781 files, no output in text box
10
clrmame Discussion / Re: Scanning does not start
« on: 04 October 2016, 22:19 »
Yep, selecting for example my Art folder containing 1389 files, all are displayed correctly in the text box and additionnally I can quit the program by clicking on the close box.
In the previous case, I had to quit them from Wine's Task Manager.
In the previous case, I had to quit them from Wine's Task Manager.
11
clrmame Discussion / Re: Scanning does not start
« on: 04 October 2016, 21:37 »
Output from DirWalk_default.exe:
Found Files: 25'958 (there are in fact 33'552 fils in the folder) and nothing appears in the text box below
Output from DirWalk_Opti.exe:
Found Files: 25'716 (and nothing in the text box below, either)
Output from DirWalk_XP.exe:
Found Files: 25'923 (still nothing appears in the text box)
Running DirWalk_default.exe a second time, now there were 25'943 files found.
Subsequent running of the 3 programs always yielded in slightly different results.
Found Files: 25'958 (there are in fact 33'552 fils in the folder) and nothing appears in the text box below
Output from DirWalk_Opti.exe:
Found Files: 25'716 (and nothing in the text box below, either)
Output from DirWalk_XP.exe:
Found Files: 25'923 (still nothing appears in the text box)
Running DirWalk_default.exe a second time, now there were 25'943 files found.
Subsequent running of the 3 programs always yielded in slightly different results.
12
clrmame Discussion / Re: Scanning does not start
« on: 30 September 2016, 14:15 »
Here are some additional observations:
- all my files and CMP are on local disks (in fact on the internal disk drive), no special permissions or anything applied
- I'm currently running CMP under full virtualisation (VMware): no problem here, it is at the stage of checking the ROMs (although it is extremely slow, after 10 minutes still at the letter 'a', hence why I prefer to use Wine, which is much faster)
I think we can conclude with some confidence that a change in macOS 10.12 triggered something in Wine.
- all my files and CMP are on local disks (in fact on the internal disk drive), no special permissions or anything applied
- I'm currently running CMP under full virtualisation (VMware): no problem here, it is at the stage of checking the ROMs (although it is extremely slow, after 10 minutes still at the letter 'a', hence why I prefer to use Wine, which is much faster)
I think we can conclude with some confidence that a change in macOS 10.12 triggered something in Wine.
13
clrmame Discussion / Re: Scanning does not start
« on: 29 September 2016, 20:14 »
FWIW, I just tried CrossOver (commercial version of WINE), that's much more recent as the current release of WINE (dates from September 20th), and it exhibits the same behaviour. 
14
clrmame Discussion / Re: Scanning does not start
« on: 29 September 2016, 18:27 »
I think there is progress: CMP still stops at sc4milja, but now I see all the file names in "Testing Unneeded" being tested (before there was no output at all) and there are additional lines at the end of the log file.
15
clrmame Discussion / Re: Scanning does not start
« on: 29 September 2016, 18:04 »
Oh, and I just checked, sc4milja is the 25'963th file in my ROMs folder. Along with 671 files in the CHD folder and 8 files in the LD folder, this makes it the 26'642th file examined (this is without counting the subfolders inside the CHD and LD folder). So nothing obvious there.
16
clrmame Discussion / Re: Scanning does not start
« on: 29 September 2016, 17:53 »
New result: my LD (laser disks) and CHDs folder are now scanned, but hang occurs at same file.
17
clrmame Discussion / Re: Scanning does not start
« on: 29 September 2016, 15:20 »
Too big to quote inline now, so here's the complete log file:
19
clrmame Discussion / Re: Scanning does not start
« on: 28 September 2016, 20:45 »
Sorry, I've never used the Rebuilder, so I don't really know how to use it.
20
clrmame Discussion / Re: Scanning does not start
« on: 28 September 2016, 20:30 »
I restored MAME 0.177 from backup and tried with that one: still no luck.
Besides updating to MAME 0.178, both MAMEBase and I (if I can believe the sidebar below a user's name) have updated macOS from 10.11 (El Capitan) to 10.12 (Sierra).
So that could contribute also to the problem we are experiencing.
Besides updating to MAME 0.178, both MAMEBase and I (if I can believe the sidebar below a user's name) have updated macOS from 10.11 (El Capitan) to 10.12 (Sierra).
So that could contribute also to the problem we are experiencing.