i have also seen this and have had to take it one step further and delete
the operating system definitions for the library/drives and redefine them
there as well.

~kris


At 07:58 AM 1/12/00 +0000, you wrote:

We had the same problem last summer and nobody could help. The customer
using a Magstar 3570 could not label cartridges, out of an amount of 80
cartridges only about 20 were labeled, the others were stopped with an i-o
error. We changed the cartridges with no positive outcome. The ADSM support
hotline was unable to help.
This problem took me about a week, then I solved it for most of the
cartridges, but not all, in the following way. I deleted the library and
made a new device installation. Then I labeled one cartridge with the label
command (overwrite=yes) at the command line by repeating the command as
long as it was accepted without error. I know, it sounds strange. But after
the first succesfull labeling, it worked for most of the other cartridges.
There is no garanty to solve your problem in this way, but maybe it helps.
Good luck, Petra Peters

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Kristopher T. Domich
Systems Engineer
Dimension Enterprises
205 Van Buren Street
Suite 180
Herndon, VA 20170

+1.703.709.7500 x289    (O)
+1.703.709.7699         (F)
+1.703.932.1848         (C)
+1.800.946.4646 PIN 1708789     (P)
1708789 AT mobilecomm DOT net  (Text Page 200 Chars or Less)

PGP Key Available
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%