If you are not yet at Win2k3 SP1 or you use the workaround mentioned
below, you may be limited by the SCSI/FC adapter setting MaximumSGList. 
Itzik

> -----Original Message-----
> From: Legato NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of f_x
> Sent: Wednesday, November 02, 2005 13:13
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Incorrect block size in Windows2003
> 
> Hi,
> 
> a article on the german support page states that if you use 
> w2k3 SP1 the tape.sys driver limits the blocksize to 64kb. 
> The workaround is to use the tape.sys from w2k3.
> 
> I don't know if there is a english version of the article.
> ftp://ftp.legato.com/pub/NetWorker/German/ntgen_67.pdf
> 
> On Mi, November 2, 2005 11:52, Pierpa wrote:
> > Hi,
> > I've setup my ADIC ascalar library with 2 IBM LTO Ultrium 2 
> drives, in 
> > SAN  with A Windows2003 Networker 7.2.1 server. In order to setup a 
> > LTO blocksize of 256K, I've used the variable 
> > NSR_DEV_BLOCK_SIZE_LTO_ULTRIUM_2 to 256, and it seems to 
> work fine ( 
> > infact, as soon as I boot my networker server it says "LTO 
> Ultrium-2 
> > set to 256K". If I check on my Windows2003 box, the IBM 
> drivers sets these parameters:
> >
> > Max blocksize  2097152
> > min blocksize   1 default blocksize 65536
> >
> > but, if I check a tape with "mt -f \\.\Tapex status" command I see 
> > something like :
> >
> > default blocksize  65536 minimum blocksize  1 maximum blocksize  
> > 131072
> >
> > So, the maximum blocksize is not the same I see using the GUI. Of 
> > course,  If I try to label a tape from networker, I see 
> from scanner 
> > utility the block size to 128K and not 256K as I fixed 
> using the NSR 
> > variable. I've installed/uninstalled the devices drivers several 
> > times, but I see always  the same frustrating difference 
> between the 
> > GUI and the mt command. Of course the real blocksize on the 
> tape is never 256K as I need, but 128k.
> > Have I missed something ? There is something else I have to check ( 
> > even on the registries )??
> >
> > Any help is really apprecited
> > Pierpa
> >
> >
> > 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 wit 
> > 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
> >
> >
> >
> 
> 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 wit 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
> 

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
wit 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