Greetings
This is fairly typical of the FAT16 file system. This is basically what is happening:
Your HD is formatted with FAT16, and this is what that means: On your HD, during a low level format, the disk is assigned tracks, and each of these tracks are split up into sectors (typically 512 bytes long). Then the disk is formatted by the Operating Sytem with it's filing system. The sectors are then grouped into Clusters.
With FAT 16, the cluster sizes are as such (this may be a little wrong, I am doing this from a very shaky memory) :
<PRE CLASS="FIXEDTEXT">
Drive Size FAT Type Sectors Cluster
(logical volume) Per Cluster Size
----------------- -------- ----------- -------
0 MB - 15 MB 12-bit 8 4K
16 MB - 31 MB 16-bit 1 512 bytes
32 MB - 63 MB 16-bit 2 1K
64 MB - 127 MB 16-bit 4 2K
128 MB - 255 MB 16-bit 8 4K
256 MB - 511 MB 16-bit 16 8K
512 MB - 1023 MB 16-bit 32 16K
1024 MB - 2048 MB 16-bit 64 32K </PRE>
So, as you can see, the larger you partition is, the larger the sector size is. Now, WinOS Filing systems can only assign ONE file per Sector. So, if you had a 1K file on a 2 Gig partition, then it will take up 32K of HD space. Similiarly, if you had a 33K file, it will take up 1 whole cluster and 1K of the next cluster, so, in total, it will be using 64K of HD space.
The way to save space is to either have smaller partitions or smaller clusters. The only way to have smaller clusters is to use FAT32 (which is unreadable by NT4, well, without the FAT32 reader by
www.sysinternals.com) or to use NTFS, where on multiple Gig drives you can have clusters as small as 512 bytes (using the compression).
So, that is why your files of 1K are taking up to 32K of space....
Hope this helps
------------------
Reuel Miller
Windows NT Moderator (yes, that does make me biased

)
rmiller@xperts.co.za Every morning is the dawn of a new error...
[This message has been edited by Reuel Miller (edited 11-20-1999).]