> There’s an additional for the output provider on Windows that isn’t listed. I think > it’s because we’re trying to encourage people not to write software that depends on > it, so it can be removed at some point. It looks like MAME Hooker hasn’t been updated > in half a decade or however long it is. Anyway, try setting the output provider to > "windows" to use Windows named pipe communication and see if MAME Hooker is happier.
Thanks Vas, will do.
EDIT: Yes so the windows option works.. somewhat. MAME Hooker detects the output now however it's clear it's not so happy with windows 10 anymore. If it's going to be deprecated then is there going to be a os-independant option that would allow an external program to do the same as name hooker?
Edited by NaokiS (09/29/21 05:28 PM)
|