• Stewart Brodie's avatar
    Another intermediate checkin now that *FileInfo works. I believe this means... · 28a6a425
    Stewart Brodie authored
    Another intermediate checkin now that *FileInfo works.  I believe this means that nearly all the core functionality is in place for long filename support.
    
    Detail:
      According to Microsoft's documentation, several of the file lookup type
        transactions return the file information in a common format buffer.
        However, what the docs fail to mention, is that in *some* of those
        commands, the time & date fields are reversed.  FindFirst2/FindNext2
        return "date, time, ...".  QPathInformation returns "time, date, ..."
        Grrr.
      There remains a problem with occasional "server error" results from
        some requests.  The reason for these is unknown ... the documentation is
        unhelpful, describing this as "non-specific error code".  Simply repeating
        the command often results in success, sometimes it has to be repeated a
        few times.
      Also fixed filename mapping which caused any 'x' characters at the remote
        server end to be mapped to 'c' at the RISC OS end(!)  This didn't affect
        it before because servers wouldn't return the old module any filenames
        which contained lower case letters (LanManFS used to make the characters
        lower-case itself if the appropriate name style mode was set).
    Admin:
      Tested - still seems to work.  Filename completion from LineEditor works
        nicely.  I can open and close files, and read data from them (*Dump
        used to test this).  *Cat, *Ex and *FileInfo all work.  *Dir works.
      Filename character translations to and from RISC OS format need to be
        verified.  The translation table DOS->RISC OS has been ripped out of
        the NFS module so should be pretty accurate.  The reverse mapping has
        not.
    
    Version 1.87, 1.1.1.1.2.3. Tagged as 'LanManFS-1_87-1_1_1_1_2_3'
    28a6a425
SMB 68.9 KB