Previous Thread
Next Thread
Print Thread
Page 3 of 3 1 2 3
Re: sdl mame64 unresponsive [Re: Procyon] #112700
02/20/18 03:53 AM
02/20/18 03:53 AM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Solved.

OK, it was this line in the ui.ini that was screwing me up:

Code
categorypath              folders


I changed it to look in the MAME dir on my NTFS drive and the hang went away. This is a pretty odd thing though, I don't have a ui.ini anywhere else, so I don't understand why running .mame64 from within ~/dev/mame didn't reproduce the hang as well. I would imagine it was referring to the same ~/.mame/ui.ini file.

Not sure if I uncovered something that will help the community at large, or if this is something unique to the way I set MAME up. But as soon as I pointed categorypath to a valid location, mame was happy.

Last edited by Procyon; 02/20/18 03:53 AM.
Re: sdl mame64 unresponsive [Re: Procyon] #112701
02/20/18 05:06 AM
02/20/18 05:06 AM
Joined: Feb 2004
Posts: 1,993
Sydney, Australia
Vas Crabb Offline
Very Senior Member
Vas Crabb  Offline
Very Senior Member
Joined: Feb 2004
Posts: 1,993
Sydney, Australia
Originally Posted by Procyon
That's interesting. I tried backing up and blowing away my ~/.mame/mame.ini, and it didn't seem to make a difference.

A bit more digging in, for this line at the top of the inifile_manager constructor:

Code
	file_enumerator path(m_options.categoryini_path());


When I run from the build dir, path is NULL, so the for loop below doesn't run and I don't hang. When I run from my home dir, path is apparently "folders"... Checking my mame.ini


path is an object, not a pointer - it can't be NULL. But that aside, if walking a directory causes a hang, you have bigger problems with your setup.

Re: sdl mame64 unresponsive [Re: Vas Crabb] #112702
02/20/18 12:53 PM
02/20/18 12:53 PM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
Originally Posted by Vas Crabb
path is an object, not a pointer - it can't be NULL. But that aside, if walking a directory causes a hang, you have bigger problems with your setup.


My apologies, you are correct. What I should have said was that path.next() was NULL. But as soon as I set the categorypath to an valid non-relative directory, I was fine.

Last edited by Procyon; 02/20/18 01:08 PM.
Re: sdl mame64 unresponsive [Re: Procyon] #112710
02/21/18 01:42 AM
02/21/18 01:42 AM
Joined: Jan 2009
Posts: 42
Maryland, USA
P
Procyon Offline OP
Member
Procyon  Offline OP
Member
P
Joined: Jan 2009
Posts: 42
Maryland, USA
A little more egg on my face about this. I wondered why, despite everything, mame would return osd_file::error::NONE instead of osd_file::error::NOT_FOUND when it used the relative "folders" path to look for Favorites.ini. I was entirely unaware that I did in fact have a ~/folders path with a busted Favorites.ini file inside. I don't really know where it came from or when it got there (I forgot to check the timestamp before I deleted it). Once I blew it away, everything worked fine with the categorypath set to "folders". So ultimately this was entirely my problem. The code is doing things correctly. Sorry for any headaches or confusion I caused. And thank you to those who tried to lend a hand anyway.

Last edited by Procyon; 02/21/18 01:44 AM.
Page 3 of 3 1 2 3

Moderated by  R. Belmont 

Who's Online Now
3 registered members (ted, Robbbert, Tauwasser), 101 guests, and 2 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,587
Posts112,169
Members4,817
Most Online283
Oct 11th, 2018
Powered by UBB.threads™ PHP Forum Software 7.6.1.1
(Release build 20180111)
Page Time: 0.029s Queries: 14 (0.014s) Memory: 5.6630 MB (Peak: 5.8356 MB) Zlib enabled. Server Time: 2018-10-18 00:23:36 UTC