> > At 13:36 4/28/96, Bill Middleton wrote: > >If you can use the new PowerTools extensions, try something like > >this: [...] > > > >Hopefully faster than asking the finder. > > And produces a smaller number in any file whose resource fork hasn't been > compacted <and smaller by the per file, per type and per resource overhead > and the sizes of the names of the named resources, probably, too>. Which > number is wanted (bytes in resource fork vs total bytes in the active > resources data) is unclear, but more likely it's the former, which the > excellent script above doesn't produce. Aside from the holes, the > overheads are computable, but it hardly seems reasonable to do so. The above is a bit unclear, would you care to reword for those of us who are interested? Indeed, the ask-finder script seems to return a slightly larger number. GetResourceSizeOnDisk() supposedly returns the exact size of the resource as it exists on the disk, not in memory. From the standpoint of the original question, this seems, imho, more appropriate. Bill