Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!akgua!mcnc!decvax!tektronix!hplabs!sri-unix!bridger@Rand-Unix.ARPA From: bridger@Rand-Unix.ARPA Newsgroups: net.micro.cpm Subject: Copying files containing 'holes' Message-ID: <12376@sri-arpa.UUCP> Date: Tue, 25-Sep-84 16:13:30 EDT Article-I.D.: sri-arpa.12376 Posted: Tue Sep 25 16:13:30 1984 Date-Received: Sun, 30-Sep-84 00:47:14 EDT Lines: 22 From: Bridger MitchellUnder CP/M 2.2,..., files written by random access may contain 'holes'-- logical data records that have never been written. A number of utilities don't seem to handle this situation well. PIP copies only at most some of the written records, missing those in higher directory extents. SD reports 'virtual' file size -- the number of blocks (in Kbytes) required if the file consisted entirely of written records. It's easy to get multi-megabyte sizes reported. What 'should' a well-behaved utility do -- i.e. what's the most useful filesize report, and which records should be copied? On first thought, it seems that the size should be number of *allocated* blocks (in Kbytes) and the copy should consist of exactly those blocks, except that in the final block only the records <= last record of file should be copied. Have other utilities already worked this out? --bridger