Open GeyserLaPunk opened 3 years ago
@GeyserLaPunk I'm running into this same issue. Have you attempted to upgrade it yourself?
@GeyserLaPunk I'm running into this same issue. Have you attempted to upgrade it yourself?
I did, but unsuccessful, still hit the limit. The only way I was able to convert is to limit length of the output directory to the bare minimum.
@GeyserLaPunk I was able to get this working by editing a registry key on Windows 10 v1067. I also had to create an application manifest file. I used these instructions:
Hope this helps! I will push changes to my fork in the next few days as well.
Maybe the program should analyze the longest file name and directory name before starting and check if they are supported. So you won't get stuck with an error after many hours.
Needs to be migrated to newer .NET Framework version to support Long File Names.
Throws following error if path or name is too long:
if using runtime settings like this:
then the error become: