Re: sdlmame

Matthias Saou wrote:
> Andre Robatino wrote :
>
>   
>>   I installed and tried to run sdlmame.  It almost immediately exited 
>> due to it expecting to find roms and other files in a different, 
>> version-specific location (/usr/share/doc/sdlmame-0.109/dirs, 
>> apparently).  My mouse froze, though I was able to use the keyboard to 
>> log out and back in, at which point it worked again.  It would be better 
>> to use a version-independent directory.  Also, is there going to be an 
>> sdlmess to replace xmess?
>>     
>
> The "/usr/share/doc/sdlmame-0.109/dirs/" directory is included as a
> skeleton only. I don't see how the sdlmame binary could know anything
> about that absolute path... are you sure it was looking for roms in
> there!? By default I think it looks for $PWD/roms/.
>
> And yes, sdlmame is a bit more rough around the edges than xmame was. It
> definitely need a frontend to become anything close to user friendly,
> but unfortunately there aren't any (yet, AFAIK). A quick frontend in
> pygtk to set the basic paths and options should be trivial...
> anyone? :-)
>
> Quick start :
> cp -a /usr/share/doc/sdlmame-0.109/dirs/ ~/sdlmame/
> cd ~/sdlmame/
> sdlmame -createconfig
> vi sdlmame.ini
> (and edit paths)
>
> Maybe the sdlmame.ini is looked for by default in ~/.mame/ but I didn't
> try it.
>
> Matthias
>
>   
  You're right, when it couldn't find the roms, I looked at the list of 
files included in the package and falsely assumed it was one of them.  
When the roms are in $PWD/roms, it finds them and runs, and doesn't 
freeze the mouse on exit.  However, it is _extremely_ slow (I'm using 
82865G integrated video).  It's not usable on my hardware in its current 
state, unfortunately.