![]() |
2007-10-19
, 04:52
|
Posts: 7 |
Thanked: 0 times |
Joined on Oct 2007
|
#72
|
![]() |
2007-11-04
, 02:38
|
Posts: 7 |
Thanked: 0 times |
Joined on Oct 2007
|
#73
|
![]() |
2007-11-06
, 19:59
|
Posts: 7 |
Thanked: 0 times |
Joined on Oct 2007
|
#74
|
![]() |
2007-11-08
, 14:49
|
Posts: 7 |
Thanked: 0 times |
Joined on Oct 2007
|
#75
|
![]() |
2010-01-07
, 19:59
|
|
Posts: 100 |
Thanked: 102 times |
Joined on Apr 2008
@ Amazon-Belém
|
#76
|
I first assumed it was a problem with the location of the ROM zip. Initially I tried with the "Browse" feature in XMAEME which I thought must be passing the full path to XMAME. Then I tried looking for the XMAME config file and putting the ROM zip in the default path. This caused the ROM to appear in the XMAEME pulldowns as "known" games but still resulted in "Unable to load ROM" for every ROM zip I tried.
However, when I launch XMAME from the command line, whether passing the option with the absolute path to the ROM zip or putting the ROM zip in the default path, every ROM I tried runs fine.
Is there a log file somewhere that I can post that will give you more precise information and help you pinpoint the problem?