9 track tapes and block sizes

I have over 1000 TAP images in my collection, so I thought I'd give this a whirl.? It's handy for a quick summary of what the TAP image is.? However, documentation is a bit light, as is its robustness for corrupt TAP images (of which I have plenty), although it seems forgiving of unpadded blocks (unlike another, stricter tool I could mention). For unlabelled tapes, it lists block count and min and max block size for each file. Nice. But it does not do that for labelled tapes; instead they get the labels that enclose each dataset decoded, and the number of blocks is reported and checked.? A warning is printed if the actual block count differs.? Sometimes this warning is incorrect, reporting 0 or a large negative number (-17342528 usually) of blocks.? It is usually correct for those of my tapes that have duplicate blocks (which I don't expect it to detect/report otherwise).? The 0s might be extraneous EOF1/EOV1 labels.? The negatives might be extraneous tapemarks.? Or stuff past EOI. It would be nice if it printed the name of the TAP file in its report. Built from source (edited Makefile to add $(CC) ).??? I didn't try vtapecp. -- Jeff Woolsey {{woolsey,jlw}@jlw,first.last@{gmail,jlw}}.com Nature abhors straight antennas, clean lenses, and empty storage. "Delete! Delete! OK!" -Dr. Bronner on disk space management Card-sorting, Joel. -Crow on solitaire