Home Page Forums MAME MAME New Fidelity chess modules

http://www.schach-computer.info/wiki/images/0/09/Fidelity_Super_9_Chess_Challenger_PCB.jpg

In above pic, the socketed chip next to the speech chip: The speech ROM wasn't dumped? I'll assume they're same as the other ones by Fidelity.

And the CB9 ROM(bottom-right chip I assume), was it dumped from the chesscomputer PCB, or from the CB9 module?

I guess your assumption is ok, the ROMs I've sent are all that I got.

From the PCB, but I also have a dump of the original CB9 module and both are exactly the same.

Many thanks to 'hap' for implementing the 'Super 9' in the Fidelity driver!

I've just sent a few more ROMs for Fidelity chess computers to the MAME developers email address,
just in case anyone may be interested to create new drivers ...

Franz

BTW, for chess players here's my new CB-Fidelity package (without ROMs!):
http://www29.zippyshare.com/v/65ziaEeg/file.html

The new 'Super 9' and 'Elite Avantgarde V9' are already included -
you can find the necessary ROMs at the usual place ...

Franz

Thanks for the support of the real V9 ROM.

You're welcome!

The V9 was easy to implement, I just had to copy and modify a few lines from the V7.
For really new modules (as e.g. the Super 9) I can write the code for supporting chess pieces, but I can't create a new driver from the scratch (I've just too little knowledge of hardware and MAME internals) - for this we need indeed a true MAME expert like 'hap'!

Franz

The new Fidelity A/S (Budapest & Glasgow) is waiting in the wings ...

Hi,

from a friend I've got a modified ROM for the Sensory Chess Challenger (SC9), it is from a tuned (8MHz) machine.
It is indeed very similar to the version implemented in MAME (by 'hap'), it has the same size and the same ROM addresses, and essentially it's working.

There's only one big problem:
it only responds to mouseclicks on the 8th row of the chessboard (a8-h8), all other fields are simply ignored.

I've now already tried to solve this problem for many days, but unfortunately without success. The current routine 'sc9_input_r' in the SC9 driver is

and I've changed this in many different ways, but nothing worked.

Has anyone any ideas what else I could do (or try) to solve this problem?
Is there any method to find out what exactly the device expects to get from from the driver, when you click on any sensor field of the chessboard?
Or are there any other places in the driver that could be the reason for this problem?

Regards,
Franz

Ok, forget my previous post.

I've now finally found the solution for this problem, and I found it myself!

"Don't rely on the help of others" is indeed a good motto - especially here in this forum.

Franz

Insulting the people who wrote the software you use probably isn't though.