HP3000-L Archives

July 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Doug Werth <[log in to unmask]>
Reply To:
Doug Werth <[log in to unmask]>
Date:
Sat, 21 Jul 2001 22:39:42 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
"Jim Killam" <[log in to unmask]> writes:


> If you are going to use a DDS-3 drive to create an SLT then you need to
use
> a DDS-3 tape, I have yet to have  a system boot from a DDS-2 tape that was
> created on a DDS-3 drive. Really doesn't have anything to do with the O/S
> version as I have experienced this on 5.5, 6.0, and 6.5.

I have also seen this phenomenon. Does anyone know what the reason for this
is?

It obviously has something to do with the creating of the SLT on DDS2 media
by a DDS3 drive (as opposed to a problem with a DDS3 drive reading a DDS2
SLT.) I conclude this for several reasons. First, we have created many DDS2
SLTs that have been used to load on DDS3 drives. Second, the factory SLTs
are still delivered on DDS1 60 meter tapes. Consequently DDS3 drives have no
inherent difficulties reading non-DDS3 SLTs. The only problem appears to be
reading a non DDS3 tape specifically created on a DDS3 drive.

It appears to me that this is somewhat of a time-bomb waiting to go off on
an unsuspecting system manager who creates his/her SLTs in this manner. Do
we know what the problem is? Is it a SYSGEN problem? A firmware issue on the
DDS3 drives? Is it going to be fixed?

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2