Hi Andy,
I think it's me you're talking about...
Reposting the message (I hope this is the solution for Marcelo's problem):
#Hello again Greg,
#
#Jochen Hoenicke solved this for me once.
#Basically, the �irq� and/or �io� information of the PC parallel port are
#missing. You have to tell the parport module which irq/io to use, or else
#ftape can't find your tape driver.
#Assuming the modules are autoloaded via modprobe, try to append a line like
#this to /etc/conf.modules:
#
#options parport_pc io=IO irq=N
#
#where N (usually 7) is the irq and IO (usually 0x378) is the io adress of
#the parallel port. They can be found at the BIOS settings.
#
#Regards,
#Rafael Oliveira
#
#Greg Walker wrote:
#
#> What does it mean ... "Device not configured"?
#> ...
Bye
Rafael Oliveira
Andy Corteen wrote:
> My Ditto Max Pro is an internal drive, so I have no direct experience
> of the parport issue - but I recall someone on the list recently gave
> advice on the module options for correct operation of the external
> drive.
>
> Perhaps that person could re-post their message?
>
> >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
>
> On 15/11/99, 13:20:43, Marcelo Via Giglio <[EMAIL PROTECTED]> wrote
> regarding Re: ftape and ditto max (pro?):
>
> > Hello,
>
> > how can i install my external ditto max pro please do you help me??
>
> > Marcelo
>
> > On Mon, 15 Nov 1999, Andy Corteen wrote:
>
> > > 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]
> > >
> > >
> > >
