BabyBillyFreeman Posted September 27, 2022 Share Posted September 27, 2022 Been using LB and setting up MAME on multiple machines since May, but this new error has me stumped No idea why this is happening, I'm simply using the MAME wizard to setup a full mame rom set with 0.246 if anyone has seen this error before, appreciate any help thanks! Quote Link to comment Share on other sites More sharing options...
Kiinkyfoxx Posted September 27, 2022 Share Posted September 27, 2022 (edited) Hi @BabyBillyFreeman I have had a similar issue but at a different line. With the help of others on here I found that generating the file myself and then reviewing it I was able to see what the problem was, for me it was using Devreorder system wide to help with controller ID order To produce the file you; Open a command window change directory to wherever you have the mame.exe then mame -listxml > listdump.xml This will generate the file in the same folder and then I used notepad++ to open it and find the problem line. Which hopefully will let you figure out the issue or come back here and ask for more help with the specific issue Good luck Edited September 27, 2022 by Kiinkyfoxx Quote Link to comment Share on other sites More sharing options...
BabyBillyFreeman Posted October 1, 2022 Author Share Posted October 1, 2022 thanks for the tip, this is new, great to learn about this! unfortunately the line error number that LB spits out doesn't exist in the mame xml dump! so this error might not even be from mame, it's probably from launchbox itself i reported the bug on LB, but one of the devs got back to me and said this is caused by using an old unsupported version of mame before 0.17'something. I explained that I'm using mame 0.246 (im even using the same one on several other LB machine setups and it works, so something is wrong with this LB on this machine (which was fine until I try to update it). Quote Link to comment Share on other sites More sharing options...
BabyBillyFreeman Posted October 1, 2022 Author Share Posted October 1, 2022 quick update, got this resolved. turns out I had same issues as you @Kiinkyfoxx- it was devreorder causing the issue, I got rid of it since its not that great anyways, thanks! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.