What follows is a reprint of the read.me file which you will find in the field test area for TSX-32 version 6.10, which will be the first version to support FAT-32. The 6.0x series will continue to be maintained in parallel for some time for maximum stability to customers who do not require FAT32, but do require "good old solid TSX". If you would like to field test FAT-32 support, you can download the field test from the FAT-32 ftp area.



COMMENTS AND INSTALLATION
-------------------------
This folder and zip file contain the field test for TSX
FAT32 support.  To field test FAT32, save your old TSX32.SYS
file, which resides in the root of C:, and copy the new one
in place.  Copy the DISKGEOM.EXE and ATFD.HDF into your
system directory, normally \TSX32SYS.  Regen and reboot.

OVERVIEW OF FAT-32 SUPPORT
--------------------------
This version of TSX-32 supports the FAT32 file system.
It will continue to be necessary to use tools such as
FDISK and FORMAT to create and parition disk drives.
Having done so, TSX will automatically recognize and
use the FAT32 parition.

FAT32 partitions can be as large as any drive you can
currently buy.  In TSX-32, the size of a single file is
limited to roughly 2.1 gigabytes.

Long filenames are NOT supported by this version of TSX.
You will not be able to create files with long filenames.
You can open existing files with long names by using the
"tilde" form of their filename.  However, deleting such
files under TSX and subsequently running SCANDISK would
result in an error message that there is a long file name
entry no longer associated with a file.

ENHANCED IDE SUPPORT INCLUDED
-----------------------------
In addition to the FAT32 support, this version of TSX-32
frees users from DISKGEOM problems.  It is still necessary
to run DISKGEOM when installing TSX-32, but by default the
geometry information found on the DEVICE statement (for
example, "/TRACKS=826/HEADS=255/PRECOMP=0/SECTRK=63" is
all ignored; any necessary geometry information is obtained
by querying the drive when the system starts.  In addition,
the (sometimes incorrect) information about the starting
block number and size of each partition on the UNIT statements
(for example, /STARTBLK=63/BLKSIZE=4192902) is also ignored
and can be omitted.  By default, TSX now reads IDE partiion
tables when it boots, as it has done on SCSI disks for some
time).

What all this means is that it's going to be MUCH easier to
configure IDE drives for TSX-32.  An acceptable definition of
a drive with many paritions can be this simple:

DEVICE=DH/HANDDEF=ATFD/CONTROLLER=A
    UNIT=0/DOSDRIVE=C
    UNIT=1/DOSDRIVE=D
    UNIT=2/DOSDRIVE=E
    UNIT=3/DOSDRIVE=F

Details of this change related to supporting old drives are
described below.  None of the following information matters
unless you are trying to use TSX-32 with very old IDE drives.


DISKGEOM DEFAULTS TO /DEVTYPE=LBA
---------------------------------
Because LBA mode is required for large drives, any new
DEVICE=DH statements generated by DISKGEOM now specify
/DEVTYPE=LBA instead of /DEVTYPE=UNIQUE.  This causes
the IDE driver to use LBA requests, which are based on
block number, instead of cylinder/sector/track type
requests.  The only reason to alter this new default
would be if you install TSX-32 on a new computer which
has a very old drive.  We have an 80 megabyte drive,
for example, which can't do LBA.

IDE DRIVES NOW DEFAULT TO /IDENTIFY
-----------------------------------
Although drive geometry is generally not required for
LBA mode, we have still changed the default mode of
operation to querying IDE drives when starting the system
for their geometry.  Again, the only reason to override
this new default, which would be done by placing
/NOIDENTIFY on the DEVICE=DH statement, would be to use
TSX-32 with a very old IDE drive.

NEW QUALIFIER /NOPTREAD
-----------------------
The /STARTBLK and /SIZE qualifiers on the unit statement
are ignored for IDE drives in this new kernel.  By default,
TSX-32 will read the partition table on an IDE disk just
as it has done for SCSI disks all along.  Should any problem
arise with the recognition of the paritions when TSX-32 starts,
you can force TSX to use the information found in the gen file
by including /NOPTREAD on the DEVICE=DH statement.