Getting INI file to load within MameWah

[lettuce]

Have set different options for my fav mame games within Mame32, such as hardware stretching, tripple buffering, and resolutions for different games. But now i have sorted out my frontend mamewah, when i load these games it seems to ignore these settings that i have set! Im guessing i need to add a config line for mamewah, but not sure what. Can someone help?

[lettuce]

Right ive worked out you need to point mamewah to the ini folder where mame32 is installed, but now have a new problem.
Using Alien VS Prediator as an example, if within mame32 in the options for this game, i have the option ticked for, stretch using hardware, the game loads within Mamewah fine, but i get the old screen roll over effect at the top and bottom of the screen, ( i sorted this out when playing the game using mame32 by just unticking the box for stretch using hardware) but if i untick the box and try and load the game through mamewah the screen saying that the rom is loading quickly appears then disappears and the rom doesnt load, i have noticed after this happens in the INI folder for Mame32,  next to the avsp.ini file (Alien VS Predator) another file appears called avsp.cfg. Why will mamewah not play this game when stretch using hardware is unticked??

[dax]

How do you point mamewah to find the ini folder?  Is this the game_specific_config_path option?  I set that to c:\mame\ini and it's still not reading the individual game ini files.  Do I need to do something like c:\mame\ini\[name].ini ?

[Minwah]

How do you point mamewah to find the ini folder?

You don't, you point MAME to it.  Edit \mame\mame.ini and set 'inipath' accordingly.

Lettuce: You need to do the above also, and ditch MAME32 if possible.

[brophog]

You don't, you point MAME to it.  Edit \mame\mame.ini and set 'inipath' accordingly.

When you hire that novelist to do the documentation, Minwah, this needs to be in there. There is a lot of discrepancy in questions of late on what Mamewah does and what it doesn't.

It's a frontend. It points to things. Anything game related is the product of Mame or another emulator.

[dax]

MameWah is really a mysterious, strange thing, kind of like Bigfoot.  Some people have apparently seen it [work] and others think it's just a myth [that it can be properly configured].  I'm still waiting for my bigfoot sighting.

I have Mame 0.69 DOS working perfectly now.  I have Mame32 .102 working perfectly now.  I have ArcadeOS running rock solid using 0.69.  HOWEVER, running MameWah with 102 just does not work, and I've gone over the configs tons of times.  I've started doing my own debugging traces to figure out what is going on and what weird things MameWah does. 

From what I can see, there isn't a command line parameter to tell Mame (102) where to look for the mame.ini file, and I am not sure what is the default path when MameWah spawns Mame.exe so I move the mame.ini file all around trying to find where it can be located so that when Mamewah spawns mame, it will be findable (if Mamewah is not in the same directory as Mame.exe, it sure doesn't seem to look by default where the executable mame.exe is located).  In one configuration I could get it to find the .ini file HOWEVER MameWah shows every game in the same 800x600 resolution.  Every other instance and version of Mame works perfectly... except Mamewah and I have no idea why or how MameWah is causing Mame to ignore all the resolution and configuration information.  Very frustrating.

[brophog]

Dax, trust us on this one.

STOP USING MAME32 WITH MAMEWAH.

[2600]

MameWah is really a mysterious, strange thing, kind of like Bigfoot.  Some people have apparently seen it [work] and others think it's just a myth [that it can be properly configured].  I'm still waiting for my bigfoot sighting.


From what I can see, there isn't a command line parameter to tell Mame (102) where to look for the mame.ini file, and I am not sure what is the default path when MameWah spawns Mame.exe so I move the mame.ini file all around trying to find where it can be located so that when Mamewah spawns mame, it will be findable (if Mamewah is not in the same directory as Mame.exe, it sure doesn't seem to look by default where the executable mame.exe is located).  In one configuration I could get it to find the .ini file HOWEVER MameWah shows every game in the same 800x600 resolution.  Every other instance and version of Mame works perfectly... except Mamewah and I have no idea why or how MameWah is causing Mame to ignore all the resolution and configuration information.  Very frustrating.

