GitLab

Detail:
  NB_Startup was failing to stop the LLC timers if the function
    was going to fail after hooking onto TickerV.  This meant that
    if LanManFS never found an appropriate driver for NetBIOS use,
    then killing the module resulted in repeated aborts when the
    TickerV handler has invoked.
Admin:
  Untested.
  Fixes Bugzilla bug #26

Version 2.13. Tagged as 'LanManFS-2_13'

Detail:
  SVC stack overflow occurred due to the recursive method used to
    discard the idle-out prevention responses.  This no longer
    happens.
  Fixed a bit of debugging which caused data aborts!
  Optimised a select() call to pass s + 1 as the first parameter to
    save Internet time in processing the fd_set.
Admin:
  Tested on desktop build, with the idle timers set to send idle outs
    every second (so we don't have to wait 100 hours for the problem
    to occur).  No longer get problems with the machine stiffing.


Version 2.12. Tagged as 'LanManFS-2_12'

  Now doesn't require that the !ArmBoot object is a directory
Detail:
  The code in Omni.c was carefully checking that !ARMBOOT existed
    before attempting to run the boot file.  Unfortunately, it was
    using a method which bypassed the filename resolution (that does
    the ,xxx filetype name mapping), so it did not find the new Obey
    file in the 400 series baseline.  The check has been removed.
  The code in SMB.c was being caught out on an uninitialised variable
    usage when the attribute cache already held details of the object
    being sought.  The variable would have been initialised on a non-
    cached lookup, but the special case of booting a machine via LanManFS
    manages to get a cached lookup without having run through the routine
    before, resulting in a strcpy() with a destination of 0.
Admin:
  Tested on Risc PC.
  Fixes fault 1511 (STB-400 Generic)

Version 2.11. Tagged as 'LanManFS-2_11'

Detail:
  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 fil...

  Removed obsolete header files.
  Removed obsolete assembler.
  Fixed flag preservation in remaining assembler.
Detail:
  See above.
Admin:
  Built RAM build.

Version 2.09. Tagged as 'LanManFS-2_09'

Detail:
  Added Install phase to Makefile.
  Added !MkInstall.
Admin:
  Tested on FastNC Ethernet card build.

Version 2.08. Tagged as 'LanManFS-2_08'

  Fixed search handle haemorrhaging.
Detail:
  The directory lookup routines cached directory search handles to avoid
    hammering the server with repeated requests to open directories.
    Unfortunately, it was possible for these to be forgotten without
    being freed up leading to resource loss at the server end.  Eventually,
    the server gives up servicing you and reports errors.  This will only
    occur once a significant number of accesses have been performed (the
    number depends entirely on server configuration).  This leak is now
    fixed.
Admin:
  Tested against Cerium - debug reports that no handles are being leaked.

Version 2.07. Tagged as 'LanManFS-2_07'

  Name mapping table modified to prefer mapping hard space to space.
Detail:
  Fixes hard space->space mismapping.
  Doesn't leak sockets during startup if driver isn't ready.
Admin:
  Check-in of previously uncommitted bug fixes to get final version number


Version 2.06. Tagged as 'LanManFS-2_06'

Detail:
  The module used to have specific knowledge of the driver to which it
    was supposed to bind if it was unable to find any active drivers at
    the time that LanManFS was initialised.  This meant that if the
    LanManFS module was placed in ROM (eg. in STB3) and the drivers
    hadn't initialised by the time that LanManFS was initialised, it
    would sit and wait for EtherH to arrive - which doesn't happen
    for ATM solutions, and doesn't happen for Ethernet in STB3 because
    we no longer use EtherH!
Admin:
  Tested in STB22 expansion cards, and in STB3 ROM builds for both
    Ethernet and ATM solutions.

Version 2.05. Tagged as 'LanManFS-2_05'

  Introduced new error message for re-entrancy prevention trap to use.
Detail:
  When 'pinging' an SMB server, LanManFS does not wait for any response
    but the response reading routine knows to just throw away any old
    SMBchkpth responses that it gets and try reading again.
  Re-entrancy trap now has its own error "LanManFS in use" &1663E, which
    means you no longer see "!Armboot files nested too deeply" which is
    confusing.  The only way you can provoke this message is if you use
    Alt-Break whilst the NetBIOS/IP code is executing.  The error plays
    the same part as "FileCore in use" does for FileCore.
Admin:
  Verified module still works and the anti idle-out features still work.

Version 2.04. Tagged as 'LanManFS-2_04'

  Fix for ./.. files in short filename shares.
  Long multiply now provided in assembler.
Detail:
  *LMLS is a new filesystem-specific command which performs the same
    task as "smbclient -L" does under UNIX - ie. listing all the shares
    available on the specified host.
  When enumerating the shares on a remote server, LanManFS now remembers
    all the printers, IPC, device and disc shares (for *LMLS to output).
  The 32x32->64 multiply routine is now provided in assembler instead of
    the previous huge amount of obscure C taken from NSPRLib.  This is
    more understandable (and almost certainly far smaller and quicker
    and doesn't need a hack to stop the compiler mis-optimising it!)
  Old short filename shares still had problems with the . and .. file
    filtering.  Programmer fault there - should've let the compiler do
    the optimisations :-)
  Server info string fixed to byte-reverse the port numbers when printing
    the string into the info buffer.  Now claims to be talking to port 139
    as it should.
Admin:
  Tested in general desktop use for several days, plus experimental versions
    tested in other boot ROMs.

Version 2.03. Tagged as 'LanManFS-2_03'

Detail:
  Long filename flag tarnsferred to be a server property rather than
    a share property, otherwise subsequent shares to the same server
    do not get long filenames (because the subsequent shares don't
    have to go through the connection negotiation phase)
Admin:
  Tested on by mounting lots of drives through desktop Omni frontend.

Version 2.02. Tagged as 'LanManFS-2_02'

Detail:
  Any filename starting with . was being hidden.
Admin:
  Tested.  Confirmed . and .. are not there but files such as .rhosts
    are visible.

Version 2.01. Tagged as 'LanManFS-2_01'

  Support for spaces in machine names.
  Merge of sbrodie_LanManFS_dev branch to trunk.
Detail:
  LanManFS 2.00 supports the "NT LM 0.12" protocol, enabling it to
    use long filenames on mounted shares.
Admin:
  Supporting documentation:
    1215,256/FS: LanManFS Software Functional Specification.
  Same as LanManFS-1_87_1_1_1_1_2_13.

Version 2.00. Tagged as 'LanManFS-2_00'

RiscOS/Sources/Networking/LanManFS is now locked out.

The rest of Omni will be imported at a later date.

Version 1.87, tagged as LanManFS-1_87