You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently only the filename of a disk image attached is stored in the process structure. If an image was loaded from a subdirectory, it is never possible to restore it after a freeze.
In addition hyppo could also store some UID of the sd card, so the entries can be invalidated if the wrong disk is inserted. Or better not?
Perhaps it is also possible to just store disk UID plus some pointer onto the disk? Not sure if this is feasible with FAT. Problem with path storage: those can get quite long...
In theory at FAT level, directory can be identified with only a single number: the starting cluster of the given directory (if it's the root directory, the starting cluster simply the cluster number of the start of the root directory but there is nothing special in that on FAT32 - though it is on FAT12/16, but it's not scope here fortunately). There is not even needed to store the textual representation of the full path, as every directory should have '..' entries to be followed to query the path then if needed. The disadvantage of this, if someone wants to see the path, not only make it working. Then the mentioned '..' following should be done to get back the path (in reversed order) till hitting the root directory. I am not sure though, how HYPPO handles these things ...
Currently only the filename of a disk image attached is stored in the process structure. If an image was loaded from a subdirectory, it is never possible to restore it after a freeze.
In addition hyppo could also store some UID of the sd card, so the entries can be invalidated if the wrong disk is inserted. Or better not?
Related FREEZER issues:
The text was updated successfully, but these errors were encountered: