[HECnet] Re: Announcing the Open SIMH project

The addition of metadata to existing disk containers can be simply disabled if a:       SET NOAUTOSIZE Command exists in the configuration file you use for a particular simulator execution, OR if you always want it disabled, that command can be placed in a simh.ini file in your home directory. If you want to determine if metadata exists on disk container files you have, this command will display the details:          sim> DISKINFO *.dsk If you’ve got containers that may or may not have previously had metadata added and you want to remove that meta data, the following command will do that:          sim> ZAP *.dsk The ZAP command will only remove metadata that was added by the code in a simulator, and otherwise leave containers without metadata alone. *From:* Mark J. Blair &lt;nf6x(a)nf6x.net&gt; *Sent:* Saturday, June 4, 2022 7:09 PM *To:* The Hobbyist DECnet mailing list &lt;hecnet(a)lists.dfupdate.se&gt; *Subject:* [HECnet] Re: Announcing the Open SIMH project I first learned of the new disk file metadata in December of 2021, when heated discussions about it occurred in a forum I was part of. It appears to me that the change was introduced in April of 2020 in this commit: https://github.com/simh/simh/commit/049ba3250521f0bc08822088bd023115da030711 <https://github.com/simh/simh/commit/049ba3250521f0bc08822088bd023115da030711> I wrote a little utility in Python to search my images for the presence of the new metadata, and add/edit/remove the metadata as desired: https://gitlab.com/NF6X_Retrocomputing/simh-diskinfo <https://gitlab.com/NF6X_Retrocomputing/simh-diskinfo> I stopped thinking about the matter not long after that, I have not pulled fresh simh code from the repository in a while, and I do not know whether my utility code is still compatible with later versions of the pre-fork simh code. My usually-on VAX emulations are running on simh code from back in December. I was surprised to see how this all escalated, since I've been living under a virtual rock for a while. I assume that I'll be switching to the new open-simh fork next time simh activities move to my front burner, because the license changes which apparently prompted the fork look rather distasteful to me. I'm interested in seeing if the metadata stuff gets any changes in the future in open-simh. -- Mark J. Blair &lt;nf6x(a)nf6x.net <mailto:nf6x@nf6x.net>> Blog: https://www.nf6x.net <https://www.nf6x.net> Git: https://gitlab.com/users/NF6X/groups <https://gitlab.com/users/NF6X/groups> HECnet:  DOGPAK::MBLAIR _______________________________________________ HECnet mailing list -- hecnet(a)lists.dfupdate.se To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se