Home Page Forums MAME MAME SVN builds - new driver flood

Check the region sizes in ng_aes.c - if you overflow one it'll crash very much like that.

Ah good, got them all working now. Silly me was only looking at the size of the 68k CPU region :P

We should make "official" XML packs available for the "good" games supported (in favour of the [at least in the past] much discussed static gamelists in the source). Just like Pugsy does for cheats.

Can the XML also be seperated from the rom data? So if you wanna play tpgolf you got the tpgolf.xml in your aes folder and a tpgolf.zip beside where the data can be found.

Would also avoid the distribution of the "official" XMLs with the "illegal" romdata in one archive.

Mizapf bypassed a lot more of the core than I was expecting, so we may or may not get standard behavior with .rpks. Separation from the ROM data doesn't seem possible - at best you could put the xmls in the AES.zip with the *other* illegal rom data.

A little more fun - I added preliminary ATAPI and GD-ROM drive emulation (including sector DMA) and we get the full startup animation with the dot making the letters bounce and then this.

Guess it's time to figure out how controllers work. Or at least how to cheat the NVRAM so it thinks the time's been set ;-)

yeah, I think xml could be added to Wiki (they only include crc info). Maybe together with a clrmame dat to rebuild the sets from MAME romsets.

static gamelists are parallel to xml and should not be mixed. static gamelists, if ever included, will be a coexisting alternative to the capability of loading any piece of software. the latter, in neogeo, would be impossible without xml layouts


I would vote no, but I would agree with the majority. the point of xml support is to replace older headered formats with something cleaner: a zip containing separate chip dumps + xml layout. Neogeo is indeed a borderline case, because MAME already allows to have good dumps, but splitting xml from other data could create problems when we shall work with other systems.


who cares if official xmls are spread with illegal data? the important thing is to stress that official website of the project ONLY distributes the legal xml data and no copyrighted items


what do you mean for "standard behavior"?


overall, great news about the neogeocd!

By standard behavior I mean things like "roms/folder == roms/folder.zip" and that sort of thing. Also, there is good news about the neogeocd? My post above is Dreamcast

I should have read more carefully

can I restate: great news about dreamcast!

I have some questions about the new system craft: for what i know is a homebrew system thats was made with a microcontroller (atmel 8-bit) and adaptations to plug with outputs to show a demo in last year...
1-the driver and dumps was made with approvementnt of creator? did he collaborate with MESS project or craft driver?
2-in the website of lft, we can download the firmware of the system, but why MESS use a bin version of it, unless the original eeprom.raw and flash.hex?...
3-why thats marked as a console?
thanks

1) lft has no involvement and he freely gives away information on the project. Also, his new demo is on completely different hardware.
2) Emulators need binaries, not hex files.
3) Since it's a bare microcontroller you could claim it's both a computer and a console. Or neither. Since in reality MESS only cares about that flag to know if the device has a keyboard and needs the annoying mode switch enabled calling it a console is correct.