> On Oct 2, 2020, at 1:46 PM, Chuck Guzis via cctalk <cctalk@classiccmp.org> > wrote: > > On 10/1/20 11:40 PM, Warner Losh via cctalk wrote: >> On Fri, Oct 2, 2020, 12:05 AM Tom Hunter via cctalk <cctalk@classiccmp.org> >> wrote: >> >>> I have never figured out why Bob Supnik defined the magnetic tape >>> containers (TAP files) with the one byte padding for odd length records. >>> This seems very odd (pun intended). :-) >>> Even on a machine which couldn't write 32 bit numbers (the record lenght) >>> on odd boundaries you could write the 32 bit number as 4 individual bytes. >>> Does anyone know the reason? > > On the .TAP files that I provide to customers, I ignore the 16-bit > granularity and supply odd-length records as appropriate. You can certainly create tape container files like that, but those are not TAP format. Instead, they are E11 format. You should call them by their proper name. paul
- Re: 9 track tapes and block sizes Jeff Woolsey via cctalk
- Re: 9 track tapes and block sizes Chuck Guzis via cctalk
- Re: 9 track tapes and block sizes Holm Tiffe via cctalk
- Re: 9 track tapes and block sizes Paul Koning via cctalk
- Re: 9 track tapes and block sizes Chuck Guzis via cctalk
- Re: 9 track tapes and block sizes Jeff Woolsey via cctalk
- Re: 9 track tapes and block sizes Tom Hunter via cctalk
- Re: 9 track tapes and block siz... Warner Losh via cctalk
- Re: 9 track tapes and bloc... Jeff Woolsey via cctalk
- Re: 9 track tapes and bloc... Chuck Guzis via cctalk
- Re: 9 track tapes and ... Paul Koning via cctalk
- Old Terminals John Many Jars via cctalk
- Re: Old Terminals Chris Hanson via cctalk
- Re: 9 track tapes and ... Chuck Guzis via cctalk
- Re: 9 track tapes and ... Al Kossow via cctalk
- Re: 9 track tapes and ... Eric Smith via cctalk
- Re: 9 track tapes and ... Al Kossow via cctalk
- Re: 9 track tapes and ... Jeff Woolsey via cctalk
- Re: 9 track tapes and ... Chuck Guzis via cctalk
- Re: 9 track tapes and ... Warner Losh via cctalk
- Re: 9 track tapes and ... Chuck Guzis via cctalk