Folderitems and NAS drives just dont play well together on Windows ?

isReadable and isWritable are highly problematic
But only on Windows ?
I dont seem have these issues on macOS but see them all the time on Windows
Apparently others have as well for quite some time

<https://xojo.com/issue/55731>
<https://xojo.com/issue/22479>
<https://xojo.com/issue/22735>
<https://xojo.com/issue/32355>
<https://xojo.com/issue/14887>
<https://xojo.com/issue/998>

Anyone else having problems with NAS devices on Windows ?
How are you working around them ?

off list someone else pointed to Be careful when interpreting security descriptors across machine boundaries - The Old New Thing

seems that isReadable and isWritable are just plain problematic on Windows regardless of language and just making folderitems return correct error codes would suffice instead of trying to rely on isReadable and isWritable

probably related to <https://xojo.com/issue/56325> as well (although I cant be certain as I dont recall the code in use in the IDE)

Quite the opposite for me. Windows has never been a problem when using the Xojo IDE with projects stored on LAN NAS drives.
Using NAS drives manufactured by Buffalo, Seagate and Toshiba. SMB versions 1.5, 2.1 and 3.1.1.
OTOH I have had problems with editing project files stashed on Dropbox and Google Drive. Would not recommend that practice!!!

My Linux boxes are not a problem either. Except for needing SMB 1.5 to access a couple of older NAS boxes.

macOS however, occasionally gives me problems. Leaves behind an SMB status file that cannot be deleted for a short time. Most often after a file deletion. Not sure why, but it’s so infrequent I don’t worry about it (one a month - maybe). The issue resolves itself after a few minutes anyway. I’ve only seen this issue with the Buffalo NAS drives.

The official Xojo position is that the IDE does not support editing project files stored on remote drives (LAN or Internet).
See (near the bottom of each page):
https://documentation.xojo.com/topics/code_management/using_source_control_with_xojo_projects.html#Online_File_Systems
and
https://documentation.xojo.com/getting_started/using_the_ide/project_types.html#Online_File_Systems

Of course, the paths strings are build using ASCII characters (32-126).

I forgot the details, but I had troubles with a project years ago, that was on an external HD (USB connected on the laptop), and the project name (or the immediate parent folder) had a non ASCII character in it…

At last, I stopped to use external (even directly connected) HD for working project (and started to have storage size troubles: the boot SSD is a 250GB SSD).

[quote=445146:@Robin Lauryssen-Mitchell]
The official Xojo position is that the IDE does not support editing project files stored on remote drives (LAN or Internet).
See (near the bottom of each page):
https://documentation.xojo.com/topics/code_management/using_source_control_with_xojo_projects.html#Online_File_Systems
and
https://documentation.xojo.com/getting_started/using_the_ide/project_types.html#Online_File_Systems[/quote]
Yes I’m aware the docs were changed yesterday and closed a case related to this
https://documentation.xojo.com/index.php?title=UserGuide%3AProject_Types&type=revision&diff=63671&oldid=63669

It doesn’t change any of the bug reports I listed above which still remain problematic with NAS volumes
And, I suspect, that IF the IDE were altered to just write to the volume and not try to use isreadable or iswriteable that the issues about saving projects to various NAS drives would also be resolved.

It seems that the take away is not to rely on them and just try to actually read or write the file and deal with the failures IS the right answer and accept that isReadable and isWriteable on Windows with a NAS are not reliable

[quote=445150:@Emile Schwarz]Of course, the paths strings are build using ASCII characters (32-126).

I forgot the details, but I had troubles with a project years ago, that was on an external HD (USB connected on the laptop), and the project name (or the immediate parent folder) had a non ASCII character in it…

At last, I stopped to use external (even directly connected) HD for working project (and started to have storage size troubles: the boot SSD is a 250GB SSD).[/quote]
I’ve never had such an issue and I have some oddly named projects, volumes & external drives

My question really only concerned a NAS

It seems to be very dependent on how the volume is mounted.

If the NAS is mounted using a fixed volume identifier (M:, Z:, etc.), it seems to work. However, if it is automounted using the “only one engineer deep in the bowels of Redmond knows” mechanism, FolderItem seems to become very confused (and has even lost a previously retrieved reference in a couple of cases).

I haven’t had problems connecting Windows to Windows NAS, or Windows to Linux NAS. Windows to Mac has been problematic. Not sure if this is related, and I tried to connect my Windows PC’s and use airport extreme hard drive to share files. After reading the Mac forums, the Mac Airport Extreme network uses SMB1, which was used by Wannacry rasomware. Windows then went to SMB2, and the way to access the Mac Drive was through SMB1 by downgrading windows from SMB2. There is a security risk, I wouldn’t leave it on SMB1 permanently.