Megalextoria
Retro computing and gaming, sci-fi books, tv and movies and other geeky stuff.

Home » Archive » net.micro.cpm » Copying files containing 'holes'
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Copying files containing 'holes' [message #80558] Mon, 03 June 2013 23:51 Go to previous message
bridger is currently offline  bridger
Messages: 19
Registered: May 2013
Karma:
Junior Member
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 Mitchell 

Under 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
[Message index]
 
Read Message
Read Message
Previous Topic: dBase II query...
Next Topic: Questions on CP/M Plus
Goto Forum:
  

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 01 23:54:18 EDT 2022

Total time taken to generate the page: 0.00247 seconds