Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!usc!brutus.cs.uiuc.edu!wuarchive!uwm.edu!ux1.cso.uiuc.edu!tank!iitmax!bundalo
From: bundalo@iitmax.IIT.EDU (Predrag S. Bundalo)
Newsgroups: comp.lang.pascal
Subject: Re: Read/WriteBlock procedures in TP 5.x
Summary: Fine, but ...
Keywords: blah
Message-ID: <2994@iitmax.IIT.EDU>
Date: 14 Nov 89 17:31:08 GMT
References: <2960@iitmax.IIT.EDU> <1989Nov14.073916.10338@cs.eur.nl>
Reply-To: bundalo@iitmax.iit.edu (Predrag S. Bundalo)
Organization: Illinois Institute of Technology
Lines: 28

In article <1989Nov14.073916.10338@cs.eur.nl> reino@cs.eur.nl (Reino de Boer) writes:
>bundalo@iitmax.IIT.EDU (Predrag S. Bundalo) writes:
>
>>	I've written a file copier using the above procedures.
>
	I've received numerous explanations ( thanks ! ), but not
	a one solution.  Now I know about the way DOS allocates
	space for files, and clusters, and all that, but I don't
	know how to go about overcoming the problem.  Would truncating
	the file to the right size deallocate the extra space DOS
	conveniently allocated for me?  How does DOS's "copy" program
	work?  I mean how does IT overcome the allocation problem?

	I've also noticed that it (dos's copy program) reads in quite
	a bit before writing.  Anyone know how much?  Is this documented
	in the DOS Technical Reference manual?

	Thanks,

	-Pred
-- 
 ______________________________________________________________________________

  Predrag S. Bundalo                  BITNET:  SysPredrag@IITVax.iit.edu.BITNET 
  Illinois Institute of Technology
  Academic Computing Center           UseNet:  bundalo@iitmax.iit.EDU 
  VAX/VMS and Unix Systems Staff 
  Chicago, Illinois