Return to ut.4 CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / man / man4 / man4.vax

Annotation of 43BSDReno/share/man/man4/man4.vax/ut.4, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1983 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)ut.4        6.1 (Berkeley) 5/15/85
                      6: .\"
                      7: .TH UT 4 "May 15, 1985"
                      8: .UC 5
                      9: .SH NAME
                     10: ut \- UNIBUS TU45 tri-density tape drive interface
                     11: .SH SYNOPSIS
                     12: .B "controller ut0 at uba0 csr 0172440 vector utintr"
                     13: .br
                     14: .B "tape tj0 at ut0 drive 0"
                     15: .SH DESCRIPTION
                     16: The 
                     17: .I ut
                     18: interface provides access to a standard tape drive interface as
                     19: describe in 
                     20: .IR mtio (4).
                     21: Hardware implementing this on the VAX is typified by the System
                     22: Industries SI 9700 tape subsystem.  Tapes may be read or written
                     23: at 800, 1600, and 6250 bpi.
                     24: .SH "SEE ALSO"
                     25: mt(1),
                     26: mtio(4)
                     27: .SH DIAGNOSTICS
                     28: .BR "tj%d: no write ring" .
                     29: An attempt was made to write on the tape drive
                     30: when no write ring was present; this message is written on the terminal of
                     31: the user who tried to access the tape.
                     32: .PP
                     33: .BR "tj%d: not online" .
                     34: An attempt was made to access the tape while it
                     35: was offline; this message is written on the terminal of the user
                     36: who tried to access the tape.
                     37: .PP
                     38: .BR "tj%d: can't change density in mid-tape" .
                     39: An attempt was made to write
                     40: on a tape at a different density than is already recorded on the tape.
                     41: This message is written on the terminal of the user who tried to switch
                     42: the density.
                     43: .PP
                     44: .BR "ut%d: soft error bn%d cs1=%b er=%b cs2=%b ds=%b" .
                     45: The formatter indicated a corrected error at a density other
                     46: than 800bpi.  The data transferred is assumed to be correct.
                     47: .PP
                     48: .BR "ut%d: hard error bn%d cs1=%b er=%b cs2=%b ds=%b" .
                     49: A tape error occurred
                     50: at block
                     51: .IR bn .
                     52: Any error is
                     53: fatal on non-raw tape; when possible the driver will have retried
                     54: the operation which failed several times before reporting the error.
                     55: .PP
                     56: .BR "tj%d: lost interrupt" .
                     57: A tape operation did not complete
                     58: within a reasonable time, most likely because the tape was taken
                     59: off-line during rewind or lost vacuum.  The controller should, but does not,
                     60: give an interrupt in these cases.  The device will be made available
                     61: again after this message, but any current open reference to the device
                     62: will return an error as the operation in progress aborts.
                     63: .SH BUGS
                     64: If any non-data error is encountered on non-raw tape, it refuses to do anything
                     65: more until closed.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.