Machine selector generates many SRAM file not found messages about openmsx HOT 4 CLOSED

Yes, this happens because the machines are actually instantiated. A similar thing is that for the extensions in some cases large files are created (e.g. empty HD images). But that doesn't give a pop-up I guess.

@m9710797 wouldn't it be better to make something to avoid this when we only want to instantiate for some queries?

from openmsx.

I agree. I'll put this on my TODO list.

from openmsx.

With a one-line change I could suppress the messages (revision 92a8dca).
However the SRAM files (typically for the RTC) and HD images are still being created.

• On the one hand that's fine. That also tests that those files really can be created (e.g. the directory is writable). And SRAM files don't take much space.
• On the other hand, empty HD images are also created. These are 100MB. Nowadays that's not a whole lot, but also not negligible.

from openmsx.

Messages were previously silenced in 92a8dca, and now the “SRAM file not found, assuming blank content” message has also been removed altogether in f1bbc93.

from openmsx.