At 6:10 PM -0500 12/7/2009, D. Finnigan wrote: >On Mon, 7 Dec 2009 17:54:40 -0500, Dan <[email protected]> wrote: >> At 5:19 PM -0500 12/7/2009, D. Finnigan wrote: >>>On Mon, 7 Dec 2009 17:14:10 -0500, Dan <[email protected]> wrote: >>> > Did the byte-count remain constant? No data transfer errors? You >>>> checked that? >>> >>>There shouldn't have been any, otherwise the data checksums wouldn't >have >>>matched and the Finder would have flagged the copy operation as having >>>failed. >> >> What data checksums? Finder doesn't do any checking. > >Then how does the Finder tell if a copy was successful or not?
Define "successful". All Finder knows is that the underlying file copy primitive didn't return a fatal i/o error. If the disk doesn't complain with a hard i/o error, Finder will happily copy corrupted blocks from point a to b. There just is no crc or checksum applied to the actual file data. That's why, for example, Apple recently implemented special signing for applications. Prior to that, there was no way to tell if an app had been corrupted or hacked, unless it crashed or spazzed. - Dan. -- - Psychoceramic Emeritus; South Jersey, USA, Earth. -- ----- You received this message because you are a member of the Vintage Macs group. The list FAQ is at http://lowendmac.com/lists/vintagemacs.shtml and our netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml To post to this group, send email to [email protected] To leave this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/vintage-macs Support for older Macs: http://lowendmac.com/services/
