as i said in another thread, i'd like to start MESSing (
) up with console emulation in MESS, to possibly find bug to report.
at the end i decided to use command line mess (as i do with mame) since i have some problem with the UI
anyway, i have a couple of questions, sort of preliminary questions to avoid reporting useless/known bugs.
1. is it expected that the UI does not work with a debug compile of MESS? i mean: if i click on messgui after a clean compile with the debugger, the ui doesn't start at all (i can imagine that the debug interface can have 'collisions' with the usual UI, hence i wouldn't be surprised if this is the correct behaviour, but i'm not sure if it actually is)
2. which is the correct/expected behaviour if you launch without carts a system which require carts? if i lauch a bios in MAME, it exits with a memory_set_bankptr NULL error, while MESS gives an initialization error (so different behaviours, and i have no clue wheter mess is ok or not)
i also remember a post about this on this forum but i cannot find it anymore
3. are reports for systems not 100% working allowed? i think to snes, lynx et similia
ps. (about 3) i don't plan to file thousands of reports for any non working demo i find, but if recurrent issues appear i think a report can be of use, even if the driver isn't complete... provided, of course, those problems aren't already reported in the driver