GitLab

Don't subscribe to service calls you do nothing with 0x42 and 0x68 removed from service call table and service call handler.

Version 1.04. Tagged as 'DOSFS-1_04'

DOSdirs.c: be more careful about %s of NULL pointers
DOSFS.c: don't waste time strcmp() of PCMCIA format name when you can compare by index

Debug version built, less oflaoflaolfa now.

Version 1.03. Tagged as 'DOSFS-1_03'

Detail:
  Somewhere in the process of adding FAT16/FAT32 support, a bug was
  was introduced where an attempt was made to calculate the number of
  sectors in a cluster before the cluster size (in bytes) had been
  determined. This affected invalid (e.g. blank) image files, as well as
  old 160K/320K DOS floppies that aren't supposed to contain a valid boot
  block.
Admin:
  Issue raised by the Raspberry Pi NOOBS team when they failed to set up
  the DOS partition where FileCore was expecting it to be.

Version 1.02. Tagged as 'DOSFS-1_02'

Missing 'Stack full' error message added (German translation needed).
Use DOSFS FS number from headers.
Tested with floppy disc (FAT12), 1GB image file (FAT16) and 4GB image file (FAT32) with no issues seen.

Version 1.01. Tagged as 'DOSFS-1_01'

RAM build include messages.
Removed atexit() handler, in favour of finalisation-code option in CMHG file.
Changed cluster rounding in saveFILE() to deal with extents > 2G.

Version 1.00. Tagged as 'DOSFS-1_00'

OpsGetPut
  DOSFS_put_bytes no longer passes an unnecessary dummy argument.
  Reindented.
  Doxygen comments added to FileSwitch layer.
OpsFind
  Suggested buffer to FileSwitch is now 1x512 sector (rather than 256).
  Note - nothing seems to use the cluster buffering code in DOSFS,
indeed nothing ever malloc()s a buffer.
  Check at line 237 of OpFind would never be true since FILE_subdir is
not 1, fixed.
  Return an error if the handle to close is invalid.
  Reindented.
  Doxygen comments added to FileSwitch layer.
OpsFile
  Reindented.
  Doxygen comments added to FileSwitch layer.
OpsFunc
  A failure to find a slot to set the disc title now reports "Dir full"
not "Disc full"
  Reindented.
  Doxygen comments added to FileSwitch layer.

Version 0.99. Tagged as 'DOSFS-0_99'

Many magic numbers changed to exported defines.
Eliminated unused "BOOTblock.h" (was just nesting 1 include file).
Moved non ASCII definitions out of "ASCII.h" then found the remainder weren't used => eliminated.

Version 0.98. Tagged as 'DOSFS-0_98'

Replaced 'lk' register name with 'lr', now APCS is not set to -none.
Inverted the sense of the conditional in CMHG file, following the more common ROM predefine use (eg. the Toolbox).
Removed obsolete NoFAT32 obey files - the switch remains but there's little point omitting that now (since the switch actually leaves most of the code in anyway).
Tested in IOMD ROM build (export, resources, ROM phases) mounting a DOS floppy and 1GB image file.

Version 0.97. Tagged as 'DOSFS-0_97'

The sources to DOSFS had become rather jumbled and monolithic
* Split FileSwitch interface out into seperate ops source files.
* Combined international error lookup with MsgTrans code.
* Split utility functions into 'Helpers.c' along with wildcard matching functions.
* Moved DOS naming functions into, erm, 'DOSnaming.c'.
Also
* Makefile tweaked to remove 'symbols' on clean.
* Obsolete 'Help' and 'Syntax' placed in attic.

RAM, debug, and ROM targets built. RAM target tested with a DOS floppy disc.

Version 0.96. Tagged as 'DOSFS-0_96'

Detail:
  In the code which determined the bitmask to apply to cluster numbers, the
  calculation of the number of clusters in the data area (which is the
  deciding factor between FAT12, FAT16 and FAT32) contained an operator
  precedence error in the calculation of the root directory size. The result
  was that if the disc size was within approx 8 MB of the FAT type threshold
  then the wrong mask was selected. (For clusters of 4*512 bytes, the FAT12/16
  threshold is about 8 MB, so discs between 8 and 16 MB would fail.)
  Also:
  * Fixed the module base address and offsets registered with FileSwitch -
    previously the static data relocation offset was incorrectly applied.
    FileSwitch didn't actually care as long as they added up to the right
    address, but it was still wrong.
  * 32-bitting was incorrectly done using the No26bitCode switch rather than
    the No32bitCode switch, meaning that softloadable builds of this module
    were not 32-bit compatible. Softloadable builds now work on anything from
    RISC OS 3.5 onwards.
