Home Page Forums MAME MAME SVN builds - new driver flood

Thanks to Curt for enabling this, the Apple II Super Serial Card now can talk to other emulated serial devices, like MESS's built-in generic terminal.

r21022

Basic implementation of software mode of the FM-Towns CD-ROM controller. You can now use CD-ROMs under Windows 95 without Windows locking up. (And no, FF7 is not playable, it requires a Pentium CPU, and it looks like MIDI playback is non-functional).

Playable, but no music, and full-screen doesn't work (no screen updates).






Sonic the Hedgehog CD (PC demo version, running on the FM Towns II HR)

RB, how is the MESS serial terminal connected to a driver?

Robert

For a system that uses a serial chip where our implementation subclasses device_serial_interface (currently the 8250/16(5/6)50, Moto 2681/68681, MOS6551, or Intel 8251) it's mostly a matter of adding an RS232_PORT device (which connects you to the terminal/null modem) and doing a little "wiring".

This commit shows the basic wiring and this one adds the actual terminal and null modem. (The null modem can output to a PTY or TCP socket; it really needs bidirectional which I'll add if Carl doesn't first).

And here's MIDI In working on the C64 (Curt did the actual work, I'm just testing for him).



If someone can point me to some Atari ST MIDI software that works in MESS I can make it work there too ;-)

On windows I've done bidirectional communication though a pipe. I haven't tried though a pty or socket though. Do either of them work?

Bidi sockets should work now with the recent winsocket/sdlsocket patch I put in right before u1. You create the socket with the FILE_CREATE flag set and it'll create a server-type socket waiting for something to connect (telnet should work in a pinch), after which it should work bidirectionally. (Creating a socket without FILE_CREATE should result in bidi also, but of course you need some kind of server at the other end to connect to).

I think PTY was always bidi but I'm not sure how to test it

By the way, the invisible graphics in Tempest 2000 on the Jaguar got fixed by Ville today and the game is now quite playable. I'm not sure the starfield is right, but the game seems otherwise near-perfect including sound and music.



On a quick cruise through the softlist in case Ville's reading... ;-)

Doesn't boot: aircars, atarikar, mutantpng, battlesp, hstrike, protect, skyhamm.

Playable: avsp (minor HUD glitches), brutalsp (perfect?), bubsy (perfect?), defender (classic mode has some alignment issues but is quite playable, D2K mode has very broken gfx), doom (HUD is too wide, sound is bad/missing), ddragon5, dragon, dinodude, flashb (some alignment issues, title screen looks like screen res is too narrow, but in-game seems OK), flipout, hyperfrc, missil3d (many gfx glitches), pinballf (no sound), pitfall, raiden (music too fast), rayman (no sound), sensible (framebuffer vertical alignment looks off but otherwise perfect), soccerkd (seems perfect), syndicat, tempst2k (starfield seems not right, otherwise perfect), themeprk (glitchy, no sound, but seems playable), troyaik, ultravor1 (many sprite frames glitched but seems playable), zero5 (no sound but great working 3D models), zoop2 (perfect?).

Boots but not playable: cfodder (music plays, no graphics show), chekflag (sound OK but graphics totally busted), clubdriv (shows a title screen, then goes haywire), cybermor(1) (can start a game but only the HUD draws properly), feverpit (shows Licensed to Atari then nothing), fforlife(1) (shows garbage then nothing), iwar (can start a game, gfx are hosed, sound/music OK), ironsold (menus OK, but dies when game started), ironsol2 (some misaligned splash screens then dies), nbajamte (hangs after splash screens), pdrive (playable but game goes berzerk if you go off-course), spacewar (graphics completely destroyed, no sound), sburnout (menus work, game doesn't start), superx3d (one screen then hangs), totalcar (playable, sound OK, but gfx super glitchy), towers2 (may be playable, but flickery and I couldn't figure out how), trevmcfr (can start game but most gfx missing), ultravor, valdiser (menu glitchy and won't let you select anything), whitemen (splash screens ok then dies), wolf3d (can start a game then dies).

Jag results may vary, a bunch of those bomb out on Windows because of reading from a bad pointer (the way the blitter code uses memory is quite awful, done for speed but it means it ends getting a pointer to memory then reading from addresses way after it (my original fix to stop tempest 2k writing over it's own ROM was addressing that very issue for writes because once it had the pointer it didn't care if it was ram or rom it was trashing ;-)