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: Problem Scanning an SMB Volume

« on: 22 March 2025, 15:41 »

I tried once again but this time with a "real" server (my Synology NAS). It worked right away without any problems.

So it seems it's the built-in SMB server functionality of macOS that is not quite up to par.

2

clrmame Discussion / Re: Problem Scanning an SMB Volume

« on: 20 March 2025, 14:54 »

Sadly, doesn't work either.

After a restart, I can't even reconnect in Explorer to the SMB share. Unless there's an SMB specialist around here, I don't think we will get this to work.

3

clrmame Discussion / Re: Problem Scanning an SMB Volume

« on: 16 March 2025, 17:45 »

I have some programming knowledge but never used C++. If you could send me the binary (bear in mind that I'm using Windows for ARM, but the x86 translation layer is installed) I'd happily try it.

4

clrmame Discussion / Re: Problem Scanning an SMB Volume

« on: 16 March 2025, 13:31 »

If I run ClrMAME as administrator it’s even worse, output consists only of these 2 lines:

Code: [Select]

error can't parse Z:\MAME\PC\mame.exe
error errors occurred, please check log

The user I created for sharing the external disk was another one as either the macOS user and Windows user (all 3 different). I then used the same user name and password for sharing the folder in macOS as the Windows user but that didn’t help either.

5

clrmame Discussion / Re: Problem Scanning an SMB Volume

« on: 15 March 2025, 20:37 »

Note: I tried to post with an image of the settings used in Rebuilder but the forum software flagged the post as spam.

6

clrmame Discussion / Re: Problem Scanning an SMB Volume

« on: 15 March 2025, 20:36 »

I don't think it's a permission problem as I can see the files in Windows so ClrMAME should also be able to access them, should'nt it?

This results in the following error:

Code: [Select]

info using already existing xml export
info loading: C:\Users\Charel\Desktop\clrmame\exports\bc03e79e-listxml.xml
info building split view, rebuilder map and destination patterns
info 47966 split merged machines selected
info rebuild start
info analyzing rebuilder source: Y:\MAME\ROMs, please be patient
error analyzing rebuilder source Y:\MAME\ROMs failed due to recursive_directory_iterator::recursive_directory_iterator: Invalid Signature.: "Y:\MAME\ROMs"
info thread pool size: 10
info analyzing rebuilder destination: Y:\MAME\Fix, please be patient
info optimizing
info finalizing and cleaning up
info rebuild end, took 0 seconds
info Done, overall time: 12 seconds
error errors occurred, please check log

Could the fact that the MAME executable is a level lower than the ROMs folder (as you can see in the config) be the source of the problem?

7

clrmame Discussion / Problem Scanning an SMB Volume

« on: 14 March 2025, 07:43 »

This may be very well a problem with my setup and not ClrMAME itself, but maybe one of you had a similar problem and knows a workaround.

For years I've been using VMware Fusion on macOS (for Intel based machines) with a feature called "shared folder" to make an external drive accessible for scanning. Having exchanged my old Mac mini for a newer model using Apple Silicon, I noticed that the current version of Fusion does not support that feature.

A way to get around is to use macOS's built-in SMB file server and access the files using Windows built-in SMB client. I'm now able to access all the files on the disk from Windows and ClrMAME sees the whole folder hierarchy as documented in the screenshot below:



But running a scan results in the following error:

Code: [Select]

error analyzing . failed due to directory_iterator::directory_iterator: Invalid Signature.: "."
Does somebody have an idea what's going wrong here?

8

clrmame Discussion / Re: Duplicates that don't even exist

« on: 31 January 2025, 22:02 »

The situation was rather confusing and as my set is correct now I don't know how to recreate it. Here is what I recall:

• there were ROMs missing for the quizard driver, which also has an associated CHD
• the missing ROMs were in the fix folder and copied from there to the CHD folder instead of the more logical ROMs folder
• although the ROMs were now shown as being duplicates of others, they really weren't and the fact that the log file showed them as being both in the ROMs folder did not help finding the solution
• as soon as I moved them from the CHDs folder to the ROMs folder, the duplicate warnings went away
  

Sorry for not being more helpful 

9

clrmame Discussion / Re: Duplicates that don't even exist

« on: 31 January 2025, 16:11 »

Yep, I can confirm that it is a problem with the path names displayed. The "duplicate" files were in the CHD folder. As soon as I put them into the ROMs folder the duplicate message went away.

10

clrmame Discussion / Re: Duplicates that don't even exist

« on: 31 January 2025, 14:29 »

Sure Roman, here they are.

11

clrmame Discussion / Duplicates that don't even exist

« on: 31 January 2025, 13:50 »

I used the new 0.2 release to check my MAME 0.274 ROM set. Initially, I got the following error:

Code: [Select]

Quizard (v1.2, Italian, i8751 IT 11 I2) [quizardi_12] [cloneof: quizard]
multiple machine: quizardi_12 [dupes: \\Mac\MAME\ROMs\quizardi_12.zip;\\Mac\MAME\ROMs\quizardi_12.zip]

Quizard (v1.7, Italian, i8751 IT 11 I2) [quizardi_17] [cloneof: quizard]
multiple machine: quizardi_17 [dupes: \\Mac\MAME\ROMs\quizardi_17.zip;\\Mac\MAME\ROMs\quizardi_17.zip]
I noticed that the file names of the 2 supposedly duplicates were identical, but there was just one of each file. Even after deleting those files, they are still shown after another scan as duplicates.

12

clrmame Discussion / Re: Convert ClrMAME unneeded masks to new scanner format

« on: 31 August 2024, 20:51 »

In pre-macOS times, Macintosh files could have a resource fork (it was an inherent part of a file). To ensure compatibility with systems that don't support that, ZIP files contain those _MACOSX folders that contain a "normal" file copy of the resource fork.
I don't know of any app who still uses them but apparently Apple's compression engine still includes them in an archive.

I tried the new exclude mask string, icon files are still flagged. Could we achieve a better result with scanner simply ignoring invisible files (which all of these special files are)?

13

clrmame Discussion / Re: Convert ClrMAME unneeded masks to new scanner format

« on: 31 August 2024, 07:58 »

Here is an example:

14

clrmame Discussion / Re: Convert ClrMAME unneeded masks to new scanner format

« on: 30 August 2024, 21:07 »

The above mentioned string still does not catch folder icon files. Maybe Apple changed the name but I can only see "Icon" in terminal. the '*' of ClrMAME seems to catch all the cases (0 or more characters).

Also, of 6 icon files only 4 are reported as unneeded:

2024-08-30 14:44:04   error   can't determine file size of \\vmware-host\Shared Folders\MAME\CHDs\Icon
2024-08-30 14:44:04   error   can't determine file size of \\vmware-host\Shared Folders\MAME\LDs\Icon
2024-08-30 14:44:04   error   can't determine file size of \\vmware-host\Shared Folders\MAME\ROMs\Icon
2024-08-30 14:44:04   error   can't calculate crc32 of \\vmware-host\Shared Folders\MAME\CHDs\Icon
2024-08-30 14:44:04   error   can't calculate crc32 of \\vmware-host\Shared Folders\MAME\LDs\Icon
2024-08-30 14:44:04   error   can't calculate crc32 of \\vmware-host\Shared Folders\MAME\ROMs\Icon
2024-08-30 14:44:04   info   scan machine
2024-08-30 14:44:05   info   update missing information
2024-08-30 14:44:07   info   scan process end, took 16 seconds
2024-08-30 14:44:07   info   fix process start
2024-08-30 14:44:07   error   can't backup \\vmware-host\Shared Folders\MAME\CHDs\Icon
2024-08-30 14:44:08   error   can't backup \\vmware-host\Shared Folders\MAME\LDs\Icon
2024-08-30 14:44:08   error   can't backup \\vmware-host\Shared Folders\MAME\ROMs\Icon
2024-08-30 14:44:08   error   can't backup \\vmware-host\Shared Folders\MAME\Extras\samples\Icon
2024-08-30 14:44:08   info   fix process end, took 1 second
2024-08-30 14:44:08   info   saving output and fixdat
2024-08-30 14:44:14   info   47098 of 47098 machines in selected filtered mode
2024-08-30 14:44:14   info   41195 complete, 5903 empty machines
2024-08-30 14:44:14   warning   4 unneeded files/folders

15

clrmame Discussion / Re: Convert ClrMAME unneeded masks to new scanner format

« on: 30 August 2024, 13:51 »

Is there any other forum where I can post about scanner? Anything more than a line and spam filter here gets wild.

16

clrmame Discussion / Re: scanner 0.04, rebuilder 0.11

« on: 30 August 2024, 13:29 »

I wanted to post something here with pictures but everytime I use them my post is flagged as spam, so you'll have to take my word for it.

Two ROM sets were mentioned in the tree as missing a ROM file, and indeed they did. But no mention of those appeared in the final log.

Also of interest, the 2 missing files were only reported in v0.0.4 of scanner and not in 0.03, although there has been no change to the ROM set in the meantime.

17

News & Communication / CleanTalk flags my posts as spam

« on: 30 August 2024, 13:25 »

The board software is sometimes extremely frustrating because all I'm getting when trying to post something with a picture in it is a message from CleanTalk stating it is considering my post as spam.

What can I do about that?

18

clrmame Discussion / Convert ClrMAME unneeded masks to new scanner format

« on: 30 August 2024, 12:44 »

Hi,

for years I've been using the following masks with ClrMAME on macOS:



The first line is for custom icon folders. The asterisk is needed because there is an invisible character at the end of the name that I don't know and can't type. The second line is for folders that reside on servers and contains some housekeeping values for that folder (like window position and size etc.).

I've tried a lot of different formats but I can't get it right on scanner. Would somebody please be so nice and show me how it's done?

19

clrmame Discussion / Re: scanner 0.03, rebuilder 0.10, .....and some cmpro update released

« on: 29 August 2024, 19:05 »

https://www.emulab.it/forum/index.php?topic=9797.0

That clears it up, thanks Roman.

20

clrmame Discussion / Re: scanner 0.03, rebuilder 0.10, .....and some cmpro update released

« on: 29 August 2024, 15:31 »

It seems like I've encountered a bug in 0.03:

Code: [Select]

2024-08-29 14:56:47 error can't access: \\vmware-host\Shared Folders\MAME\ROMs\wontame.zip
2024-08-29 14:56:47 error can't access: \\vmware-host\Shared Folders\MAME\ROMs\gekimaka.zip
2024-08-29 14:56:54 error can't access: \\vmware-host\Shared Folders\MAME\ROMs\dokodemo.zip
2024-08-29 14:57:07 error can't backup \\vmware-host\Shared Folders\MAME\ROMs\wontame.zip ic33
2024-08-29 14:57:07 error can't backup \\vmware-host\Shared Folders\MAME\ROMs\wontame.zip ic30
2024-08-29 14:57:08 error can't backup \\vmware-host\Shared Folders\MAME\ROMs\dokodemo.zip ic33
2024-08-29 14:57:08 error can't backup \\vmware-host\Shared Folders\MAME\ROMs\dokodemo.zip ic30

But the backup folder exists and has been used by previous versions of scanner (the folder contains several files).