I think your frustration lies with MAME not MAMEWAH.  MAME has it's own mame.ini file.  Have you created this file and put all your settings FOR MAME in it?
I'd suggest you read the folowing after you read the documentation:
http://www.mameworld.net/easyemu/
specifically
http://www.mameworld.net/easyemu/mameguide/mameconfig.htm



BTW, I'd stop spewing theories and badmouthing things you don't know or assume.

[dax]

Dax, trust us on this one.

STOP USING MAME32 WITH MAMEWAH.

Excuse me?

I am using the command line version of mame with Mamewah.

I think I can tell the difference.  Mame32 is 32MB in size.  Command line version if 8MB.   These were separate downloads.  How could I possibly be using Mame32 from Mamewah? 

[brophog]

I have Mame 0.69 DOS working perfectly now.  I have Mame32 .102 working perfectly now.  I have ArcadeOS running rock solid using 0.69.  HOWEVER, running MameWah with 102 just does not work,

My mistake then. From that quote it wasn't clear that you were using commandline with mamewah.

[dax]

I think your frustration lies with MAME not MAMEWAH.  MAME has it's own mame.ini file.  Have you created this file and put all your settings FOR MAME in it?
I'd suggest you read the folowing after you read the documentation:
http://www.mameworld.net/easyemu/
specifically
http://www.mameworld.net/easyemu/mameguide/mameconfig.htm

BTW, I'd stop spewing theories and badmouthing things you don't know or assume.

See this thread for more details:
  http://forum.arcadecontrols.com/index.php?topic=47895.0

I am well aware that Mame has it's own ini file.  Why it is ignored from MameWah is what I don't know.

Let's get real here.  I understand you all have the developer of Mamewah participating in this forum... that's great... but every single one of you also knows that MameWah leaves a lot to be desired when it comes to user-friendliness.... Hell, if you put any comments in the ini files, they're stripped out each time the program is run.. WTF?  Hey Minwah... what's up with that?  Are you intentionally trying to make your program even more difficult to configure?  I just don't get it.. WHY would you do something like that? 

I'm sorry if you think that is "bad-mouthing".  I am just expressing an opinion.  I TOTALLY APPRECIATE the guy for developing the program, and from what I see, it looks to be a great emulator, but I am not going to pretend that there aren't some issues that need to be addressed.

Obviously, I'm interested in using his program.  Admittedly, I am making some of my replies a little more acerbic and comedic, but I've found it helps get people motivated to respond.  Don't take it personally.  We all have the same goals here.  And if I can get this darn program running reliably, I'll be MinWah's greatest booster, but until then, I am confounded by some of the weird behavior of this program and am appealing to others to help.

[Minwah]

When you hire that novelist to do the documentation, Minwah, this needs to be in there. There is a lot of discrepancy in questions of late on what Mamewah does and what it doesn't.

It's a frontend. It points to things. Anything game related is the product of Mame or another emulator.

As far as I'm concerned setting up MAME's inipath (& other settings) is related purely to MAME setup, and this should be one of the first things a MAME user does (regardless of FE).

I agree with what your saying (I should have this in some docs), but still if you use MAME you should know how to use it before even attempting to use a FE...anyone not confident with commandline MAME should take a look here: http://www.mameworld.net/easyemu/

[Minwah]

MameWah is really a mysterious, strange thing, kind of like Bigfoot.  Some people have apparently seen it [work] and others think it's just a myth [that it can be properly configured].  I'm still waiting for my bigfoot sighting.

Goodness me.

I have Mame 0.69 DOS working perfectly now.  I have Mame32 .102 working perfectly now.  I have ArcadeOS running rock solid using 0.69.  HOWEVER, running MameWah with 102 just does not work, and I've gone over the configs tons of times.  I've started doing my own debugging traces to figure out what is going on and what weird things MameWah does. 

