"My own filesystem" what should I take into accoun

[neochrome32]

your right, if i had to do it that way, the space would have to be NOT an issue! also, would have to create my own clustering systems too, basically at the end of each 512bytes there is a 4byte chunk pointer?

[Ttelmah]

This is all up to you....

This is where the complexity comes in a file system.

Fat as it stands, allows you to have variable length files, and find where they are in the huge 'data block', that is a partition. Then allowing the files to grow and shrink if required. How much of this you actually 'need' is down to the nature of what you are doing. There are ways of 'finding things' that are faster (the hash is one), but these have costs like needing to pre-allocate enough storage for the whole table.

You 'pays your money and takes your choice'.

The big advantages of FAT, is that it is basically pre-written, and then the files are standardised so can be read/written on other systems,

[neochrome32]

its a shame i may have to abandon Fat32 if there is a huge price tag on it, BUUUT i got most of what i need working.

i wrote a basic crummy MKDIR function that appears to work well enough, and windows doesn't seem to complain.

yeah i noticed that the files could expand, but i cant see how they did it!


Thanks Ttelmah
excellent advice!