The different TV incarnations for the various platforms are aimed at resembling
one another as closely as possible. In some areas, however, that is simply not
desirable. It would not be at all useful have, say, users under Unix entering
filenames in the convention created for the Amiga. That is why TV adopts the
file naming convention of the underlying OS - usually.

On the Amiga:
- Files can be entered only in accordance with the filename convention laid down
  by the OS.
  Example: DH0:S/user-startup
- Files are always displayed in the same manner.
- The file-system is not case-sensitive: 'user-startup' will match 'User-startup'.
- Filenames displayed by TV will always match the casing on disk.

Under Unix:
- Files can be entered only in accordance with the filename convention laid down
  by the OS. It is possible to use environment variables; they will be translated.
  Example: $HOME/.profile
- Files are always displayed in the same manner.
- The file-system is case-sensitive: '.profile' will not match '.Profile'.

Under Windows:
- Files can be entered in accordance with the filename convention laid down by the
  OS. Environment variables cannot be used. Future updates may add that.
  Example: C:\Users\user1\Documents
- Files can also be entered in a pseudo-Unix way. As environment variables are
  supported, this can be a work-around for the limitation mentioned above.
  Example: /c/Users/user1/Documents
- The file-system is not case-sensitive: 'documents' will match 'Documents'.
- Filenames displayed by TV will always match the casing on disk.
- A setting controls whether TV displays filenames in accordance with the OS, or
  in the pseudo-Unix semantics.