On 11/17/2000 5:49 PM, "David Oberst" <[EMAIL PROTECTED]> wrote:
> In the "Signatures" file case, it is not just that the unused portion of the
> allocation block has random data. The random data is part of the file (ie.
> it is before the EOF), which is why you see it with BBEdit. BBEdit is NOT,
> as someone said, reading in the whole sector/block, just requesting the data
> up to EOF. The random data would be included if you copied the file to
> another disk, unlike data past EOF in the unused portion of the last
> allocation block.
>
> Presumably Outlook/Entourage requests that files be "grown" in chunks, and
> manages the space as required. The File Manager "SetEOF" and "Allocate"
> calls don't zero out the allocated space, and OE doesn't, presumably for
> performance reasons. If this is an issue for people, perhaps Microsoft
> could zero out unused sections of these files as part of the "Rebuild"
> process?
Yes, growing the file size is slow, so we grow it in chunks so we have to do
it less often. The data left in the file when it's grown is whatever random
junk was on the disk before. And, yes, it's not zeroed for performance
reasons. On a rebuild, the only non-zeroed data you'll get is at the very
end of the file.
Dan
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
