Even this is a bit of a problem the way you describe it
'a brand new MAME64 executable' isn't enough.
There are a lot of sites stupidly offering MAME distributions containing ONLY the mame64.exe file*, this is bad, bad, bad. You should specifically avoid emucr and a lot of places offering 'no nag' builds for this reason.
Why is it bad? because a lot of MAME features these days need additional files, HLSL is one of those, Software Lists are another, without the support files you have a broken install that is liable to crash.
The official distributions found on mamedev.org of course do include the correct support files, but simply saying 'new MAME64 executable' doesn't convey this message properly.
I'm glad you have it sorted now, but don't underestimate the ham-handedness of some people packaging MAME. None of this is being sarcastic or treating you like an idiot.
* or in some cases out of date support files alongside it because they didn't bother to update them either, again just dropping a new exe into an old distribution folder they had.
> When I say "Fresh Install", I do mean "Fresh Install". A brand new MAME64 executable
> in a brand new folder. No need to be sarcastic.
>
> I thought it was a 0.167 problem as it was working with 0.166 before. I re-downloaded
> 0.166 and the problem was also there.
>
> I reinstalled DirectX and some Redistib from MS (they were already in my computer)
> and back to normal. No idea why it didn't work before.
>
> False alert.
|
Index 
Flat 
Re: MAME 0.167
Reply
