Closed Artik-joachim closed 1 year ago
Quite deep relative path. WinUAE in relative paths mode always converts all paths that are directories under WinUAE exe path to relative. Perhaps this is too deep relative path but mounting still succeeds. (E=0 would become E=1 meaning empty/non-existing)
Does all files return same error or only some files? Perhaps whole path (original absolute path + .....\ and so on) gets combined and becomes too long internally?
Does filesystem_mangle_reserved_names=false UAE config file entry help? What if you disable Windows 260 character PATH limit? (https://docs.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation) WinUAE internally supports at least 1000 character paths.
From inside WinUAE, all files in /Prefs/Env-Archive/Sys are invisible or any file in 2 or 3 folder deep.
The filesystem_mangle_reserved_names=false
dit not change anything
Disabling the file limit did the trick.
And by the way, thank you @tonioni and all the team for the oustanding work that you guys are doing !
I am running Winuae 4.9.0 64 bit from the following windows folder:
C:\Users\USER\AppData\Roaming\Code\User\globalStorage\prb28.amiga-assembly\downloads\vscode-amiga-assembly-binaries-@-1.4.0\vscode-amiga-assembly-binaries-windows_x64
DH0 is located here:
C:\dev\Amiga-asm\uae\A1200dh0
I get the floowing error in winuaelog.txt:
In WINUAE, I get weird issues, for example, I cannot access the inputs.prefs.
When WinUAE is located in
C:\dev
, there is no issue.is there an issue with the size of the path for accessing DH0 ? thx