Many threshold and overrun changes precede recovery errors in my
experience - you are best to restrict the values for these during
ftape initialisation. It is widely reported (rightly or wrongly) that
it is not possible on the vast majority of PC platforms to get Linux
to drive the Ditto Max Pro at its full rated speed. By the way, I have
heard that the Ditto Max Pro is now obsolete, Iomega having handed it
over to a third party to look after until it dies.
The Ditto only achieves its quoted speeds under windoze as a result of
compromising multi-tasking etc. in the drivers, and the Linux driver
authors were not prepared to compromise this fundamental cornerstone
of *nix. I don't have the details of the argument, so I can't do more
than repeat their conclusions... real argument or excuse? Who knows.
I set the following parameters during module init, and have zero
problems with the drive (aside from an annoying lack of absolute speed...)
conf.modules - RedHat kernel 2.0.35, ftape 4.02-1, ftape-tools 1.07-1,
Ditto Max Pro + Dash card
============
alias char-major-27 zftape
options ftape -f ft_fdc_driver=ftape-internal,none,none,none
ft_tracings=3,3,3,3,3
options zftape -f ft_major_device_number=27
options ftape-internal -f ft_fdc_fc10=0 ft_fdc_mach2=0
ft_fdc_base=0x210 ft_fdc_irq=9 ft_fdc_dma=3 ft_fdc_rate_limit=2000 #
ft_fdc_threshold=15
If I followed the threads correctly, you have the jumper-ed version of
the Dash card, so using ISAPNP tools to configure it does not apply.
Regards, Andy
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 15/11/99, 07:45:17, "Mike Junghanns" <[EMAIL PROTECTED]> wrote
regarding ftape and ditto max (pro?):
> I have installed the unstable Version ( 17.September.1999?).
> I can now rewind the tape and open eject the tape.
> But i can't use the "stat" command of ftmt.
> The log-File shows, that the driver changes the threshold and the
transfer
> speed, because excessive overruns. The driver can't change the
transver
> rate.
> thanks
> Mike
> [EMAIL PROTECTED]
