Neue romdump von Berger: GGM Morphy modul =)
http://www.spacious-mind.com/html/morphy_module.html

So ist das in der Computerwelt. Kaum bringt unser Franz eine neue Version raus, ist sie schon wieder alt... lach

__________________
Mein Profil beim ICCF (International Correspondence Chess Federation)
https://www.iccf.com/player?id=89948&tab=3

If you prefer, I can stop supporting MAME so that the latest version of CB-Emu doesn't get outdated.

No, just don't. Then our Franz would have nothing more to do in his retirement - and we could no longer look forward to new versions of our beloved board computers.

I don't often write here in the forum, but now it's time to say a big thank you to berger, hap and Franz for their tireless work. Unfortunately, I don't have much time left to play chess. Therefore I am very grateful to you, that you beautify my last time with new versions.

Many thanks, hap!
¡Muchas gracias, berger!
Vielen Dank, Franz!

Don't worry, I was just joking!

Thanks for the acknowledgement anyway.There are other contributors too, such as bataais and Sean Riddle. But as long as the master hap is involved in MAME, you can be sure that Franz will still have to update CB-Emu. xD LOL

Best,
Gerardo "berger"

yep, I am curious which one of our triumvirat will be the first to give up.

So, jetzt gibt's also schon nach 2 Tagen die nächste Version.

Eigentlich wollte ich nur ein kleines Update machen (für das neue Morphy-Modul wären ja nur ein paar Zusatzdateien nötig), aber dann wollte ich für diese GGM-Modell auch das jeweils gewählte Modul im Artwork anzeigen, wie ich es auch schon bei anderen Geräten getan habe (sind jetzt ja doch schon eine ganze Menge an GGM-Modulen).

Also gleiche Methode wie beim ARB (für die Sargon-Versionen 2.5 und 4.0) - hat aber nicht funktioniert.
Dann habe ich mit Entsetzen festgestellt, daß auch beim ARB die Sargon-Version jetzt nicht mehr angezeigt wird, was in MAME 0.215 damals noch problemlos geklappt hat - ist bisher aber anscheinend niemandem aufgefallen, mir auch nicht.
Da muß sich also bis MAME 0.220 schon wieder intern etwas geändert haben, also mußte ich wieder erst einmal die Ursache für dieses Problem finden, worin ich zum Glück recht begabt bin.
Nun gut, das Problem ist wieder behoben, und damit wird jetzt auch im GGM-Artwork das jeweils geladene Modul angezeigt.

Die neue CB-Emu-Version ist bereits online - vielen Dank an Berger und 'hap' für das neue Morphy-Modul.

Grüße,
Franz

@hap,

after starting the ARB SArgon 2.5 you have to click on [New Game] before you can start to play (without it not even the board is usable).
In MessChess the plugin does this job by sending a send_input(":IN.0", 0x80, 1) to the device.
Can this also be automated for MessExtra, i.e. without using a plugin?

I've searched through the MAME drivers and found commands for sending a value to an ioport, so I tried the following command in machine_reset()
of the ave_arb driver: ioport("IN.0")->write(1,0x80)
It compiled without errors, but unfortunately it doesn't seem to do anything!?

Is this command wrong? Is there any other command to simulate this keypress (i.e. to activate this ioport) in the driver, or is this not possible at all?

Regards,
Franz

I did it in this driver:
https://github.com/mamedev/mame/blob...s/k28.cpp#L110
https://github.com/mamedev/mame/blob...s/k28.cpp#L186

Ah, yes I remember now that I've done something like this in a few drivers long time ago in the first CB-Emu versions (in MAME 0.175).
But this method of manipulating m_inputs[i]->read() is quite complicated - I believe I've asked you at that time, why there isn't an easy method to send values to an ioport, and IIRC your answer was, that this would make cheating easy, and so the MAME team decided to not implement it.

Ok, I'll try it, but I'm not sure if I'll get this method working again after so many years ...

Yep, I got it working!

But your method with this m_onbutton_timer requires a bit too much code IMO, so I've just used a boolean variable 'arbinit', which I set to 'true' (only for the Sargon 2.5) in machine_reset(), and then I use the following code in input_r():
It seems to work correctly, since it's also only executed once after each reset.

BTW, is it normal, that the RESET button for the ARB and ARBV2 doesn't seem to do anything?