Print

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

[cabel]

Hello! I've recently set up my Windows 11 PC to access my MAME roms viaa local server using a Mapped Network Drive.

The network drive is mapped to Z:\\ - so I set my Rom Path to Z:\\Emulation\Arcade\MAME\roms\

With both old ClrMamePro and new Clrmame (0.08.1), despite all ROM .zip files being in place, it quickly reports that they are all missing.

The new clrmame logged the following error:

Code: [Select]

2024-12-27 22:31:21 error accessing Z:\Emulation\Arcade\MAME\roms failed due to recursive_directory_iterator::recursive_directory_iterator: Invalid Signature.: "Z:\Emulation\Arcade\MAME\roms"
2024-12-27 22:31:25 error analyzing . failed due to directory_iterator::directory_iterator: Invalid Signature.: "."
2024-12-27 22:31:33 warning 41437 missing, 62 partly wrong machines
2024-12-27 22:31:43 error errors occurred, please check log
Anything I did wrong, or need to change?

-C

[Roman]

Hmmmm….maybe double check access rights of the files in the folders?

[Roman]

Searching the internet gets you:

Possible Causes:
The "Invalid Signature" error could occur when the system or the library encounters an unexpected or malformed response from the network drive during directory iteration.
You may not have the appropriate permissions to access certain directories or files on the network drive, especially if network authentication or certain security settings are involved.
Even if the network drive is mapped correctly, certain directories might require elevated privileges or additional handling that your program doesn't support.
Mapped network drives can sometimes be unreliable, especially if the connection is slow or unstable. std::recursive_directory_iterator may attempt to access files or directories that are temporarily unavailable due to network latency or disconnects.

Solutions
Check Network Drive Availability:
Before using std::recursive_directory_iterator, ensure that the network drive is fully accessible and stable. You can check if the network share is mounted and if you can access the drive manually (e.g., through a file explorer).
Verify Permissions:
Ensure that your program has sufficient permissions to access the directories and files on the network drive. You may need to run your program with elevated privileges or adjust security settings on the network share.
Timeouts and Network Configuration:
Ensure that your network connection is stable and that your program is not timing out or facing issues with slow network drives. Depending on your network settings, it might be useful to implement retries or set timeouts in case the network drive is temporarily unreachable.

[cabel]

As you can see in the above screenshot:

• My network is working fine
• The network share is working fine
• All of the ROMs are listing just fine in File Explorer
• If I get "Properties" on a .zip, it looks fine

So it's definitely not a basic connectivity or networking problem (sorry, internet search.)

Another strange wrinkle: in cmpro64, the "ROMs" scan works fine, but the "Sets" scan fails -- presumably with the same error.

Well, this is a weird one, then!!

Since it sounds like it's not something you've seen before, I'll keep digging around! Thanks for your time.

-C

[Roman]

Sounds weird. I've just setup a mapped network drive to a server far far away with a lousy connection and VPN involved and it works fine.
Maybe ensure that the drive/files are accessible by opening them in an explorer window right before a scan.

Do you have more information about the network? Is SAMBA involved (since it always caused timing problems in the last decades.....guess you can even search the forum for that....), drivers up to date, etc etc...
Try to setup 1 folder with just one set and test that one....maybe something is in your folder which causes the problem and the exception avoids continuing with the other files.....