Is There Any Way To Delete The Legal Warning Screen In MAME?

[EndTwist]

Hi Guys

Think I am glad that i asked the original question as it seems to have sparked a cracking thread. Can someone please clarify whether I should compile my own version or mame or whether to incoperate the skip frame ini file in my mame folder?

Also does it matter what the skip frame ini file is called in the mame folder?

Hey thanks again for all your help.

Lea

- You need to compile your own version in order to use skip_startup_frames.

- Yes, it does matter. Each INI file should be named after the rom name of the game you are skipping frames for.

[whatisk]

Is your computer fast enough for that version? For the latest versions, you should honestly be using at least a 1.5GHz PC. Otherwise, it would be better to go with an older version based on your processor speed.

Oh, and I have quite a number of INI's I have put together myself for skip_startup_frames (100+ of them? It's taken me hours and I haven't kept count) so I probably will post them in this (the Software) forum at some point.

I think there are about 120 in the zip file I compiled.

My MAME PC is a P4 2.4 with 512MB RAM, so I don't think speed is an issue. Without the skip_start_frames incorporated into the source, I can navigate the config menus in games with no issues, so I'm not sure why that switch causes issues. Though I must admit that I didn't actually try playing any games to see whether or not the whole thing was affected or just the menu for some reason. For the time being, I'm happy enough to have the 'normal' looking game loads.

Edit: have since found that all of my recompiled MAMEs display this behaviour - whether it be just adding in the 'skip_warnings' option or speeding up the start-up of games 

[Tiger-Heli]

Edit: have since found that all of my recompiled MAMEs display this behaviour - whether it be just adding in the 'skip_warnings' option or speeding up the start-up of games 

Could you post more details on what is happening and when, also under what OS?

[whatisk]

Could you post more details on what is happening and when, also under what OS?

I think I have found what the problem was. When compiling, I was running 'make' instead of 'mingw32-make'. Not sure if it is only coincidence or not, but when using that, MAME appears to run fine again.

But to let you know, I am running Win XP (SP1 as I don't really need all the security stuff introduced in SP2 for a standalone MAME box - in my opinion anyway). What would happen is that the game would load fine. When pressing keys for credits, start, going to the config menu, etc nothing would happen for 10 or more seconds. Eventually an occasional keypress from earlier would then register and sometimes quite a few would all happen at once and then it would go back to delayed responses again.

So, all seems fine now. I have my skip_warnings and fast/skip_startup_frames working with all key presses registering as they should 

[Tiger-Heli]

I think I have found what the problem was. When compiling, I was running 'make' instead of 'mingw32-make'. Not sure if it is only coincidence or not, but when using that, MAME appears to run fine again.

That's odd.  I wouldn't have thought to try Mingw32-make.

So, all seems fine now. I have my skip_warnings and fast/skip_startup_frames working with all key presses registering as they should 

Glad you got it working and thanks for sharing what you did!

[whatisk]

I think I have found what the problem was. When compiling, I was running 'make' instead of 'mingw32-make'. Not sure if it is only coincidence or not, but when using that, MAME appears to run fine again.

That's odd.