I think I mentioned this somewhere else but do you have Windows Commandline MAME?  I do not recommend using DOS MAME or MAME32 with Mamewah so that would be a good thing to start with.  I know your later reply says you are using 'commandline mame', but it is unclear to me which version you are using exactly.

From what I can see, there isn't a command line parameter to tell Mame (102) where to look for the mame.ini file

Why do you need to tell MAME where mame.ini is??  It should always be located in MAME's folder.

and I am not sure what is the default path when MameWah spawns Mame.exe so I move the mame.ini file all around trying to find where it can be located so that when Mamewah spawns mame, it will be findable

I have no idea what you mean by 'mamewah spawning mame.exe'.  As above your (mame) mame.ini file should be within your MAME folder...when you do 'mame -cc' to create mame.ini this happens by default, so I'm not sure why you would place mame.ini anywhere else.

(if Mamewah is not in the same directory as Mame.exe, it sure doesn't seem to look by default where the executable mame.exe is located).

I think you are confused somehow...Mamewah *never* does *anything* with MAME's mame.ini file - MAME creates it, parses it, uses it - regardless of FE.

In one configuration I could get it to find the .ini file HOWEVER MameWah shows every game in the same 800x600 resolution.

This is a MAME configuration issue - nothing to do with Mamewah.  Run MAME from a commandline until it works properly and then configure a afterwards.

Every other instance and version of Mame works perfectly... except Mamewah and I have no idea why or how MameWah is causing Mame to ignore all the resolution and configuration information.  Very frustrating.

Mamewah isn't causing Mame to ignore the configuration - there must be a Mame configuration issue.  My first guess would be an incorrectly named ini file...it should be named the same as your mame executable (bar extension of course).  So for example  for mame.exe you need mame.ini, mame102.exe needs mame102.ini etc.  However, there used to be a bug/issue with MAME where you would need to call this mame.ini (regardless) - I'm not sure if this has been fixed, but the easy thing to do is just use mame.exe and mame.ini.

[Minwah]

Let's get real here.  I understand you all have the developer of Mamewah participating in this forum... that's great... but every single one of you also knows that MameWah leaves a lot to be desired when it comes to user-friendliness.... Hell, if you put any comments in the ini files, they're stripped out each time the program is run.. WTF?  Hey Minwah... what's up with that?  Are you intentionally trying to make your program even more difficult to configure?  I just don't get it.. WHY would you do something like that? 

I wrote the ini system based around MAME's own system (based on the ideal that users should be able to operate MAME properly).  You will find if you comment in MAME's mame.ini file, and subsequently do a 'mame -cc' your comments dissapear since they are unrequired.  I used the same principal for Mamewah.  I don't see anything wrong with that frankly.

I'm sorry if you think that is "bad-mouthing".  I am just expressing an opinion.  I TOTALLY APPRECIATE the guy for developing the program, and from what I see, it looks to be a great emulator, but I am not going to pretend that there aren't some issues that need to be addressed.

Sure there's issues, there always will be - as with all free software really.

Oh, and it's a frontend, not an emulator

Obviously, I'm interested in using his program.  Admittedly, I am making some of my replies a little more acerbic and comedic, but I've found it helps get people motivated to respond.  Don't take it personally.  We all have the same goals here.  And if I can get this darn program running reliably, I'll be MinWah's greatest booster, but until then, I am confounded by some of the weird behavior of this program and am appealing to others to help.

I usually respond to all Mamewah-related posts here, no matter how acerbic or comedic they are.

[brophog]

but still if you use MAME you should know how to use it before even attempting to use a FE

 

[Hoopz]

Props (or kudos in the bs corporate world) to Minwah for being extremely supportive and patient will all the questions and pointed comments (barbs) about his program.  Nobody and no program is perfect but Minwah probably couldnt have handled himself any better.

Cheers man.  Fly over the pond and beers are on me.