MAME and "Type ok"

[madk]

Ok I was just doing some brainstorming to make sure I didn't miss anything before I start my cabinet...and I thought about one thing.  While loading up some roms in MAME if comes up with that "Type ok to continue" prompt.  Now is there anyway to get around this?  I was thinking that once my cp was complete I don't want to have to pull out my keyboard everytime I want to fire up a certain game.  Hrmm..I feel like I am asking a dumb question but it was just something that came to mind.  Thanks.

madk

[hyiu]

try shaking your 1st player joystick left and right....
that should take care of the ok thing.....
heee heee.....    

ps: I'm using game pad hack....

[nullb0y]

thjat helped me alot umm will that work with a keyboard hack?

[BombProofPlane]

i heard there was script you can add in cant think of it right now

[Thenasty]

Here are the possiblities.

1. Modify source and Compile your own build (Of course    your not allowed to distribute it, just keep it to yourself).

2. Wiggle Joystick left-Right ( This is the Easiest one...)

3. Use ArcadeOS FE has option to bypass it in the Config.
    Don't have any other clues what other FE does it.

[u_rebelscum]

thjat helped me alot umm will that work with a keyboard hack?

Yes, keyboards work too.  (try pressing left - right (or the keys mapped to left and right) on your keyboard instead of O - K)

[nullb0y]

cool thanks

[Ryan]

That is awesome!  Just a little wiggle eliminates two buttons from my control panel plans.  Thanks!

[daywane]

I have mame 32. we have noticed some mame 32's,  down loaded , let you play the game  with out hitting  "OK" . After the first  time playing. You must hit "ok" the first time ,  but never again after this...
I just lucked out and this was the first mame I down loaded.

[Minwah]

I think all MAME versions operate in this way

Thenasty is right tho, compiling your own nag-free version is great

[)p(]

I think all MAME versions operate in this way

Thenasty is right tho, compiling your own nag-free version is great

Yeah lovely isn't  

And to all...compiling is not difficult at all. just follow the no brainer instructions on mame.net. After that you only have to adjust two lines off code...and compile it...

Peter

[Minwah]

I'm no C programmer, but I managed to do it using mame.net's instructions and a bit of thinking .

I think the relevant section of source changed slightly in .61 from memory (?).

[)p(]

I'm no C programmer, but I managed to do it using mame.net's instructions and a bit of thinking .

I think the relevant section of source changed slightly in .61 from memory (?).

true change it to: if(1)

/*-------------------------------------------------
   run_machine_core - core execution loop
-------------------------------------------------*/

void run_machine_core(void)
{
   /* disable artwork for the start */
   artwork_enable(0);

   /* if we didn't find a settings file, show the disclaimer */
   if (1)
   {
      /* show info about incorrect behaviour (wrong colors etc.) */
      if (1)
      {

Peter

[Tiger-Heli]

Yes, keyboards work too.  (try pressing left - right (or the keys mapped to left and right) on your keyboard instead of O - K)

Not exactly, MAME is looking for "O or L Arrow or Joystick X-" and "K or R Arrow or Joystick X+", so if your keyboard hack uses "Y" for Left and "G" for right, you won't be able to get past this screen.  You can avoid this without recompiling by reassigning keys:  I found my old notes for it here:  http://www.mameworld.net/emuadvice/ok.doc

Posted by: daywane Posted on: Today at 03:10:41am
I have mame 32. we have noticed some mame 32's,  down loaded , let you play the game  with out hitting  "OK" . After the first  time playing. You must hit "ok" the first time ,  but never again after this...
I just lucked out and this was the first mame I down loaded.

I think this is a bug in all MAME's (not MAME32).  It's on MAMETESTERS.  With certain (particularly GRAVIS) gamepads and joysticks, MAME will skip the startup screens.

BTW, to compile your own without nag screens, follow these changes (both 0.61 and previous versions) stolen from the Mameworld compile board:

I've been following these instructions in order to remove mame nags screens. But with 61, somethings seems to be changed.

Open up mame.c and edit line 1195: if (settingsloaded == 0) and change it to: if (0). In line 1202: if (showgamewarnings(real_scrbitmap) == 0) change it to: if (1).

Now, the most similar lines are

502 -> if (settingsloaded || showcopyright(artwork_get_ui_bitmap()) == 0) I change it to if (0)

505 -> if (showgamewarnings(artwork_get_ui_bitmap()) == 0) I change it to if (1)

However, after compiling (with no errors), mame don't work. Do you have the same problem?

Here you go!

502 -> if (settingsloaded || showcopyright(artwork_get_ui_bitmap()) == 0) I change it to if (1)

505 -> if (showgamewarnings(artwork_get_ui_bitmap()) == 0) I change it to if (1)

These are the correct changes try
them and recompile if it still doesn't
work then delete your obj-directory and
start from a clean build.

Good Luck
Rodney


In my custom compile, I also remove the "Bad or missing rom, Press any Key" screens as follows:  (Data provided by Ciro of Emuloader)  (Some of the code has changed since he sent this, but you should still be able to figure it out.

I discover where you can avoid that message (not only "No Good Dump Known",
but "bad CRC" and "bad Size" as well).

Follow these steps:

1. Make a backup copy of the file "mame\src\common.c"

2. Open the file "mame\src\common.c"

3. Go to the line 880 (not sure if this is the exact line)
  You will see this function:
  ......
  /*-------------------------------------------------
   display_rom_load_results - display the final
   results of ROM loading
  -------------------------------------------------*/

  static int display_rom_load_results(struct rom_load_data *romdata)
  ......

4. Comment this "IF" sequence (everything, including the " } " character on
the end of it)
  The commentary characters are:
  - to open the commentary use : "  /*  " (without the quotes)
  - to close the commentary use: "  */  " (without the quotes)

  ...........................
  /* if we're not getting out of here, wait for a keypress */
  if (!options.gui_host && !bailing)
  {
   int k;

   /* loop until we get one */
   printf ("Press any key to continue\n");
   do
   {
      k = code_read_async();
   }
   while (k == CODE_NONE || k == KEYCODE_LCONTROL);

   /* bail on a control + C */
   if (keyboard_pressed(KEYCODE_LCONTROL) && keyboard_pressed(KEYCODE_C))
      return 1;
  }
  ............................

5. Delete these two commented lines from the "IF" statement or the compiler
will generate an error...
  /* loop until we get one */

  /* bail on a control + C */

6. Save the file and re-compile MAME...
  That's it!!!


PS: Always keep the .o (object files). If you change only one file, you will
not need to wait for all the compilation to be over...

In the compilation folder, just delete the file "common.o" from "mame.obj"
folder (this folder can be different for other types of compilation, mine is
"mameppro.obj" because I use the Pentium optimized compilation)
so it will recompile only the "common.c" file and you will not need to wait
too long...
 

Hope this helps

[Minwah]

I too hide the 'Bad Rom' messages, as this stalls MAME before switching to full screen.  In my frontend, this causes what looks like a 'hang' as the dos-box is hidden, therefore you can never 'Press any Key''.  My FE does have features to cure this problem, but the best option is to compile your own - I believe HowardC has released a version that does just this (although you'll still have the OK screens).

[Howard_Casto]

Yup, it's on the lazarus homepage....  Upon the next release it will have much more though... things like psuedo translucent in game menus with definable colors multi mice support, ect.  That is if the respective mame build creators don't mind me swiping some code.  

[u_rebelscum]

Yes, keyboards work too.  (try pressing left - right (or the keys mapped to left and right) on your keyboard instead of O - K)

[/b]

Not exactly, MAME is looking for "O or L Arrow or Joystick X-" and "K or R Arrow or Joystick X+", so if your keyboard hack uses "Y" for Left and "G" for right, you won't be able to get past this screen.  You can avoid this without recompiling by reassigning keys:  I found my old notes for it here:  http://www.mameworld.net/emuadvice/ok.doc

Okay, if you want to get technical , MAME is looking for "O or [UI_LEFT]" and "K or [UI_RIGHT]".  (like your notes at http://www.mameworld.net/emuadvice/ok.doc say.)  IMO, you should map UI_left and (game)left to the same inputs, and UI_right the same as (game)right, UI_up & up, etc, but that's up to you.  However this way, if your keyboard hack uses "Y" for Left and "G" for right, you would also use "Y" for UI_Left and "G" for UI_Right, which would mean you would be able to get past the screen.

But you are right I should have said "try pressing leftArrow - rightArrow, which are the default UI_left - UI_right, or, if you changed them, the keys/buttons/joystickdirections mapped to UI_left and UI_right)..."  Thanks for correcting me.

[SirPoonga]

You'd be amazed at how many people don't know about the O K thing with the left and right, it is in the mame faqs.

[madk]

Consider me one of them...well not anymore.  But thanks guys!