Build Your Own Arcade Controls Forum
Main => Software Forum => Topic started by: fmzip on April 05, 2015, 05:30:02 pm
-
Running windows XP SP2 and the latest version of MAME, this is what I get on my display. Any suggestions as to what to try?
(http://home.comcast.net/~fotosbyfran/Space%20Invaders%20Arcade/IMG_0748.JPG)
-
intel graphics?
try updating the drivers.. but it might just be they suck too much
in which case -video ddraw or you might want to try one of the SDL builds which have a different video codepath completely.
http://mamedev.emulab.it/haze/2015/02/25/ume-mame-mess-0-159/ (http://mamedev.emulab.it/haze/2015/02/25/ume-mame-mess-0-159/)
(sorry haven't had time to do 0.160 builds yet)
-
I run MAME perfectly on Intel graphics, I even resolved the video preview issue.
What's the spec on your computer?
-
intel graphics?
try updating the drivers.. but it might just be they suck too much
in which case -video ddraw or you might want to try one of the SDL builds which have a different video codepath completely.
http://mamedev.emulab.it/haze/2015/02/25/ume-mame-mess-0-159/ (http://mamedev.emulab.it/haze/2015/02/25/ume-mame-mess-0-159/)
(sorry haven't had time to do 0.160 builds yet)
The SDL build works on my Sony Laptop running Windows 7 which is great! Where is the ROM directory with this SDL build?
-
intel graphics?
try updating the drivers.. but it might just be they suck too much
in which case -video ddraw or you might want to try one of the SDL builds which have a different video codepath completely.
http://mamedev.emulab.it/haze/2015/02/25/ume-mame-mess-0-159/ (http://mamedev.emulab.it/haze/2015/02/25/ume-mame-mess-0-159/)
(sorry haven't had time to do 0.160 builds yet)
The SDL build works on my Sony Laptop running Windows 7 which is great! Where is the ROM directory with this SDL build?
it will still use whatever rom paths you configure in mame.ini
you can create the ini file with sdlmame -cc on the commandline
by default it just looks in 'roms' in the same folder
for the most part it works the same as a regular mame CL build, just some slightly different SDL specific ini options.
-
^^^ Need some help with what you are describing.
That is greek to me
-
First: Is the problem only MAME-related? Do you see the windows desktop on your screen?
-
^^^ Need some help with what you are describing.
That is greek to me
don't really have time to do a full tutorial on commandline use, guess you've only used the GUI builds before.
hopefully people here can get to the bottom of it for you, or guide you thought the process if you do decide to use one of the commandline builds.
windows key + R will get you a run prompt
typing cmd.exe will get you the command line
but beyond that you really have to know what you're doing to some degree, and it sounds like you have no knowledge at all.
most of the frontends assume a regular DirectX build too, not SDLMAME too, so might not help much.
-
I mentioned this in your other thread, but I'll post it here as well.
You get that screen garbage when your video set doesn't want to do Direct3D. Simply add the switch "-video ddraw" at the end of your command line and it will work.
-
got it to work, used Mame 1.45 instead