Sep 6 16:13:21 fabsoft2 linux: [000] fdc-io.c (fdc_config) - Using the standard fdc controller.
Sep 6 16:13:21 fabsoft2 kernel: [001] fdc-io.c (fdc_probe) - Type 82077AA FDC found.
Sep 6 16:13:24 fabsoft2 linux: [002] ftape-ctl.c (ftape_activate_drive) - drive wakeup method: Mountain.
Sep 6 16:13:26 fabsoft2 linux: [003] ftape-io.c (ftape_set_data_rate) - post QIC-117B drive @ 1 Mb/s.
Sep 6 16:13:26 fabsoft2 linux: [004] ftape-io.c (ftape_set_data_rate) - 307 ft. QIC-80 tape.
Sep 6 16:13:28 fabsoft2 linux: [005] ftape-read.c (read_header_segment) - header segments are 0 and 1.
Sep 6 16:13:28 fabsoft2 linux: [006] ftape-bsm.c (extract_bad_sector_map) - 130 bad sectors.
Sep 6 16:13:44 fabsoft2 linux: [007] fdc-io.c (fdc_result) - fdc not ready.
Sep 6 16:13:44 fabsoft2 linux: [008] fdc-isr.c (fdc_isr) - probably fatal error during FDC Result Phase.
Sep 6 16:13:44 fabsoft2 linux: [009] fdc-isr.c (fdc_isr) - drive may hang until (power) reset :-(.
The last three of this messages appear whenever the tape is accessed, however,
the tape is working in some way, this means i can write and read tape archives
with tar, even big ones.
In contrast, Taper-6.7.4 is not working, it creates archives, but cannot read them back.
Has anybody had similar problems and solved them ?
-- Martin Cornelius, ZARMFAB software development, University of Bremen phone: 49-421-218-4807 FAX: 49-421-218-3889 email: fabsoft@zarm.uni-bremen.de paper-mail: Hochschulring / Am Fallturm, 28359 BREMEN, Germany