Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!uwmcsd1!ig!jade!ucbvax!RAND-UNIX.ARPA!bridger%rcc
From: bridger%rcc@RAND-UNIX.ARPA (Bridger Mitchell)
Newsgroups: comp.os.cpm
Subject: Re: PIPing random files
Message-ID: <8711301704.AA21747@newton.arpa>
Date: Mon, 30-Nov-87 12:04:45 EST
Article-I.D.: newton.8711301704.AA21747
Posted: Mon Nov 30 12:04:45 1987
Date-Received: Thu, 3-Dec-87 04:55:57 EST
References: <8711261736.AA12340@ngp.utexas.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14

Copying randomly-written sparse CP/M files is considerably more
involved than the sequential read/sequential write operation used
by PIP and nearly every other file copy utility; it is especially
tricky when the source and destination have different logical block
sizes.  When I wrote DATSWEEP for DateStamper I queried the list
about interest in adding that capability; no one expressed interest.
I know know of no general-purpose utility that can do it correctly.

Your best bet is probably to use the database program that created
the sparse file to copy it; I expect that all such programs contain an
internal copy command that will work (e.g. for dbase II, "copy to
").

--bridger mitchell