DLTVS160.txt Driver File Contents (31r3020.exe)

IBM DLTVS160 firmware update and diagnostic - Windows 2000/Windows Server 2003

CONTENTS:

1.0 Overview
2.0 Change history
3.0 Installation and Setup Instructions
4.0 Configuration Information
5.0 Web sites and phone support
5.1 Web sites
5.2 Software service and support
5.3 Hardware service and support
6.0 Notices and trademarks
7.0 Disclaimer

1.0 Overveiw

The DLTVS160.exe file is a Microsoft Windows based self-extracting WinZip executable program that will automatically bring up a menu of selections to:

1: update the Firmware
2: Run TapeRx.exe Diagnostics
3: SCSI Inquiry
4: Enter Serial Number of tape backup unit
5: Exit program.

The file was built to be fully automated and will take effect immediately upon completion of the tape backup units reset after the firmware has been applied.

2.0 Change History

This document describes the changes since V34.0 for the V35.0 release of VS160 firmware.
The firmware consists of code that supports both Bluelite and Morpheus VS160 subsystems.

ENHANCEMENTS AND NEW FUNCTIONALITY

1. Description: If a Locate command terminates on EOD, a subsequent write type command will
create a bugcheck B0300037.
Root Cause: The read-to-write transition is failing due to incorrect position update at the end of
the Locate command.
Corrective Action: Properly update position at the completion of the Locate command.
2. Description: If the cartridge ejector arm is pressed in and then quickly released it can create a
bugcheck B0001100. For example, a person uses a finger to press the arm without a cartridge
being present.
Root Cause: The servo processor begins the load sequence and then upon recognition of the
cartridge present sensor status change, begins issuing messages for which the controller
processor is not prepared.
Corrective Action: Change made to recognize the condition and notify the controller processor
so that it can command the servo processor back into an appropriate state.
3. Description: A non-zero count field (bytes 2-4) on a Space EOD command will cause drive to
respond with a check condition.
Root Cause: Not properly ignoring count field on a Space EOD command.
Corrective Action: Ignore count field on a Space EOD command.
4. Description: If the drive has entered Dump to LEDs mode and an attempt is made to re-enter
the FrontPanel Wizard, it can create a bugcheck B0830029.
Root Cause: Not clearing a timer upon exit of Dump to LEDs mode.
Corrective Action: Properly clear timer upon exit of Dump to LEDs mode.
5. Description: Send Diagnostics command with PF=1 (byte 1, bit 4) and Parameter List
Length=0 (bytes 3-4) will create a check condition.
Root Cause: Send Diagnostics command is documented as not supporting the Page Format bit
and requiring it to be set to 0. This is an unforeseen exception condition.
Corrective Action: Ignore command and return good status.
6. Description: FrontPanel Wizard can allow multiple modes to be entered simultaneously which
can create erroneous data and/or bugchecks B0830000A and B0830029.
Root Cause: Unforeseen exception condition.
Corrective Action: Implement zone exclusion properties within FrontPanel Wizard.
7. Description: If an SDLT cartridge is loaded and the drive is powered off just as the load
process begins and proper tension has not yet been achieved, upon power-on the drive will
enter into an infinite tension/de-tension loop. The only way out of this loop is power-cycle the
drive at which point a dropped leader will occur.
Root Cause: The load ring motion on power-on exceeds the allowable range to insure the
leader stays engaged.
Corrective Action: Added code to learn the position of the load ring during power-on and only
move it in a direction that will insure the leader stays engaged. Also, the correct drive state was
added for an error during a mid-tape load on an exception cartridge.
8. Description: A timing condition exists where if the takeup reel is stopped just after the leader
is unhooked it may create a bugcheck B0500009.
Root Cause: The servo processor is entering the unloading state before signaling the controller
processor that an error has occurred. The subsequent unload command from the controller
processor is rejected because servo believes it is already unloading.
Corrective Action: Create a new drive state to signify an unload is necessary (due to the error
condition) but not yet in progress.
9. Description: A multi-initiator emulation test suite is failing due to strategically placed bus
resets creating race conditions.
Root Cause: Improper detection and handling of bus resets during large data transfers created
situations where the drive did not always properly flush the partial record from the buffer.
Corrective Action: Proper bus reset detection and write abort handling.
10. Enhancement: Made the Unload Button Mode Zone 7 (Dump Logs to Tape) non-operational.
11. Enhancement: Ensure tape is not loaded before entering Unload Button Mode Zone 6
(Read/Write Diagnostics) to avoid potentially overwriting current media in the drive which
might have been part of a recent customer data operation.
12. Description: Bugcheck B0300043 on read of 256KB record when buffer is nearly empty.
Root Cause: If the read queue is not full and a DMA burst is started, a certain alignment of
data within the entities and timing of loading read data into the buffer will cause firmware to
lose track of its location in the data buffer.
Corrective Action: Insure the read queue is full before starting a DMA burst.
13. Description: Bugcheck B0500009 on an ERASE command on a write-protected tape.
Root Cause: Unforeseen exception condition.
Corrective Action: Check for write-protect status in erase function.
14. Description: If the drive is in a condition where on a power loss during loading the takeup
reel can stop prior to the supply reel, the continuing supply reel motion can allow the cartridge
buckle and drive leader to separate.
Root Cause: At the proper location in the tape path when power is lost, the supply reel is
capable of staying in motion for a short distance (1/8”-1/4”) because of its large inertial mass.
The takeup reel stops quickly, because of its small inertial mass. The additional movement of
the supply reel causes the drive leader end to slip out of the cartridge buckle. When power is
re-applied, the tip and buckle are already separated and cannot be recovered.
Corrective Action: Control both reel motors during the tape path loading process which
produces improved tape position handling and speed control.
15. Enhancement: Added function to learn load ring position before moving it to a new position.
Also added function as part of the midtape load process to detect and recover from condition
where takeup reel flange is located on the wrong side of the buckler flange.
16. Enhancement: Only write evflash dump if at least 8 tape motion hours have accumulated
since last evflash dump (or if evflash is empty) so that original error dump is not overwritten
due to secondary error conditions.
17. Enhancement: Compression can be inadvertently enabled if a MODE SELECT is issued
with default density. Change was made to not affect compression mode when default density is
issued. The only valid method to enable/disable compression is via MODE SELECT Pages
0Fh (Data Compression Page) and 10h (Device Configuration Page).

