Re: Disassembling an FST: Retort

[brian.hammack@rook.wa.com (Brian Hammack)]

 Antoine raised the cup and toasted:

 AV<| Please let me tell you a story. The story of the HFS FST (I think
    | I did it before).

Nice story!  :)

    | - the FST is bugged. Thanks for us, some guys patched it.

I commented to someone in CSA2 the other day that Brutal Deluxe should
put out the improved System as a package, as opposed to someone's
suggestion that BD make a program that patches a bunch of stuff, so
that things like the HFS FST are already patched and reliable.

 AV<| They lived happily ever after (no child named HFS+)

Which brings me to my question, which no one in CSA2 has responded to,
of how feasable or possible an HFS+ FST would be to write.  Personally
I'd prefer a ProDOS+ since I don't use HFS for more than storage.

 AV<| The 32mb limit must be broken,

Yes!!!

    | The 16mb may remain (have any interest in a bigger size for a
    | limit of 8mb of ram?)

I'd say there's interest.  This is the reason why I have 8mb and not
higher (I have two 4mb cards in a RamKeeper); I don't like being FORCED
to use whatever ram I have above that 8mb for a ramdisk or for nothing
at all.  Is there actually a way to break the usable-8mb barrier?

    | The length of filenames may be up to 31 characters long
    | The size of a block may remain at 512b
    | The number of logical blocks may be larger than 64k

Fine by me.  How about the number of files in a directory, can this be
made to exceed 128?  (Maybe I should say "reliably exceed 128"; in my
experience more than that number, although permissible, is unreliable.)

                                                << mushroom >>

 * 2qwk! 2.04 * You find out who your friends are after that first breakdown.