They seem to have changed the command to list the driver file yet again. I"ll look into it.
A workaround is to remove the mameexe info in your mamehooker setup.
Nevermind. A new "feature" appears to be that you get a warning message if anything in your mame.ini is set to an invalid value... which is nice BUT it prints this error even if you are calling command line functions.