[lkml]   [1996]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: MSDOSFS misfeature
Followup to:  <>
By author: "Ulrich Windl" <>
In newsgroup:
> > Hello,
> >
> > I've played a bit with the MSDOS filesystem and found that when
> > it scans a directory, it doesn't stop on first entry starting with
> > zero byte, which causes it to show invalid files on some not so
> > cleanly formatted disks. I'm not pretty sure it's OK to have
> > garbage after the first empty directory entry, but the DOS itself
> > permits it, allowing implementors of disk utilities to misuse it.
> > Any ideas?
> Deleted files are 0xe5 like in CP/M. 0x00 is maybe just a performance
> hint for the slow dos. In CP/M time the disks were formatted with
> 0xe5, so no problem... I'd recommend a different formatter.

The specs are crystal-clear that 0x00 means no more files (directory
high water mark); any residue in the directory should be ignored.
0xe5 is used for unused entries that do not indicate the end of
directory (i.e. deleted files). 0x05 is used if the filename really
contains 0xe5...


PGP public key available - finger
"The earth is but one country, and mankind its citizens." -- Bahá'u'lláh
I don't work for Yggdrasil, but they sponsor the linux.* hierarchy.

 \ /
  Last update: 2005-03-22 13:37    [W:0.043 / U:8.792 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site