Amiga Old File System: Difference between revisions

Content deleted Content added
No edit summary
Line 1:
:''"OFS" redirects here. For the former Dutch African colony, see [[Orange Free State]].''
On the [[Amiga]], the '''Old File System''' was the filesystem for [[Amiga OS]] before the [[Amiga Fast File System]]. Even though it used 512-byte blocks, it reserved the first small portion of each [[block]] for [[Metadata (computing)|metadata]], leaving a very irregular actual data block real capacity of only 488 bytes per block. It wasn't very suitable for anything except [[floppy disk]]s, and it was soon replaced.
 
== History ==
Originally known as Amiga File System, the filesystem itself was very similar to that of [[Xerox]] Alto Filesystem. Development was from 1982 to 1985 as the filesystem of [[TripOS]]. It received the nickname of "Old" when [[Amiga Fast File System|Fast File System]] was released with [[Amiga OS]] 1.3.
 
OFS is very good for repairing the filesystem in the event of a problem, although the so called DiskDoctor provided by Commodore quickly earned the name DiskDestroyer, because it could not repair No-DOS type autostart disks provided by third -party software- manufacturers as bootable disks for games. Interestingly, the idea to create non-standard autobootable disks was born in a primitive attempt to prevent copy of such disks and to avoid the loading and launch of Amiga DOS, in order to directly access the amiga graphic, audio and memory chipsets. DiskDoctor in fact changed autostart disks bootblocks into standard AmigaDOS -based ones, renaming a disk with "Lazarus" namedisk, and made the autostart disk unusable.
 
Metacomco, BSTRINGS, BPOINTERS, and family contained in the Amiga FS entered the scene when it was decided that the originally planned OS would take too long to be developed in time for the launch of Amiga. Consequently, Metacomco grafted onto the filesystem a lot of things that the old Amiga Inc. has changed, and this resulted in a sort of hodgepodge mess.
 
== Characteristics ==
Amiga uses [[MFM]] encoding/decoding by default when handling [[floppy disk]]s. There are 80 cylinders on an Amiga floppy disk. Each cylinder has 2 MFM tracks, 1one on each side of the disk. Double density (DD) disks have 11 sectors per MFM track, High density (HD) disks have 22 sectors.
 
The geometry of an Amiga Floppy Disk is as follows:
Line 39:
The Rootblock contains information about the disk: its name, its formatting date, etc. It also contains information on accessing the files/directories/links located at the uppermost (root) directory.
 
The characters '/' and ':' are forbidden in file and volume names, but *!@#$%|^+&_()=\-[]{}';",<>.? and accented letters like âè are allowed.
 
The date fields in the root block (and other blocks) are structured in the form of DAYS, MINS and TICKS. The DAYS field contains the number of days since January 1. 1978. MINS is the number of minutes that have passed since midnight and TICKS are expressed in 1/50s of a second. A day value of zero is considered illegal by most programs. TheSince the DAYS value is stored as a 32-bit number, the Amiga filesystem does not have an inherent year[[Year 2000 problem]] or [[Year 2038 problem]].
 
To reach a file, directory or a link in a removable media, Amiga has to compute its hash value with an algorithm often called a [[Hash function]]. After having computingcomputed the hash value, this is then used to access HashTable ('ht' field in Rootblock/Directory block). The HashTable[ HashValue ] contains the number of the first block of the object (File header block, Directory block or Link block).
 
It happens that different names can result in the same HashValue. If more than one name has the same HashValue, the other blocks (for files and directory only) are stored in a chained list. This linked list starts at the 'next_hash' field of the File header or Directory block.
Line 50:
There was a bug in the old AmigaDOS versions when applying the Hash function to international characters (ASCII codes > 128). Consequently, FFS was then created with the 'international mode' (INTL). Filename characters can be lowercase and uppercase, but are not case sensitive.
 
Files are comprisedcomposed of a file header block, which contains information about the file (size, last access time, data block pointers, ETCetc), and the data blocks, which contain the actual data. The file header block contains up to BSIZE/4-56 data block pointers (which amounts to 72 entries with the usual 512 byte blocks). If a file is larger than that, file extension blocks will be allocated to hold the data block pointers. File extension blocks are organised in a linked list, which starts in the File header block ('extension' field).
 
== See also ==