How do I enable verbose logging?

SpudsMcToole

I'm still trying to solve this problem:

https://retropie.org.uk/forum/post/166438

and I figured verbose logging might be some help, but how the blazes do I switch it on? Every search result says it's an option in the Runcommand menu when you boot up a ROM file, but it bloody isn't.

I tried adding -log to EMULATORS.CFG:

advmess = "/opt/retropie/emulators/advmame/bin/advmess dragon32 -log -cfg /opt/retropie/configs/dragon32/advmess.rc -floppy %ROM%"
default = "advmess"

But that made no appreciable difference, the RUNCOMMAND.LOG file is still only this unhelpful line about not being able to find the BIOS, but not telling me where it's looking for it:

Parameters: 
Executing: /opt/retropie/emulators/advmame/bin/advmess dragon32 -log -cfg /opt/retropie/configs/dragon32/advmess.rc -floppy "/home/pi/RetroPie/roms/dragon32/Airball (1987)(Microdeal).cas"
d32.rom      NOT FOUND
OPTIONAL ddos10.rom   NOT FOUND
ERROR: required files are missing, the game cannot be run.

dudleydes

@SpudsMcToole Verbose logging is only available as an option in the runcommand menu for RetroArch emulators.

According to the AdvanceMAME/AdvanceMESS documentation, running advmess with the -log parameter creates a file with a .log extension. This is the file you should be looking for.

SpudsMcToole

@dudleydes Ah, Retroarch only? Dammit. And yep, as I said above, running with -log was no use :(

dudleydes

@SpudsMcToole Have you looked for the log file AdvanceMESS creates when you run it with -log? It should be a separate file, nothing to do with runcommand.log.

SpudsMcToole

@dudleydes Ah, no, I haven't. Where might one find those?

dudleydes

@SpudsMcToole Try the home folder, /home/pi.

SpudsMcToole

@dudleydes Hmm, no, no sign of anything there.

dudleydes

@SpudsMcToole I don't really know where the log is for certain as I have never played around with AdvanceMESS. I based my earlier post by running AdvanceMAME with the -log parameter which created advmame.log in the home folder.

You could use WinSCP or the find command to locate the log.

SpudsMcToole

@dudleydes Ha ha :D I'll have a go, but in my entire 18 months of using WinSCP I don't think its comedy search function has ever successfully found ANYTHING.