Academia.eduAcademia.edu

Figure 1 – uploaded by Simson Garfinkel

See full PDFdownloadDownload figure
Figure 2. AFF file schematic. Figure 8. AFF segment schematic.

Figure 2 AFF file schematic. Figure 8. AFF segment schematic.

Related Figures (5)

Table 1. Comparison of AFF and EnCase (all values in MB). Table 1 compares the sizes of AFF and EnCase images of a 6 GB hard drive. The hard drive was filled with: (i) all zeroes, (ii) the complete works of William Shakespeare repeated approximately 1,200 times, and (iii) random data. AFF used gzip compression performed at levels “1,” “6” and “9” with aimage -X1, -X6 and -X9 options. EnCase compression was performed using the “Good” and “Best” levels. images Call be spilt Mto Mu itiple les (e€.g., Or arCOival tO UlJ OF DVL). A limitation of the EnCase format is that image files must be less than 2 GB in size. As a result, | FinCase images are typically stored in direc- tories with the individual file’s given names (e.g., FILE.E01, FILE. E02, etc.). The format also limits the type and quantity of metadata that can be associated with an image. Some vendors have achieved limited com- patibility by reverse-engineering the format; however, these attempts are generally incomplete.
Table 1. Comparison of AFF and EnCase (all values in MB). Table 1 compares the sizes of AFF and EnCase images of a 6 GB hard drive. The hard drive was filled with: (i) all zeroes, (ii) the complete works of William Shakespeare repeated approximately 1,200 times, and (iii) random data. AFF used gzip compression performed at levels “1,” “6” and “9” with aimage -X1, -X6 and -X9 options. EnCase compression was performed using the “Good” and “Best” levels. images Call be spilt Mto Mu itiple les (e€.g., Or arCOival tO UlJ OF DVL). A limitation of the EnCase format is that image files must be less than 2 GB in size. As a result, | FinCase images are typically stored in direc- tories with the individual file’s given names (e.g., FILE.E01, FILE. E02, etc.). The format also limits the type and quantity of metadata that can be associated with an image. Some vendors have achieved limited com- patibility by reverse-engineering the format; however, these attempts are generally incomplete.
Table 2. Summary of features supported by various file formats.
Table 2. Summary of features supported by various file formats.
Table 3. AFF segments defined in the AFF 1.0 specification.
Table 3. AFF segments defined in the AFF 1.0 specification.
Some AFF Segments created by the Advanced Disk Imager
Some AFF Segments created by the Advanced Disk Imager
Figure 4. Screenshot of aimage in action.
Figure 4. Screenshot of aimage in action.
580 California St., Suite 400
San Francisco, CA, 94104
© 2025 Academia. All rights reserved