This is Release 1.0 of FS-TST (1 May 2002), a package of programs 
that can be used to support testing of disk imaging tools used in 
computer forensic examinations.  The package can be downloaded from
the WWW.CFTT.NIST.GOV web site. Everything is offered as is. This 
package is under active development.

This software uses the BIOS to access both IDE and SCSI disks.

Know bugs and restrictions
(1) The mapping between drive numbers assumes the the BIOS is
configured to look at IDE drives first. If the BIOS looks at SCSI
drives first (e.g., set the BIOS to boot from SCSI) and there are SCSI
and IDE drives present, this software thinks that disk 0x80 is the
first IDE disk. This would be incorrect. The first SCSI disk
would be disk 0x80. Anytime both SCSI and IDE disks are installed,
BIOS boot order must be IDE first.
(2) Unusual disk hardware may not be handled properly. Examples
include:  Disks with sector per track values other than 63. IDE drives
not attached to an IDE controler (e.g., "Promise board") may be
reported as non-IDE drives.

File inventory
Readme.txt  This readme file
*.CPP       C source file
*.IDE       Borland C++ Version 4.5 project file (makefile)
*.ASM       Assembler Source file (you need turbo assembler)
*.EXE       Compiled and linked C executable
*.COM       Compiled and linked assembler executable
*.H         C header files
mx.bat      run the assembler and linker (you need to set the path to tasm)
*.doc       Documentation in Word 2000
what.txt    SCCS Version number of each program

Locating items
beta/       An older version of the software used to test dd 4.0.36.
            Only programs used in the dd testing are included.
beta/diffs  For each file in beta, a list of differences between
            the beta version and the current version.
bin/        The current version of FS-TST. Used on Safeback 2.18
doc/        Documentation
src/        The source for the current version.
src/SCCS    The SCCS history files for each source file.

Some questions and answers:

Which version (beta or current) should be used? 
Normally the current version should be used since the current version
is the latest. However, if it is important to use the exact software
used by NIST to test dd version 4.0.36, then use the beta version even
though the beta version is older.

What about support or help?
None. Well almost none. If you call me, Jim Lyle (301) 975-3270 or
email JLYLE@NIST.GOV, I will give limited help as time permits.

How do I install the software?
You don't really install the software anywhere. Copy the exe and com
files to a DOS floppy or burn to a CD.

Are the programs DOS, Windows or UNIX?
Things are a little of all three. The programs all run from a DOS
environment. MS-DOS 6.3 was our execution environment.
The Borland C++ 4.5 was running in Windows 98, with the target
platform set to DOS STANDARD and the memory model set to HUGE, i.e.
the development environment was Windows 98.
The source files are kept on a UNIX (Solaris 7.0) file server with
version control kept by SCCS, i.e. version control was managed in
a UNIX environment.

What is SCCS?
A version control system for the UNIX or Linux environment.

What information can be obtained from the history files in src/SCCS
and how can that be done?
The SCCS history files allow any earlier version of the software to
be reconstructed. To use the SCCS files, they need to be accessed
from a UNIX of Linux environment with the SCCS programs. Any earlier
version of a program can be brought back. For example, to obtain
version 2.5 of zbios.cpp, the command would be:
sccs get -r 2.5 zbios.cpp
Other information that can be obtained includes: creation dates and
reason for change comments for each version.

Can I modify and redistribute the software?
Sure, just give us credit and add a notice of what was changed.
Note the following comment included in each program ...
The software provided here is released by the National
Institute of Standards and Technology (NIST), an agency of
the U.S. Department of Commerce, Gaithersburg MD 20899,
USA.  The software bears no warranty, either expressed or
implied. NIST does not assume legal liability nor
responsibility for a User's use of the software or the
results of such use.

Please note that within the United States, copyright
protection, under Section 105 of the United States Code,
Title 17, is not available for any work of the United
States Government and/or for any works created by United
States Government employees. User acknowledges that this
software contains work which was created by NIST employees
and is therefore in the public domain and not subject to
copyright.  The User may use, distribute, or incorporate
this software provided the User acknowledges this via an
explicit acknowledgment of NIST-related contributions to
the User's work. User also agrees to acknowledge, via an
explicit acknowledgment, that any modifications or
alterations have been made to this software before
redistribution.