> On Oct 18, 2018, at 4:31 AM, Christian Corti via cctalk > <cctalk@classiccmp.org> wrote: > > On Wed, 17 Oct 2018, Clem Cole wrote: >> As Paul W pointed out correctly, the TK50 and its children in the DLT* >> family all used a fixed format 512 byte *blocks on the tape*. This > > And that is wrong. The TK50 clearly uses variable block sizes. For example, > have a look at a RSX11 or VMS tape: ... Different point. You're talking about the host programming interface; Clem was talking about the physical representation of the data on the tape. Clearly it's easy to accept random-length blocks from the host and translate them to a sequence of 512 byte blocks on the media. SIMH is an example of how that is done: it stores tape images as a count field plus data, laid down in a disk file that internally consists of a sequence of fixed length (512 bytes, traditionally) sectors. paul
- Re: [TUHS] Ultrix Tape: Block Size? Warner Losh via cctalk
- Re: [TUHS] Ultrix Tape: Block Size? Paul Winalski via cctalk
- Re: [TUHS] Ultrix Tape: Block S... William Pechter via cctalk
- Re: [TUHS] Ultrix Tape: Blo... Paul Koning via cctalk
- Re: [TUHS] Ultrix Tape... Ethan Dicks via cctalk
- TK50, was: Re: [TUHS] ... emanuel stiebler via cctalk
- Re: TK50, was: Re:... Ethan Dicks via cctalk
- Re: TK50, was: Re:... Paul Koning via cctalk
- Re: TK50, was: Re:... Clem Cole via cctalk
- Re: TK50, was: Re:... Christian Corti via cctalk
- Re: TK50, was: Re:... Paul Koning via cctalk
- Re: TK50, was: Re:... Warner Losh via cctalk
- Re: TK50, was: Re:... Tom Ivar Helbekkmo via cctalk
- Re: TK50, was: Re:... Tom Ivar Helbekkmo via cctalk
- Re: [TUHS] Ultrix Tape: Blo... Clem Cole via cctalk
- Re: [TUHS] Ultrix Tape: Blo... Paul Winalski via cctalk
- Re: [TUHS] Ultrix Tape: Block S... Clem Cole via cctalk
- Re: Ultrix Tape: Block Size? Christian Corti via cctalk