MAMEWorld Forums - EmuChat - Re: MAME Fatal Error help please

> > Running 64 bit MAME .207 on a 64 bit Windows 10 machine.
> >
> > Played Popeye (revision D). Everything was fine. However, I did notice on this
> game,
> > if you change dip switches, the changes do not take effect until the game is
> totally
> > restarted (on some games it takes effect after cycling through attract mode).
>
> More often than not, games with hardwired dip switches are read at boot time and
> changing the orientation of the switches is not recommended while the machine is in
> operation. MAME does not force reset, so such changes with DIP would be best followed
> by exiting then restarting MAME, or using the SHFIT+F3 which is a HARD RESET,
> basically stop/start in one step.
>
> > I changed one dip switch, from up right to cocktail. When I restarted the game, I
> got
> > this error message:
> >
> > Fatal error: netlist ERROR: Error adding TERMINAL C.5 to terminal list
> >
> > At that point, it completely boots me out of the MAME front end I am running
> > (MAMEUI64).
> >
> > Changing that one dip switch was the only thing I did between the two games. Now I
> > can't even start the game to change the dip switch back. Can anyone tell me how to
> > manually change the dip? I imagine I have to edit some file somewhere, but I have
> no
> > idea where. Thanks,
> >
> > Joe (joemagiera at ameritech dot net)
> > [email protected]
>
> I only have MAME64 version 0.207 (official from mamedev.org) and I do not get such an
> error no matter what the Cabinet switch is set to. MAMEUI, I think by default, saves
> all previous run information (write config) so if you get a configuration that causes
> problems, it will continue in that state until you exit MAME and then manually delete
> your entry in the CFG folder (popeye.cfg) and try again.
>
> Current version 0.215 as well as current Github sources also seem to work fine, so
> I'm unsure why the UI flavor is having issues. There is a new version expected in
> just a couple days, perhaps you'd want to pick that up.

it's a report for 0.207, that bug did exist in certain configurations in said build