Re: VFAT kernel considerations

[Konrad Kokoszkiewicz <draco@mi.com.pl>]

>  >> Well, every file should have a standard 8+3 filename as well as a
>  >> VFAT-entry, so if the FAT is readable by TOS it's also quite possible
>  >> to boot plain TOS.
>  >
>  >That's true, but then if you delete a file that in VFAT has a long
>  >filename, things can get messy. :)
> 
> Exactly.  Write a file using VFAT, delete it under SingleTOS.
> You end up with a longname reference to a file that is gone.

Errr.... what else would you expect? At least VFAT is an extension and
the TOS doesn't know this extension. So it would be rather silly to expect
that the TOS can do *anything* with VFAT entries properly.

In other words: as long as you don't have VFAT entries on a disk, where
VFAT is enabled, you can safely access it from the TOS. If you do have
VFAT entries there (long filenames), to properly access that directory
(including deletions) you need a filesystem that understands the VFAT
extension.

--
Konrad M.Kokoszkiewicz
|mail: draco@mi.com.pl                  | Atari Falcon030/TT030/65XE |
|http://www.orient.uw.edu.pl/~conradus/ | ** FreeMiNT development ** |

** Ea natura multitudinis est,
** aut servit humiliter, aut superbe dominatur (Liv. XXIV,25)
*************************************************************
** U pospolstwa normalne jest, ze albo sluzy ono unizenie,
** albo bezczelnie sie panoszy.