Admin:
  Tested on Raspberry Pi and Iyonix.

Version 0.95. Tagged as 'DOSFS-0_95'

Admin:
  Changes received from Willi Theiss

Version 0.94. Tagged as 'DOSFS-0_94'

Admin:
  Changes received from Willi Theiss

Version 0.93. Tagged as 'DOSFS-0_93'

Detail:
  c/DOSFSops - The while() loop in findSUBDIR now bails immediately if getnextDIRentry() returns NULL. Avoids null pointer dereference when calling buildFILEname().
Admin:
  Tested on Raspberry Pi with high processor vectors


Version 0.92. Tagged as 'DOSFS-0_92'

Detail:
  c/DOSFSops - packdir() was treating its optional 'preserve' parameter as mandatory, leading to peeking (and potentially poking) of null pointers
Admin:
  Tested on Raspberry Pi with high processor vectors


Version 0.91. Tagged as 'DOSFS-0_91'

Detail:
  Renamed function "localTIME" to "get_RISCOS_TIME" since it has nothing to do
  with local time. This function used to call the C library function
  localtime(), but until recently the C library was non-conformant to the
  C standard, and simply produced a year/month/day/hour/minute/second breakdown
  as UTC. When this was fixed (RISC_OSLib 5.68) it changed DOSFS's behaviour;
  it was first detected because the reverse operation is implemented locally
  within DOSFS, so a read-modify-write of file attributes leads to the
  modification time being skewed by an amount equal to the difference between
  UTC and local time. Arguments can be made either to treat the on-disc time as
  local time (for compatibility with Windows and Mac OS) or as UTC (for
  compatibility with Linux or older RISC OS systems); I have opted to return
  behaviour to UTC. Also placed a lower limit on dates of the earliest date
  supported by FAT (1980), so for example if your system clock is set to 1970,
  as it will be if there is no RTC and NetTime is not operational, then you
  don't end up creating dates in the far future due to underflow.
Admin:
  Tested on a beagleboard

Version 0.90. Tagged as 'DOSFS-0_90'

Use Push/Pull macros for stack operations.
Unix-ify path names in assembler files.

Version 0.89. Tagged as 'DOSFS-0_89'

Detail:
  DOS-formatted discs don't have a FileCore boot block, so there's nowhere
  to store the *OPT 4 setting. Up till now, it's been hard-coded to 0; this
  commit changes it to a hard-coded 2, which means that (at least in theory)
  it is now possible to construct a bootable DOS-formatted medium - like, say,
  the same SD card that contains a beagleboard ROM image.
Admin:
  Verified the reported boot option using *Cat.

Version 0.88. Tagged as 'DOSFS-0_88'

Previous changes were untagged, but incrementing the version number gives
us a tag we can associate with the official RISC OS 5.16 release.

Version 0.87. Tagged as 'DOSFS-0_87'

Detail:
  Uses suffixed file extensions for compatiblity with both Norcroft and GCC.
Admin:
  Supplied by Peter Naulls, tested at ROOL

Version 0.86. Not tagged

Detail:
  Unaligned word loads and stores have been optimised if only pre-ARMv6 or
  if only ARM6+ arachitectures need be supported.
Admin:
  Builds but untested

Version 0.86. Tagged as 'DOSFS-0_86'

Version 0.85. Tagged as 'DOSFS-0_85'

now ensures that any long name that doesn't match the linked shortname is markee erased. This then copes with images where a longnamed file is deleted on shortname filing system, thus leaving several longname name entries 'hanging around'

Detail:

Admin:
         tested at castle.. castle added IP


Version 0.84. Tagged as 'DOSFS-0_84'

Detail:
       the DOSMap command had a couple of *8 multipliers which
       thus wrongly indexed dos extent info in printout.
Admin:
       long file name dosfs beta tested in the field .. appears fit
       for purpose.. Also tested at castle
       castle added IP


Version 0.83. Tagged as 'DOSFS-0_83'

Detail:
    bug fix reported from beta release of 0.81.
Admin:
    castle testes.. castle IP


Version 0.82. Tagged as 'DOSFS-0_82'

Detail:
   1: loading dir could occasionally blank the first dir entry.. lfn ptr
      blanking went too far
   2: long names and short names could get out of sync if the short
      name was changed on a non long name dosfs
Admin:
   castle tested
   castle added ip


Version 0.81. Tagged as 'DOSFS-0_81'

Detail:
   ensure long file name pointer nulling stopped in time
Admin:
   Tested at castle
   Castel IP


Version 0.80. Tagged as 'DOSFS-0_80'

