NAME

tm − tapemaster 1/2 inch tape drive

CONFIG — SUN-3 SYSTEM

controller tm0 at vme16d16 ? csr 0xa0 priority 3 vector tmintr 0x60
controller tm1 at vme16d16 ? csr 0xa2 priority 3 vector tmintr 0x61
tape mt0 at tm0 drive 0 flags 1
tape mt0 at tm1 drive 0 flags 1

CONFIG — SUN-2 SYSTEM

controller tm0 at mbio ? csr 0xa0 priority 3
controller tm0 at vme16 ? csr 0xa0 priority 3 vector tmintr 0x60
controller tm1 at mbio ? csr 0xa2 priority 3
controller tm1 at vme16 ? csr 0xa2 priority 3 vector tmintr 0x61
tape mt0 at tm0 drive 0 flags 1
tape mt0 at tm1 drive 0 flags 1

DESCRIPTION

The Tapemaster tape controller controls Pertec-interface 1/2” tape drives such as the CDC Keystone, providing a standard tape interface to the device, see mtio(4). 

SEE ALSO

mt(1), tar(1), ar(4S), mtio(4)

DIAGNOSTICS

tmn : no response from ctlr.

tmn: error n during config.

mtn : not online.

mtn : no write ring.

tmgo: gate wasn’t open.  Controller lost synch. 

tmintr: can’t clear interrupts. 

tmn : stray interrupts.

mtn: hard error bn=n er=%x.

mtn : lost interrupt.

BUGS

The Tapemaster controller does not provide for byte-swapping and the resultant system overhead prevents streaming transports from streaming. 

If a non-data error is encountered on non-raw tape, it refuses to do anything more until closed. 

The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the console. 

Sun Release 4.0  —  Last change: 9 October 1987