Re: 1.5.12: mt sees incorrect maximum block size

2004-12-16 Thread Corinna Vinschen
On Dec 15 10:36, Brian Dessent wrote: > Corinna Vinschen wrote: > > > So, as you can see, the Windows NT tape functions doesn't allow me to set > > the block size to more than 64K, too. That's the same functionality used > > inside of Cygwin. I have no idea how to workaround that. I also didn't

Re: 1.5.12: mt sees incorrect maximum block size

2004-12-15 Thread Brian Dessent
Corinna Vinschen wrote: > So, as you can see, the Windows NT tape functions doesn't allow me to set > the block size to more than 64K, too. That's the same functionality used > inside of Cygwin. I have no idea how to workaround that. I also didn't > find anything useful on the Web so far. > >

Re: 1.5.12: mt sees incorrect maximum block size

2004-12-15 Thread Corinna Vinschen
On Dec 14 14:36, Richard Simon wrote: > when I attempt to set the correct block size with mt (or try to do so with > tar) I am unable to do so. > mt status 2 reports a maximum block size of 65535, whereas the windows driver > and the winTarSCSI utility both report a much larger maximum block size

1.5.12: mt sees incorrect maximum block size

2004-12-14 Thread Richard Simon
when I attempt to set the correct block size with mt (or try to do so with tar) I am unable to do so. mt status 2 reports a maximum block size of 65535, whereas the windows driver and the winTarSCSI utility both report a much larger maximum block size of 16777214 I can use the winTarSCSI utili