Ahemmm.... let me try to explain this. 3.26 mb is the actual size of the fil. However, your hard disk is separated into smaller sectors and the OS is trying to fit 3.26 mb into many small sectors. As the 3.26 mb is cut into smller chunks, the OS sometimes does not split the chunks to fit perfectly into a sector (for performance reasons) and as such, on disk, the file size is larger (i.e. it takes more than 3.26 mb of disk space to store a 3.26 mb file)...
so whats the point of using sectors? is it so that when loading something for example a 20mb file...it does it part by part, therefore not overloading the oc's memory with the full 20mb
There are lots of reasons - e.g. if the whole disk is one sector and the sector goes bad, you've just lost all your data. However, in the case of a disk with many many sectors, if a sector goes bad, it'd only be that sector + the file which uses the sector.
Python
Forum LeaderThe Royal RAM
Comments
Phew... :idea:
The Royal Ram
The Royal Ram
The Royal Ram
Also, disk management would be very much easier.
:idea: