@artandtechnic well done, and congrats!
Conversation
Notices
-
Foone🏳️⚧️ (foone@digipres.club)'s status on Wednesday, 18-Dec-2024 11:15:39 JST Foone🏳️⚧️
-
Denis Warburton (artandtechnic@digipres.club)'s status on Wednesday, 18-Dec-2024 11:15:43 JST Denis Warburton
After handling a few tasks elsewhere, I came back and discovered the problem: an off-by-one error in the `snprintf` that generated the filename. Instead of generating filenames that were 16 bytes long, we were only writing 15 ASCII characters… and a null byte ($00).
Since I wasn’t padding out the filenames with $A0 bytes, like you’re supposed to do when filenames are less than 16 bytes… the C64/emulator... responded to the malformed filenames.
Much better. Now to give actual names, etc.
-
Denis Warburton (artandtechnic@digipres.club)'s status on Wednesday, 18-Dec-2024 11:15:43 JST Denis Warburton
With the exception of the very first file in the list, I’ve restored the original names for every file, using the directory data found in the “garbage” of various blocks. I’ve given the first file the name “unknown,” as there’s nothing on the disk that tells me what it is, and frankly I’m not sure what it’s supposed to make either. 😂
At this point, the D64 image of the disk is fully repaired. SUCCESS!! 🎉🥳
-
Denis Warburton (artandtechnic@digipres.club)'s status on Wednesday, 18-Dec-2024 11:15:44 JST Denis Warburton
In the continuing saga of the 1986 recipe disk…
The good news is that the emulated Commodore 64 can read the reconstructed disk directory (left screengrab). The bad news is that there’s something clearly wrong with some aspect of how I did it. 😂😢
Curiously, the “attach disk” file preview for VICE shows a less problematic view of the disk directory.
-