RC 4.1.0: very long filenames bug
Issue #217 duplicate
Using RC 4.1.0 The latest GB no-intro DAT contains:
Mani 4 in 1 - Genki Bakuhatsu Gambaruger + Zettai Muteki Raijin-Oh + Zoids Densetsu + Miracle Adventure of Esparks - Ushinawareta Seiseki Perivron (China) (Ja).gb
RC sees it as yellow although the filename is ok..
I tried and get a green flags everywhere.
Can you post a screeshot ?
prog is in:
rom is in:
Tried to put rom as:
D:\new\ but didn"t solve the bug.
On Win 7 32bit.
I have a hunch this is related to 32bit versus 64bit, I also have this issue.
Yes, it’s possible. Please have a look at this web page: https://social.msdn.microsoft.com/Forums/en-US/fc85630e-5684-4df6-ad2f-5a128de3deef/260-character-explorer-path-length-limit?forum=windowsgeneraldevelopmentissues
It proposes two solutions to solve the problem.
Now I’m confused because the path I have the rom stored at:
D:\Unzipped\NoIntro\GB\Mani 4 in 1 - Genki Bakuhatsu Gambaruger + Zettai Muteki Raijin-Oh + Zoids Densetsu + Miracle Adventure of Esparks - Ushinawareta Seiseki Perivron (China) (Ja).gb
is 185 characters, so far less than the problematic 260..
Also the 2 solutions apply only to Win10 and newer, so it can’t be the same issue, I don’t think..
Thanks for your help.
Eric,, did you test with the rom uncompressed ?
The bug seems to only occur when the rom is NOT zipped.. !?
I will try it. Thanks for the details.
I’m having a similar issue when trying to scan a redump sega-saturn folder containing plain cue+bin files.
Some japanese game names are pretty long and when you combine the folder and the name of the cue, it’s easy to bust the limit.
When it occurs, romcenter doesn’t tell you exactly the folder that caused the issue.
My use-case might bit a little bit different though because I’m accessing the files using a UNC (everything is stored on a NAS)
kik, try to compress that folder to .zip,
When compressed, does RC see it green ?
if it’s zipped, yes, it does work fine. Although if the zip file full path is too deep, I get the same path too long error.
Eric, any update regarding this bug ?
I’ve tried the 4.2 RC3, but it looks like the long path support is still not functioning properly.
Any chance to get it fixed in the official 4.2 ?