"COMPUTING" is output to "0.7.11", it's not necessary to read it from RAM.

Thanks!

I guess this is a number in the SVG file (?), so of course this can only know the one who created this file.
I'm now using the following line in the plugin, I hope this is correct (?) - at least it seems to work:
computing = (machine: outputs():get_value("0.7.11") ~= 0x00)

BTW, I saw that you've already implemented the automatic layout switching for the GGM modules - great job!

Yeah, GGM automatic keypad overlay switch works well =)

SVG details can be seen by anyone. Open the file in Inkscape, then click on one of the objects, the output ID is in the Title (see Object menu -> Object Properties). This goes for ssystem3, savant, mchess, ccmk5. And other games too such as Nintendo Game & Watch.

Yes, this may be true, but only for someone who has experience with such SVG files.
In my very long time working with computers I've not used or needed this SVG format yet.

One other question:
The Steinitz module also existed as 4MHz and even 20MHz version, and it has been requested here to implement these versions, too.
Of course I could add a completely new machine for it (with the ROM integrated), but maybe it's also possible to just add these 2 versions in the XML file (e.g. with feature name="mhz" value="4" and feature name="mhz" value="20" or something like that)?
Could this be done, and what would I have to add to the GGM driver to change the CPU speed depending on this "mhz" feature?
If it's not possible, then I'll create an extra machine ...

Or you could just add a CPU frequency switch to the driver itself, similar to Novag Super Expert.

I did look around for the "Mega-4", but can't find any evidence that it was ever released.
More information about this machine: http://spacious-mind.com/html/great_...ine_4_mhz.html
"So the question needs to be asked was the Destiny MEGA-4 GGM ever released? Where there any made at all? Most sources say no."

The 20MHz version by SteveUK(?) probably has ROM modifications for the changed timing.

Well, that would of course be possible, but then you could also change the CPU frequency for the other 2 modules (Sargon 2.5 and Sandy), but they go crazy with these higer speed. So that's not a good idea.
I don't think this is needed, because I've already tried 20MHz for the CPU on the Steinitz module (with the VIA6522 frequency unchanged at 2MHz), and everything worked fine - just the clock is running a little bit faster (but only a few %).

Ok, then try it the same way I did the extra RAM feature.
Name the parameter "overclock20" or something, then in the cartridge load function do: if (image.get_feature("overclock20")), and set_unscaled_clock.

Or if you want to do a cleaner implementation, add a mhz param like you said. Convert string to unsigned int and multiply by 1million.

Aah, that's exactly what I needed to know - many thanks!

Ok, I got the Steinitz 4MHz and 20MHz working!

I've now checked the clock with a stopwatch, and both versions are running 10% faster, so I've also changed the line VIA6522(config, m_via, 2000000) to VIA6522(config, m_via, 1800000) and then the clocks are ok again - but of course now 10% slower for Sargon 2.5 and Sandy.

So I've one question again:
can I also change this VIA6522 to 1800000 in the cartridge load function with any command?
Just adding VIA6522(config, m_via, 1800000) there doesn't work.

Edit: Ok, I just found a command m_via->set_clock(), I guess this might work - I'll test it ...

Edit2: Yep, that's indeed working! Hartmut kann sich freuen ...

Hallo Franz...

Nicht nur Hartmut

Viele Grüße
Mark 1