Hello. I wanted to read picotron_manual.txt directly from inside the OS and attach an icon to it so it'd look like the default readme.txt. Somehow, attaching an icon with the help of about.p64 didn't exactly work as planned: the file wouldn't open anymore.

So, I dug around and I noticed that fetch-ing the file's content would return the metadata as expected but not the file's content, returning nil instead. Looking in the file's header I noticed something weird: where readme.txt was saved with the marker pod_format="raw", the manual was saved just as a pod. I highly suspect the OS is then unable to figure that it could open the file as a text file without the proper marker. And indeed, manually fixing the file metadata to replace pod with pod_format="raw" fixes the problem.

So here's the minimal repro scenario:

1. Open your Picotron drive
2. Create a text file with some content in it with the Host OS.
3. Open the file's properties in Picotron
4. Add an icon to it and save.
5. Double click the file (or open it with the code editor)
6. (Bonus) Introspecting the file through the Host OS will reveal that the marker is not pod_format

I'm not sure if it's a problem coming from about.p64 or store_metadata because at this point, it only got a file without metadata before applying the icon, but I think something might still be related to one of those.

Have a nice day!