Conversation
TomHarte
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Some titles now work, some don't; as with most of these Thomson formats the documentation is obscure even before the language barrier.
Some discussion in https://forum.system-cfg.com/viewtopic.php?f=6&t=15013&hilit=sap+crc&sid=6d054b10d3897a20e480c130987b1818 took me to https://github.com/Samuel-DEVULDER/Thomson-Projects/blob/97fab1b2aa2145473111bb4d63caebdc418b0a53/sapfs/libsap.c which might be useful further to read to understand the on-disk structure for Thomson's filing system but wasn't especially helpful when it came to verifying what might be afoot with weird disk images like Renegade's, which just opens with a bunch of sectors containing only 256 copies of the byte 0xe5.