Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!bloom-beacon!eru!hagbard!sunic!news.funet.fi!uwasa.fi!ts From: ts@uwasa.fi (Timo Salmi LASK) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: **** WANTED **** BINARY FILE COPY PROGRAM Message-ID: <1990Sep21.155919.15602@uwasa.fi> Date: 21 Sep 90 15:59:19 GMT References: <90263.114424POTELLE@MAINE.BITNET> <1990Sep21.071337.10847@uwasa.fi> <6177@uceng.UC.EDU> Organization: University of Vaasa Lines: 25 In article <6177@uceng.UC.EDU> dsims@uceng.UC.EDU (david l sims) writes: >ts@uwasa.fi (Timo Salmi LASK) writes: >>In article <90263.114424POTELLE@MAINE.BITNET> POTELLE@MAINE.BITNET (John A. Potelle) writes: >>>This program should be able to copy PARTS of files, given a starting >>>relative address within the source file and a length. >>>Example of a possible command line syntax: >>>chopcopy [-s100 [-l360]] > >> BTW writing a slow program that does what you want should be >>trivial. The trick is to make it a relatively fast one. : >For those who aren't sure how to buffer their program, one solution is >to perform read's and write's in, say, 10000 byte blocks, instead of the >usual and simple method of reading and writing one character at a time. My apologies, since I'm again drifting outside the subjects of c.b.i.p.d., but if anyone is interested in knowing more about buffering, I suggest taking a look at O'Brien, Turbo Pascal, The Complete Reference. It includes a very useful, even if complicated, method for buffering binary file I/O. ................................................................... Prof. Timo Salmi (Moderating at anon. ftp site 128.214.12.3) School of Business Studies, University of Vaasa, SF-65101, Finland Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun