I've written a backup system for my digital photos that copies a directory tree of files into DVD sized directories to be burned and am adding up file sizes as I go to determine where to stop and start on a new disk. The problem I'm running into is that the file size seems not to be exactly equivalent to the size on the disk.
I'm aiming for a size on disk of 4.37 GB or less since undersize is ok, but oversize requires the manual adjustments I wish to avoid. lnDisksize < 4800000000 is the cutoff prior to a copy is the litmus that has generated the results below Here are some sample "size on disk" coming from win explorer properties windows 4.26 GB (4,577,214,464 bytes) 4.40 GB (4,725,853,231 bytes) 4.37 GB (4,697,579,520 bytes) 4.37 GB (4,702,322,688 bytes) I suppose I could work from diskspace() rather than file size addition. Are there other quick and more accurate ways of getting the "size on disk" of a set of subdirectories programmatically in foxpro? I'm presently working in fox 6. Best, Steven Holt Steven Holt http://stockpix.com (541) 267-2803 [EMAIL PROTECTED] 93559 Easy Creek Ln. Coos Bay, OR 97420 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
