- Jun 26, 2021
- 102
- 81
As far as I know, modern versions of compression utilities have "longPathAware" element set to "true" in the application manifest, so they shouldn't have these problems when used on up-to-date Windows systems.Yeah, at that point all bets are off, it's likely throwing an assert when changing locations (different music).
Try to unzip it to somewhere like c:\tmp or something; windows file extractor sucks balls, and will choke on file paths if they're >230 characters.
You must be registered to see the links
XML:
<application xmlns="urn:schemas-microsoft-com:asm.v3">
<windowsSettings xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
<ws2:longPathAware>true</ws2:longPathAware>
</windowsSettings>
</application>
Last edited: