README.txt 
   Tapedrv.exe -- IBM Tape Device Firmware Utility - v1.1

Files
-----
   README.txt    This file
   Tapedrv.txt   Tapedrv documentation
   Tapedrv.exe   Tapedrv executable
   Tapedrv.msg   Tapedrv message file
   Tapedrv.ini   Tapedrv initialization file

Extraction of the ISO image
---------------------------
Once the ISO image file has been downloaded, use Adaptec CD Creator or a similiar tool to build the CD image from the ISO file.

How to use the CD ISO image
---------------------------

Once the CD image is built it can be run via various methods described below:
1.  Booting with the CD image file in the CDROM drive will automatically preform tape firmware level discovery and update any unit in need of updating.

2.  The update program can be run from a DOS command prompt within a Microsoft Windows environment.  Place the CD image in the CDROM bay and change directory to the CDROM drive letter. By typing "tapedrv autoupdate /p d:\Drivemic" where "d:" is the driveletter will invoke the application to run.

3.  Copy the files Tapedrv.exe, Tapedrv.msg, and Tapedrv.ini and the DRIVEMIC directory from the cd iso image file to a test directory.  For example:
      \tapedrv\Tapedrv.exe
      \tapedrv\Tapedrv.msg
      \tapedrv\Tapedrv.ini
      \tapedrv\DRIVEMIC

History
-------

1.1  - Add non-zero LUN support (Use new /z option if LUN0 only is needed);
     - Add "seagate_tr7" UpdateAlgorithm (for STT3401A)
     - Add "quantum_dlt_8k" UpdateAlgorithm (for DLT4000)
     - Add UpdateFlags = "<flagcharacters>" control
1.0  - Debug version (partial non-zero LUN support)
0.9  - Fix 'tapedrv status /o' broken in v0.8; 5K DOS memory reduction 
0.8a - Fix 'tapedrv status /r' broken in v0.8
0.8  - Fix for HP half-high and Win9x 3600 Library w/ 126I firmware
0.7  - Add support for device access via NT port driver
0.6  - Fixes for 3502 and 3600 Libraries and the IBM Ultrium-1
0.5  - Fix "Invalid device request reading drive c" errors during 
       DOS mode program initialization.
0.4  - Reduce maximum DOS mode memory requirement an additional 15K.
0.3  - Reduce maximum DOS mode memory requirement by about 12K.
0.2  - Add DOS mode memory usage logging
     - Hide cursor after status and prompt line update
     - Fix command line option character case insensitivity
0.1  - Second pass
0.0  - Initial pass


Library reboot
--------------
Both the 3600 and 8502 libraries need to be rebooted if the 
Library firmware is updated.
For autoupdate, Library devices are moved to the end of the 
list of devices displayed on the screen.  This reordering 
may reduce the requirement to reboot between Drive and 
Library update for the 3502. However, whenever Library 
firmware is updated, a Library power cycle as well as a 
host system reboot is recommended.

Known Issues
------------
- Firmware update fails for DLT7000 Drive in an 3502-R14 Library
  when a tape is present in the drive.  Customers need to be 
  instructed to eject any tapes, if present in tape drives, into 
  storage slots.
- If the message 
    "TAPEDRV8360 error: Timeout waiting device to become stable"
  is seen, try inserting a tape in the left most storage slot.


DOS Memory Requirement
----------------------
   Tapedrv v0.6 has the following DOS mode memory requirement:
   363K for Seagate Travan drives,
   337K for Seagate DDS-1 and DDS-2 with 256K EEPROM, and
    97K for all other drives.



Usage Hints
-----------
   To run the status simulation, use a command similar to: 
      \tapedrv\tapedrv statussim [/r] [/o outfile]

   To run the autoupdate simulation, use a command similar to: 
      \tapedrv\tapedrv autosim

   For any of the commands status, statussim, autoupdate, autosim, ÿa 
   log file may optionally be created by adding a /l <logfile> 
   parameter.

   Once firmware files are accumulated in a directory (e.g., 
   \FIRMWARE), re-run the autoupdate commands, using a commands 
   similar to: 
      \tapedrv\tapedrv autosim /p \FIRMWARE
      \tapedrv\tapedrv autoupdate /p \FIRMWARE
