@@ -171,7 +171,7 @@ is a new and potentially harmul feature so do not experiment on a unique
171
171
copy of an ADF image with your precious data. Do it on a copy (and report
172
172
if any issues are encountered).
173
173
174
- Update: The notice above is especially actual that it was discovered that
174
+ Update: The notice above is especially actual as it was discovered that
175
175
the version ` 0.8.0 ` and earlier ** do not rebuild the block allocation bitmap
176
176
for volumes where it is marked invalid** . In short, this means that if the bitmap
177
177
is really incorrect, writing to such volume may lead to data loss/corruption
@@ -180,6 +180,18 @@ Because of this, it is strongly advised to **UPDATE TO THE LATEST VERSION**.
180
180
181
181
(See also TODO and BUGS).
182
182
183
+ ### DirCache
184
+ Dircache is an existing but somewhat exotic feature of the FFS.
185
+ Until now, I haven't encountered any disk image with this enabled. The only
186
+ one with dircache set on the volume is one of the test floppies for the ADFlib
187
+ (testffs.adf)...
188
+
189
+ While dircache support is implemented in ADFlib (at least, to certain extent),
190
+ so far, there are no tests of dircache. As such, assume that this feature is
191
+ practically ** not tested** .
192
+ While it can be used rather safely in read-only mode, be very careful with
193
+ write mode using a volume with dircache enabled.
194
+
183
195
184
196
## The API documentation in doc/
185
197
... in major part is outdated. The lib underwent many changes and, possibly,
0 commit comments