archive.worldofdragon.org

It'd be tricky... ISTR there being some unexpected limit on binary size, and of course getting it running fast enough would mean stripping back a lot of things - and re-adding the NDS-specific video and audio code from ye olde days. But if you want a coding challenge, it should all still be there in...

Right! Sorry for not replying to this sooner... Looks like some interaction with the "-type" command needs some thought. The config file reading changes mean you can use double or single quotes and escape characters with backslash. At the moment the "-type" command also interprets some of those char...

Latest snapshot works around this by picking the first UI if specified one doesn't exist (any more).

MESS/MAME is just big . It has admirable goals... I'd have used MESS "back in the day" if a) it had stood a chance of running full-speed Dragon emulation on a GP32 or indeed an UltraSPARC Solaris desktop machine, and b) I'd stood a chance of understanding its architecture in the time available to me...

Aha! Yes, that totally explains it: the Windows specific code has been rolled into the general SDL code.

Congrats on finding it... if there had been any way for you to see stderr output there would have been a useful error message there... :/

XRoar doesn't itself write any logging anywhere other than stdout/stderr (edit: so you could run it from command line and redirect those to a file, I guess? though i think the whole need for a "console" window in the first place means that might not work) Windows generally - well it's not something ...

Well it's certainly easy enough to just build it again! It'll get a new snapshot id built in, so the binary will change. See if 2019-51897 behaves any differently...

Hope you find something - it's really odd that you see no output at all. There must be an error message somewhere!

FWIW I've just tested it on a Windows 10 laptop and yes, you have to click through an awful lot of nonsense, but it did then run (though appeared to start minimised, which was odd).

IIRC, the main Windows-related thing that changed in that snapshot is rolling the Windows-specific code into the main SDL2 initialisation. It's possible I've missed something out or done something in the wrong order and it still happened to work in Wine... I remember one other change: I redraw the m...

Interesting - worth doing some test runs, then...

Can you run with "-C" (to open a console) and paste what it says?