cant create mame.ini

[BlackFox]

okay i know how to do the -cc command and create an mame.ini file, but ive done this about 20 times and i still have nothing. example: my mame on my desktop is in "D:\Emulators\Mame" so i go into the command line and type "D:\Emulators\Mame\Mame.exe -cc"... it jumps to a blank command line like i would expect after preforming any dos-like command, but i check all my directories and there isnt a mame.ini file ANYWHERE. its driving me nuts because i want to be able to edit the configuration without having to do all of the text commands.
anyone got any ideas as to why this is happening?

[vibez]

D:\Emulators\Mame\Mame.exe -cc

That is your problem

You need to change to mame's directory before you run that command

Example

cd D:\Emulators\Mame\
Mame.exe -cc

The problem is that mame doesnt know where to write the .ini file to if you run a command from a different directory

[BlackFox]

yeah, i feel somewhat retarted now, because i ran a search and it showed up in D:\Documents and Settings\Administrator.
now i feel like i wasted forum space. lol

[SirPoonga]

The problem is that mame doesnt know where to write the .ini file to if you run a command from a different directory

Actually, it should have wrote it in whatever directory it was run from.  But yeah, it wouldn't be in the mame folder if run like that

BTW, some older frontends have this problem.  They won't run mame from within the  mame folder so the exe will be looking for stuff based in the executing folder.

[Tiger-Heli]

-createconfig , not -cc.

I'm not sure when this was changed, but -cc hasn't worked on the last few versions.

[SirPoonga]

cc and createconfig are the same.  It's always worked for me.

From the sourcecode
/* name, shortname, type, dest, deflt, min, max, func, help */
{ "createconfig", "cc", rc_set_int, &createconfig, NULL, 1, 0, NULL, "create the default configuration file" },

The first argument is the name, the second argument is the shortname.  either work.

another good option to help with problems
{ "verbose", "v", rc_bool, &verbose, "0", 0, 0, NULL, "display additional diagnostic information" },

So you can either use mame -v or mame -verbose.

[Tiger-Heli]

cc and createconfig are the same.  It's always worked for me.

From the sourcecode
/* name, shortname, type, dest, deflt, min, max, func, help */
{ "createconfig", "cc", rc_set_int, &createconfig, NULL, 1, 0, NULL, "create the default configuration file" },

The first argument is the name, the second argument is the shortname.  either work.

another good option to help with problems
{ "verbose", "v", rc_bool, &verbose, "0", 0, 0, NULL, "display additional diagnostic information" },

So you can either use mame -v or mame -verbose.

That's what I thought, but one one of my BuddaMAME's -createconfig worked and -cc didn't, I'm pretty sure.  Wouldn't hurt to try anyway.