Hi Steve,
I bought a Pertec 1600 which is supposed to read TR-2 tapes. I had
similar
problems related to inability to process the header. I have not been
able to
resolve the problem with my system but perhaps getting yours going will
help.
As far as I know, Pertec is out of business, so no help will be coming
from there.
Did you get the drive to work under Windows ?
The devices you have to create with a script that comes with either
ftools or
ftape and does the make devices. Check the documentation. It has been
too long
and I am at work, while I have my system at home.
Cheers,
Paul
Steve Hale wrote:
>
> I'm having trouble with an internal drive made by 'Pertec' and called
> 'MyTape 800'. It uses 'TR-1' tapes.
>
> I'm very new to Linux so please forgive any obvious lack of
> knowledge on my part!
>
> The hardware is a TXPRO 11 motherboard with a Cyrix M2 333 processor.
> The floppy interface is 'on board'. The Kernel is version 2.2.10 and i'm
> using the SuSE V6.2 distribution. Ftape V3.04d is installed. I have
> compiled the kernel for Ftape support. I can 'insmod' the Ftape and
> zftape modules without error. Now onto the problem....
>
> All tape transport operations e.g. 'retention' etc. work fine. However
> if i try and erase/format/write or read a tape i receive an
> 'input/output' error. The follow is an edited extract from the log:
>
> zftape-init.c (zft_init) - zft_init @ 0xc2845ca8.
> kernel: [009] zftape-init.c (zft_init) - installing zftape VFS interface
> for ftape
> driver ....
> kernel: [010] fdc-io.c (fdc_config) - fdc base: 0x3f0, irq: 6, dma: 2.
> kernel: [011] fdc-io.c (fdc_probe) - Type 8272A/765A compatible FDC
> found.
> kernel: [012] ftape-ctl.c (ftape_get_drive_status) - status: new
> cartridge.
> kernel: [013] ftape-ctl.c (ftape_log_vendor_id) - tape drive type:
> PERTEC
> MyTape 800.
> kernel: [014] ftape-io.c (ftape_report_configuration) - TR-1 tape
> detected.
> kernel: [015] ftape-ctl.c (ftape_init_drive) - post QIC-117B drive @ 500
> Kbps.
> kernel: [016] ftape-ctl.c (ftape_calibrate_data_rate) - Highest FDC
> supported
> data rate: 500 Kbps.
> kernel: [017] ftape-io.c (ftape_report_configuration) - TR-1 tape
> detected.
> kernel: [018] ftape-ctl.c (ftape_init_drive) - unknown length QIC-80
> tape.
> kernel: [019] ftape-read.c (ftape_decode_header_segment) - calculated
> tape
> length is 1033 ft.
> kernel: [020] ftape-read.c (ftape_decode_header_segment) - Tape
> parameters inconsistency, please report.
> kernel: [021] ftape-read.c (ftape_decode_header_segment) - reported =
> 4/504/36/71/254/128.
> kernel: [022] ftape-read.c (ftape_decode_header_segment) - required =
> 4/504/36/17/254/128.
> kernel: [023] zftape-rw.c (zft_erase) -
> ftape_read_header_segment(zft_hseg_buf) failed: -5.
> kernel: [024] ftape-ctl.c (ftape_disable) - == Non-fatal errors this
> run: ==.
> kernel: [025] ftape-ctl.c (ftape_disable) - fdc isr statistics:
>
> >From the above i'm assuming that the 'Tape parameters inconsistency' is
> the main problem. On another note, when using 'Ftape-tool', it tries to
> use devices called
> 'nqft0' and 'nrawft0'. These devices do not exist at all in my '/dev'
> directory!
> How do i correct this?
>
> Any help and advice on getting the tape drive working would be most
> appreciated,
> i've spent a lot of time configuring Linux and now i need to back it
> up!!
> All the best...
>
> --
> >From Steve Hale
> http://www.moneygods.co.uk/steve
>
> ------------------------------------------------------------------------
> Name: RFC-822.TXT
> RFC-822.TXT Type: Plain Text (text/plain)
> Encoding: base64
> Description: RFC-822.TXT
