Home Page Forums MAME MAME SVN builds - new driver flood

we might end up with the first instance of MESS emulating itself... and on mac!

In svn rev6190, I fixed the crash in cdtv. Now we can once more load CHDs to cdtv. (thanks Anna for providing a test case )

However, I think there is something wrong going on with the cdda (probably on the MAME side): the cdda can be set from the cdrom by using cdda_set_from_cdrom, but this function requires the cdrom to be a 'void' entry rather than a device (like cdroms are in MESS) and this was causing the error I fixed: the cdda.c code was not finding the correct cdda device when cdda_set_from_cdrom was called.
This is probably due to the fact that in MAME cdda_set_from_cdrom is called with a second parameter from SCSI elements and SCSI is not a device yet in MAME.

While the current code in MESS seems to work, there are other functions which expect a void parameter and receive a device one.
Hence, I fear there could be other problems (hopefully not affecting anything visible) which will only be fixed with a device-ification of SCSI!!

That's the default gamma for the Mac II. Seriously. I think you can change it in one of the control panels.

eta: that change is somewhere in the neighborhood of horrifically wrong. You should've just fixed cdda_from_cdrom.

Great fix, etabeta78

SVN r6190
cdtv driver

fixing cdda_from_cdrom requires changes in the way scsi works in drivers using that call (affecting among others gdrom.c and cubocd32.c). changes to scsi to pass a device in those two drivers might require a full device-ification of scsi, and hence touching the drivers using it (firebeat, ksys573 and dc among others)

I hope you realize it's not something I could have fixed in half an hour, like adding a tag in the interface. proper fix is in my (growing) todo list.

Given that I clearly documented the reason of the ghastly hack (so that the system will work in 0.135 but we know the fix is not good), I think we can live with it until I have some more spare time

That's fair. I've deliberately avoided converting all of that to devices because MAME's irritating "startup order is not guaranteed" policy means we could easily end up with a situation where sometimes it can find the media and sometimes not.

Can't you just use device_delay_init() to guarantee that another device has been started?

Does that actually work? I vaguely recall someone tried to use it once and ended up quitting the scene ;-)

If it doesn't you can always fix it :P

Nope, "button 3" on more recent controllers just presses 1 & 2 simultaneously There IS no button 3...