Detail:
   Extend DOSFS to correctly recognise FAT32 DOS images and to
   use the Long File Name extensions. NOTE that there is still
   a 2gb size limit imposed by the max filecore image file
   size limitiations. NOTE also that as yet there is no support for
   UTF encoding of file names.
Admin:
   Tested at castle and with beta testers.
   Modifications are castle and castle assigned IP (from CJB)


Version 0.79. Tagged as 'DOSFS-0_79'

When a disc has no title but does have the extended boot sig and the volumeid is non zero then the disc title will be set to %04X-%04X of the volumeid instead of "Untitled" which should cut down on ambiguous disc names a bit.

Version 0.78. Tagged as 'DOSFS-0_78'

Now,for fixed discs,we read uncached as much as possible into as big a
lump of RMA as possible.
Reduced mounting a 128M flash keyring from 21s to 1.5s!

Version 0.77. Tagged as 'DOSFS-0_77'

For non floppies passed to Service_IdentifyDisc the disc record is updated to the correct number of sectors per track.This was causing exceptionally slow backups from the filer as it dribbled one sector at a time.

Version 0.76. Tagged as 'DOSFS-0_76'

Fix to cycle ID calculation inside Service_IdentifyDisc,this was causing lots of "Ambiguous disc name"s

Version 0.75. Tagged as 'DOSFS-0_75'

Rewrote Service_IdentifyDisc partly because it was an unreadable mess but mainly so it can handle fixed discs too - this will be useful for DOS format USB mass storage.

Also it will have a go at interpreting the partition table on fixed discs.
Tweak to filetyping logic (again!).

Version 0.74. Tagged as 'DOSFS-0_74'

Assumption that TRUE was -1 in the filetype lookup removed,this was causing filetype 0 to be overriden to FE4.

Module date string now got from VersionNum file so I don't have to keep
remembering to stamp the CMHG file.

Version 0.73. Tagged as 'DOSFS-0_73'

Looks like Win2k is zeroing the reserved fields where the RISC OS filetype is stored leading to directory viewers full of type &000 files.

To combat this the ROS filetype is only used when the creation date is
zero (as DOSFS always clears this when writing a file).
Also,when a settype is performed DOSFS will zero it (this isn't a problem
for DOSFS 0.6x because you could never have a filetype of zero anyway!)

Version 0.72. Tagged as 'DOSFS-0_72'

Made sure on return from global_error the V bit gets set,fixes bug in finding the free space on a floppy (since freespace64 is tried first but which led to the pointer to the error message being returned as the freespace rather than the caller trying again another way).

Correction to missing \ in the makefile,meant you could only compile
it once having checked it out.
Fixed a pointer in the DiscOp64 support added,this caused DOSFS to go
pop when you asked it to vet a format.

Version 0.71. Tagged as 'DOSFS-0_71'

Unused MSDOStoSTRING #if'd out to save a massive 112 bytes!
Corrected tracef1 in map_file_rostype which was printing out the
debugging before the variable got assigned.
Conditionally uses FileCore_DiscOp64 now,if available when the module
starts.
Eliminated some local 64 bit time handling code in favour of using that
already in the compiler (thanks to Kevin).
Now requires a compile time switch PCMCIA=<TRUE | FALSE> which leaves in
or takes out the PCMCIA card support.

Version 0.70. Tagged as 'DOSFS-0_70'

Eliminated MOVS and R14 fiddling to achieve 32 bit compatibility
RISCOS Ltd made 3 changes in their sources
 - ensure disc titles don't contain rogue characters (added)
 - files with time,date,and reserved fields of zero appears as DEADDEAD
   which is silly since Winodws uses this to mark a file unstamped which
   isn't quite the same thing! (not added)
 - syslog debugging support (not added)

Version 0.69. Tagged as 'DOSFS-0_69'

Dates on machines not running Win95FS no longer stuck at 1900 (got
broken in 0.67 by a missing && somewhere).

Version 0.68. Tagged as 'DOSFS-0_68'

Unstamped files (marked by DOS with a time and date of 0x0000) will now return 01-Jan-1900 rather than very late at night on 31-Dec-1979.

Can now set the RISC OS type to 0x000 (previously this would then have been
stamped as 0xFE4 since 0x000 was used as a magic 'no filetype found' marker.
Will now try to use MimeMap if no 'dosmap'ping was found,in this way dosmap
overrides MimeMap for DOSFS - if neither offer a match,0xFE4 is used.
Updated messages to reflect this.
Discs formatted under DOSFS will now set the OEM vendor id to "DOSFS   ".

Version 0.67. Tagged as 'DOSFS-0_67'

Formatting now pads disc titles with spaces rather than NULs.

Version 0.66. Tagged as 'DOSFS-0_66'