ENHANCEMENTS AND NEW FUNCTIONALITY FOR LIBRARY DRIVE APPLICATIONS

1. Description: Set File Protect [0x18] is only functioning when tape is loaded, which is opposite
of its intended function.
Root Cause: Specification misinterpretation.
Corrective Action: Allow Set File Protect [0x18] to only function when tape is unloaded.
2. Description: Media Type (byte 0, bits 3-0) in the SEND TAPE DATA 3 response packet
shows 0x0 No Tape/Unknown Tape during a cleaning operation.
Root Cause: Two different possible cleaning tapes created a mistake in coding of the response
packet.
Corrective Action: Correct Media Type to appropriately show 0x1 Cloth Cleaning Tape or 0x9
VS Cleaning Tape during a cleaning operation.
3. Description: Clean Requested (byte 3, bit 3) in the General Status Packet is not being set upon
a permanent read error or 250 tape motion hour threshold.
Root Cause: The Cleaning Required bit was instead mistakenly being set.
Corrective Action: Properly set Clean Requested bit.
4. Description: Library interface TapeAlert flags are not always set synchronously with the host
interface TapeAlert flags.
Root Cause: Specification misinterpretation.
Corrective Action: Insure all TapeAlerts flags are set synchronously on both the library
interface and host interface.

3.0 Installation and Setup Instructions

This file is a self-extracting WinZip executable file that will self extract to the systems dedicated temporary directory and run via a batch file. A self-test and bus reset are performed at the end of the update and the device will then be again ready for use.

4.0 Configuration Information:

The system must recognize that the device is available to the operating system to run either the firmware update or diagnostics. If the hardware cannot be found in Device Manger than the application layer utilized will not be able to preform it's operations.

-------------------------------
5.0 Web sites and phone support

Information and assistance is available through the IBM Web site
and by phone.

5.1 Web sites

IBM Support Web Site:
http://www.ibm.com/pc/support/

IBM eServer Web site:
http://www.ibm.com/eserver/xseries/

IBM IntelliStation Web site:
http://www.ibm.com/pc/intellistation/

5.2 Software service and support
--------------------------------

Through IBM Support Line, you can get telephone assistance, for a
fee, with usage, configuration, and software problems with xSeries
servers, IntelliStation workstations, and appliances. For
information about which products are supported by Support Line in
your country or region, go to
http://www.ibm.com/services/sl/products/.

For more information about Support Line and other IBM services, go
to http://www.ibm.com/services/, or go to
http://www.ibm.com/planetwide/ for support telephone numbers. In
the U.S. and Canada, call 1-800-IBM-SERV (1-800-426-7378).

5.3 Hardware service and support
--------------------------------

You can receive hardware service through IBM Services or through
your IBM reseller, if your reseller is authorized by IBM to
provide warranty service. Go to http://www.ibm.com/planetwide/ for
support telephone numbers, or in the U.S. and Canada, call
1-800-IBM-SERV (1-800-426-7378).

In the U.S. and Canada, hardware service and support is available
24 hours a day, 7 days a week. In the U.K., these services are
available Monday through Friday, from 9 a.m. to 6 p.m.

6.0 NOTICES AND TRADEMARKS

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some jurisdictions do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this
statement may not apply to you.

This information could include technical inaccuracies or
typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new
editions of the publication. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

IBM, the e-business logo, eServer, IntelliStation, xxx, and xxx
are trademarks of the IBM Corporation in the United States, other
countries, or both.

******************************************************************

The following terms are trademarks of International Business
Machines Corporation in the United States, other countries, or
both:

e-business logo
eServer
IBM
IntelliStation
xxx
xxx
******************************************************************

Intel, MMX, and Pentium are trademarks of Intel Corporation in the
United States, other countries, or both.

Microsoft, Windows, and Windows NT are trademarks of Microsoft
Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United
States and other countries.

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both.

Adaptec and HostRAID are trademarks of Adaptec, Inc., in the
United States, other countries, or both.

Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based
trademarks and logos are trademarks or registered trademarks of
Red Hat, Inc., in the United States and other countries.

Other company, product, or service names may be trademarks or
service marks of others.

7.0 Disclaimer (Required)
----------------------------

7.1 THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF
ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS
OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
LICENSES TO ANY PATENTS OR COPYRIGHTS.

7.2 Note to Government Users
Include the following note after the disclaimer paragraph.

Note to U.S. Government Users -- Documentation related to
restricted rights -- Use, duplication or disclosure is
subject to restrictions set forth in GSA ADP Schedule
Contract with IBM Corporation.

Download Driver Pack

DLTVS160.txt Driver File Contents (31r3020.exe)

Recent Help Articles

More Popular Downloads

How To Update Drivers Manually

Recent Help Articles

More Popular Downloads