Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sdd.hp.com!usc!howland.reston.ans.net!EU.net!Germany.EU.net!netmbx.de!zrz.TU-Berlin.DE!zib-berlin.de!informatik.tu-muenchen.de!klimt
From: klimt@informatik.tu-muenchen.de (Wolfgang Klimt)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Looking for firmware for Tandberg TDC3660
Date: 23 Aug 1994 08:32:18 GMT
Organization: Technische Universitaet Muenchen, Germany
Lines: 26
Distribution: world
Message-ID: <33cc6i$1kv@hpsystem1.informatik.tu-muenchen.de>
References: <miff.777135979@apanix.apana.org.au>
Reply-To: klimt@Informatik.TU-Muenchen.DE
NNTP-Posting-Host: sunrbg4.informatik.tu-muenchen.de
Originator: klimt@sunrbg4
In article <miff.777135979@apanix.apana.org.au>, miff@apanix.apana.org.au (Michael Smith) writes:
> Says it all, really.
>
> I have a TDC3660 with the =08:15 SCSI-2 firmware which is giving me
> lots of trouble. I recently upgraded to this revision (changeover 8( )
> while the unit was nonoperational due to mechanical problems.
>
> I'm not 100% sure that the firmware's the problem, but I'd like to try
> an older/newer revision to see...
I'm using (or better: try to use) a TDC 3660 on th NCR Onboard
controller of a ASUS PCI-Board and it causes many problems. Actually,
only commands like st fsf, st bsf and so on seem to work, but setting
density and blocksize and even writing data with tar or dd causes an
Input/Output-Error, and I didn't manage to fix this. Does anybody know
a solution for it? Is this behavior caused by the NCR-chip or by the
Tape itself?
A quantum Harddisk also connected to the NCR-chip works fine.
Thanks -- Wolfii
--
--------------------------------------------------------------------------------
Wolfgang Klimt ******** klimt@informatik.tu-muenchen.de ******** IRC: wolfii
Windows 3.1 -- from the guys who brought you edlin