teufelchen1 / fatx-on-a-snake Goto Github PK

ATM a lot of errors are handled like in Golang:
ret, err = func()
which should be replaced with python raise Exception

Its not really clear how DirectoryEntryLists get terminated. For one its done by a 0xFF entry thats for sure but given empty XMU images, 0x00 might also be a valid termination.

Currently I use some asserts which don't make a lot of sense as they might fail by simply using the tool with bad parameters - if they fail, they don't provide a proper error message.

Currently only the blocks.py is automated tested. Thats good but not enough.

Atm only files that fit in one cluster(32*512Bytes, 16kb on typical FATX) can be viewed or dumped.

When exporting and re-importing a FATX filesystem, some metadata from the superblock will be lost.
On XMUs this contains the nickname of the device.

Such data should be exportable, and re-importable.

Somewhat related to this issue, additional options should potentially be investigated, like preserving accurate flags for each file entry, or even FAT allocations (offsets of files), list of broken sectors etc., ... (could be realized by exporting a python script which uses the FATX-on-a-snake API to re-add all the file contents again - so it would be a human readable script with one-line per file); however, this issue is primarily about the superblock.

Currently only standard size partitions are confirmed to work. However, its possible that it will also work with larger partitions, this has to be confirmed

@JayFoxRox suggested to use virtual file interfaces via IO Interface

Hello! 👋

I'm constantly annoyed by the amateur print() debugging and logging. One should make use of the logging module and implement good logging of events, warnings, debug, info and more.

Since python-fuse is a thing, it would be cool to utilise it one day!

I'd like to see CLI options for -sector-size and -cluster-size (or, when parameterized differently: -sectors-per-cluster).

This is important for supporting XMUs and Chihiro DIMM boards.