> I have an Overland 4000E Lib with LTO3 and LTO5FC drives
> working like a charm with Win2008R2 and NSR75.
> I have standard Win2008 LTO Tape drivers and reg key for
> permanent device naming.

2 things about that - according to the Overland tech guy I had here on 
Friday, the "E" series is a completely different build that the non-"E" 
series. They use completely different circuitry and builds, he told me. So 
a 4000 and a 4000E are not similar hardware (he said).

Also, I am not yet on Win2008. I hope and plan to, when the budget cycles 
again in Sept/Oct. I'm trying to make it through to the hardware refresh, 
where I will migrate from my Win2003 32bit to Win2008 R2 64bit. Then 
ideally, this problem will go away, since I will be using the Win2008 LTO 
drivers.

I use the reg key for permanent naming, too. In my case, I've had more 
problems with the SCSI ID changing (even though it's a giber connected 
library).

> 
> Th
> 
> -----Message d'origine-----
> De : EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> De 
la
> part de Michael Leone
> Envoyé : lundi 30 juillet 2012 14:52
> À : NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Objet : Re: [Networker] Anyone having problems with HP LTO tape drivers 
for
> Windows?
> 
> > Hi Michael,
> > 
> > I have seen this or a related problem on different sites using 
(always) 
> new 
> > (2011-2012) overland tape libraries.
> 
> This library is from 2008 ...
> 
> > The workaround was to label the (blank) tapes on a different server. 
> Does it 
> > happen with labelled tapes or only blank ones?
> 
> Labeled tapes. (altho I have seen it happen once, maybe twice, when 
> labeling blank tapes). And I don't have another server to use, nor 
another 
> LTO-4 drive to label tapes.
> 
> > If you cannot downgrade,  that may happen because the 1.0.6.3 
> > driver files are 
> > still on the windows directories. Try uninstalling the 1.0.6.3 
> > driver, remove 
> > all the 1.0.6.3 files  and reboot the windows machine. That might 
work.
> 
> I don't know what all the 1.0.6.3 files are. :-) I did reboot between 
> uninstalling, and trying to re-install, to no luck. I will try again 
> today, if I can.