Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!dlyons
From: dlyons@Apple.COM (David Lyons)
Newsgroups: comp.sys.apple
Subject: Re: GS/OS 3.O & ICON INFO
Message-ID: <34331@apple.Apple.COM>
Date: 25 Aug 89 22:38:46 GMT
References: <698@mountn.dec.com>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 48

In article <698@mountn.dec.com> shatara@memit.dec.com (Chris Shatara) writes:
>[In Finder 1.3 Icon Info window for a folder]  I asked for the 
>information for a folder I had (which contained six files) and clicked on
>the calc idon and got the following information:
>
>    SIZE:  126,524 bytes  643K on disk
>
>This seems way out of whack with what I see when I do the same thing on my 
>other folders.  I would expect the numbers to be about the same.  I then 
>got information for each of the files in the folder individually and I got
>the following:
>
>    file 1      577,536 bytes    567k on disk
>    file 2       65,496 bytes     65k on disk
>    file 3        4,354 bytes      5k on disk
>    file 4        2,077 bytes      3k on disk
>    file 5        1,041 bytes      2k on disk
>    file 6          158 bytes      1k on disk
>
>Can anyone shed some light on this. I thought i knew what this feature
>did but with this result I'm not quite sure.

My goodness...looks like a bug.  The total is so *close* to being off by
an exact multiple of 65536 ($10000) bytes, that it looks like the Finder
is ignoring the high word of the file size.  (Could the invisible Finder.Data
file in your folder account for the missing 149 bytes?)

Apparently, if all the files in a folder are smaller than 65536 bytes, the
Finder will compute the correct "bytes used."  There doesn't seem to be
any problem with "k on disk," so you can still pay attention to that to
get a rough idea of whether a folder is going to fit when you try to copy it
onto another disk, for example.

I'll report this to the FinderDudes.

Note that you *can* legitimately have files with larger byte-sizes than
their "k on disk" would indicate, at least on ProDOS disks.  This is
because ProDOS files can be "sparse"--long sequences of "zero" bytes 
don't take up blocks.

 --Dave Lyons, Apple Computer, Inc.          |   DAL Systems
   AppleLink--Apple Edition: DAVE.LYONS      |   P.O. Box 875
   AppleLink--Personal Edition: Dave Lyons   |   Cupertino, CA 95015-0875
   GEnie: D.LYONS2 or DAVE.LYONS         CompuServe: 72177,3233
   Internet/BITNET:  dlyons@apple.com    UUCP:  ...!ames!apple!dlyons

   My opinions are my own, not Apple's.