Print

[coreyinoz]

QUOTE(danked @ Dec 26 2009, 05:12 AM)

also tried to put the roms in Emus\Mame\roms\ didn't work.

This actually worked for me after I deleted the .ini file.

So MS internal HD \Emus\Mame\roms\

Next issue - MAME won't load any of them. Any advice here? I have a half-dozen old roms that load fine under MAMEOX for xbox1. On MAME360 it just goes through the loading screen, pauses, then back to MAME menu.

Thanks,

coreyinoz

[wolfson8471]

QUOTE(iTry @ Dec 20 2009, 07:13 AM)

okay got the container built, just really dissapointed that i can only make it 4gb
i have 15gb+ of mame roms and i cant container them all

thinking of making several mame containers for specific developers, or maybe just my favorites

Instead of building your own container use QuickBoot v1.1 and create a "games on demand" container shortcut  pointing to the .xex  (or demo container if your prefer) No need to worry about the 4gb limitation with this method.

[mathieulh]

The problem is the only defined devices are

CODE

usb:....\Device\Mass0...dvd:....\Device\Cdrom0

so setting another one will fail, there is still a way though, you can set game:\ in the .ini file

this way : rompath = game:\Emus\Mame\roms
game:\ being the folder which contains mame's xex.

Then it will work.

patching with an hex editor the device map string changing it to the following

CODE

hdd:....\Device\Harddisk0\Partition1

 might have worked but the path lenght is too big for it to respect the original one.

P.S. To those who could not figure it out, the in rom menu is accessed by using left trigger + a

This post has been edited by mathieulh: Jan 8 2010, 08:22 PM

[coreyinoz]

QUOTE(coreyinoz @ Jan 8 2010, 04:03 PM)

This actually worked for me after I deleted the .ini file.

So MS internal HD \Emus\Mame\roms\

Next issue - MAME won't load any of them. Any advice here? I have a half-dozen old roms that load fine under MAMEOX for xbox1. On MAME360 it just goes through the loading screen, pauses, then back to MAME menu.

Thanks,

coreyinoz

Turns out that deleting the .ini file is not good advice. It will make the ROMS show up if you use the default folder places, but prevent roms from loading.

Better solution is to fix the paths in your .ini properly so MAME sees the roms, and then they boot.

All is good now.

PS - Left trigger plus A brings up MAME menu, Left trigger plus push RS brings you back to MAME rom list

coreyinoz

[modslave]

QUOTE(coreyinoz @ Jan 9 2010, 06:20 PM)

Turns out that deleting the .ini file is not good advice. It will make the ROMS show up if you use the default folder places, but prevent roms from loading.

Better solution is to fix the paths in your .ini properly so MAME sees the roms, and then they boot.

All is good now.

coreyinoz

I agree editing the .ini seems the way to go but can you give us an exact example of what address you have in yours?  Im trying to load off internal hdd not usb and have tried everything

[mathieulh]

Just look at my post, as I said use game:\ as a device ini the option.ini file . game:\ maps to the folder where your xex is contained.

anything other than usb, dvd or game will fail because such devices as hdd are not defined in the mame binary.

This post has been edited by mathieulh: Jan 11 2010, 05:09 PM

[modslave]

QUOTE(mathieulh @ Jan 11 2010, 04:08 PM)

Just look at my post, as I said use game:\ as a device ini the option.ini file . game:\ maps to the folder where your xex is contained.

anything other than usb, dvd or game will fail because such devices as hdd are not defined in the mame binary.

Christ this is doing my head in

I already look thick on this thread so one more wont make any diff

my xex is on internal drive at Hdd1:\EMUS\mame
my roms are in Hdd1:\EMUS\Roms

Tried changing Hdd1 to game and couple of others tries I won't mention.  Does someone want to put me out of my misery and shame?

[BIMPtacular]

Why do the vast majority of my roms not show up at all?  I have all of them zipped and tried renaming some of them and they still don't show.  Weird.

[coreyinoz]

QUOTE(modslave @ Jan 11 2010, 08:00 PM)

my xex is on internal drive at Hdd1:\EMUS\mame
my roms are in Hdd1:\EMUS\Roms

There's your problem. Unless you are changing the .ini file, everything should be below \Mame

Example;

hdd1\emus\mame
hdd1\emus\mame\roms
etc...

Then edit your .ini so the root of all paths is game:\ (as mentioned above).

Example;

game:\roms
etc.

Then all will work, and all is good.

QUOTE(BIMPtacular @ Jan 12 2010, 06:19 AM)

Why do the vast majority of my roms not show up at all?  I have all of them zipped and tried renaming some of them and they still don't show.  Weird.

Possibly because this build of MAME is from 2007, and you're looking at newer roms?

Would be nice if somebody updated this build for sure...

[modslave]

QUOTE(coreyinoz @ Jan 14 2010, 06:19 PM)

There's your problem. Unless you are changing the .ini file, everything should be below \Mame

Example;

hdd1\emus\mame
hdd1\emus\mame\roms
etc...

Then edit your .ini so the root of all paths is game:\ (as mentioned above).

Example;

game:\roms
etc.

Thanks coreyinoz for your reply.  
Although when reading it I realized I made a mistake in my post,  I DO have the folder structure YOU stated ie

hdd1\emus\mame
hdd1\emus\mame\roms

and I had already changed my ini to
rompath = game:\EMUS\mame\Roms

And they do not work.  Also tried rompath = game:\Roms     does the character case matter?

[coreyinoz]

OK,

Cut and paste of my .ini file;

rompath = game:\roms
samplepath = game:\samples
cfg_directory = game:\cfg
nvram_directory = game:\nvram
memcard_directory = game:\memcard
input_directory = game:\inp
state_directory = game:\sta
artpath = game:\artwork
snapshot_directory = game:\snap
diff_directory = game:\diff
ctrlrpath = game:\ctrlr
comment_directory = game:\comments
cheat_file = game:\cheat.dat
title_path = game:\titles

autoframeskip = 0


I have it installed into an internal hardrive at location

\Emus\Mame (mame360.xex in here)
\Emus\Mame\Media (.ini file and other supporting files in here)
\Emus\Mame\roms (guess what goes here)

That's it. If you can't get it working now, not sure what else to say.

Good luck.

[modslave]

coreyinoz I can't thank you enough for your patience and time!
I finally have it working  (IMG:style_emoticons/default/pop.gif)

As you are also running from internal drive I started from scratch copying yours including the letter case of folders and copy pasted the ini and hey presto

[problem_child]

Thanks for the info, but I had a problem and wanted to see if it worked for you guys. Even though I can now boot Mame from NXE dashboard following coreyinoz advice, I still need the usb stick to be plugged in for the rom list to work. Does anyone here have the same issues. Do you need all files and folders that are in the option.ini?

[hazed69]

everyone talks about an ini.file but i never seen one
do i make one?
and if so how?

[problem_child]

The options.ini file is in the Media folder, if you don't have one you probably got the retail dash one.

I found out what I was doing wrong I had both Mame360's on my hard drive and it was messing up each other. The method coreyinoz posted does work sorry for any confusion.