> Bela Lubkin wrote:

> > But, all that aside, I would recommend against suppressing the message
> > even if you were able to pinpoint a single bit in `cha_print_notices'
> > which controlled it. The fact that the controller burps up that notice
> > at boot time is well enough known to appear in the FAQ. The drive
> > works. So just ignore the notice.
> >
> > If you get the _same_ notices later, during actual drive operation,
> > you'll want to see them -- otherwise the drive will seem to have just
> > mysteriously failed.
>
> My memory of this is that it happens every time the drive is accessed.
> I've never been able to convince a customer to just "ignore it" though..
>
> My feeling is to silence it. If the drive fails, you either know it
> because it failed completely or you start getting flaky verification
> errors. If it supports TapeTell then you can get more info from that
> anyway.

I didn't know it was issuing the warning on every access. That ups the
annoyance factor considerably. Then I would say: go ahead and disable
the warning (preferably by determining exactly what bit(s) to set in
those space.c variables) _if and only if_ the tape drive is the only
device on that adapter. If you have any other drives on the same
adapter, you'd be unwise to turn off warnings that might alert you to a
real problem...

>Bela<