Return to BSD News archive
Xref: sserve comp.unix.admin:7262 comp.unix.bsd:5525 comp.unix.internals:5265 comp.unix.sysv386:24063 comp.unix.ultrix:13905
Newsgroups: comp.unix.admin,comp.unix.bsd,comp.unix.internals,comp.unix.sysv386,comp.unix.ultrix
Path: sserve!manuel!munnari.oz.au!uunet!unislc!dold
From: dold@unislc.uucp (Clarence Dold)
Subject: Re: SCO Can't Read 8-mm Tape Written by Ultrix.
References: <1992Sep22.153418.2197@sco.COM>
Message-ID: <1992Sep23.155827.12979@unislc.uucp>
Organization: Unisys Corporation SLC
Date: Wed, 23 Sep 1992 15:58:27 GMT
Lines: 29
>From article <1992Sep19.193954.1497@morrow.stanford.edu> karish@pangea.Stanford.EDU (Chuck Karish) writes:
> In article <BusMMF.12I@npt1.uucp> root@npt1.uucp writes:
> > I need to transfer data via 8-mm tape (Exebyte 8800 drives on both
> >systems) from an Ultrix 4.2A system to a SCO 3.4 system. So far, I have been
> >unable to do so.
>
> ...
> I tried reading tapes written on Suns and RS/6000s on an
> SCO system, with no success. The SCO system tells me
> "block size 0", saws thew tape back and forth, and gives up
> after three or four minutes.
On AIX 3.1 - RS6000, I used SMIT to set the block size to 0 for the 8MM, so
that it would write blocks properly.
I read a rather large tar tape onto a SCO 3.2.4 machine, with one oddity.
Files that had 14 character file names on AIX wound up with 14 character
file names, followed by \001\002. Examining the directory entires, I see
that SCO got confused about whether the files were more than 14 characters
or not. It established the >14 style in the directory entry, but there was
nothing to put in the next line.
But, the tape did seem to read with no trouble. I made no adjustments on
the SCO machine.
--
---
Clarence A Dold - dold@unislc.slc.Unisys.COM
...pyramid!ctnews!tsmiti!dold