• Stewart Brodie's avatar
    More tolerance has been added of files found on the remote server which have unexpected extensions. · 36543191
    Stewart Brodie authored
      LanManFS does not like it if you create (independently, using a PC or
        otherwise) files with names like "myfile,fff" which you intend to
        be displayed as files with type &FFF (ie. Text) on a RISC OS machine.
        If you tried to access the file for reading it, such as loading it
        into an editor, that worked due to the name matching resolution.
        However, any attempt to update the file caused LanManFS to attempt
        to write the file without the extension and not notice that a file
        with a ,fff extension already existed (Text files are special cased
        in the current implementation of name translation - see LanManFS
        Functional Specification for details and rationale).  Attempts to
        save typically succeed (giving you two files: myfile and myfile,fff)
        but generate "Operation not permitted" or such like.  This stemmed
        from the attempt being made by LanManFS to rename a file to the same
        name.  SMB_Rename now traps that and tells its caller that the rename
        succeeded.  The Xlate.c code now indicates correctly that the filename
        extension has been altered when a ,fff extension has to be chopped off.
      Tested briefly on desktop build against art-work's SAMBA server.
      Bug reported by TopCat engineers.
    Version 2.10. Tagged as 'LanManFS-2_10'
VersionNum 472 Bytes