Goslin, Paul wrote:

We've been working with Dell regarding this very issue. We have a 60
slot library and it had 3 IBM LTO2 drives until last December, when we
added two more drives. Before adding the drives, I think we had
persistent binding implemented via the IBM driver/registry lock down and
never had any problems with drive mapping changing across reboots. In
the process of adding the new drives, the Dell tech installed Dell
drivers for all the drives, including the new ones. Ever since, we've
had problems whenever the server was rebooted. We opened a case and we
tried some registry hacks (including adding the persistence entry
mentioned below), but nothing has worked so far. Now they recommend
either using an emulex elxcfg.exe utility (we have an emulex fiber card)
or installing SP2 for Win2003 server, which is supposed to include a fix

for this...

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER