Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: MAME v36 Nag screen/Compiling  (Read 1464 times)

0 Members and 1 Guest are viewing this topic.

HagHore

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 133
  • Last login:October 24, 2007, 02:24:00 pm
  • Game Over Man, Game Over!
MAME v36 Nag screen/Compiling
« on: April 05, 2004, 11:10:40 am »
??? ??? If anyone can help me out here.  I've got a PII-400/ATI Rage/ESS onboard sound in a cab I'm building.  Using DOS 6.22 as the OS and GameLauncher for my Frontend.  I've grabbed NoNameMAME v72 and v76 and they work fine but the majority of the games, even the classics, won't run full speed on this old PC (using NNM because of the easy to remove Nag screens).  I also have MAME v36 (Release Code 2) installed and it runs the games full speed but I'm left with the nag screen showing up.  Now I have the compiler installed on my Win98 PC (followed the nice instructions on www.mame.net) but my C programming skills are poop as my last bit of programming in C was in '91 and that was for simple stuff.  So if anyone can tell me which lines of what source code need to be commented out to get rid of the nag screens in v36 I would appreciate it.
We're on an express elevator to Hell! Goin' down!

SirPeale

  • Green Mountain Man
  • Global Moderator
  • Trade Count: (+23)
  • Full Member
  • *****
  • Offline Offline
  • Posts: 12963
  • Last login:August 04, 2023, 09:51:57 am
  • Arcade Repair in New England
    • Arcade Game and Other Coin-Op Projects

Tiger-Heli

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 5447
  • Last login:January 03, 2018, 02:19:23 pm
  • Ron Howard? . . . er, I mean . . . Run, Coward!!!
    • Tiger-Heli
Re:MAME v36 Nag screen/Compiling
« Reply #2 on: April 05, 2004, 11:23:42 am »
For MAME 0.60 and previous (line numbers may be different):
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).

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...
It's not what you take when you leave this world behind you, it's what you leave behind you when you go. - R. Travis.
When all is said and done, generally much more is SAID than DONE.

HagHore

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 133
  • Last login:October 24, 2007, 02:24:00 pm
  • Game Over Man, Game Over!
Re:MAME v36 Nag screen/Compiling
« Reply #3 on: April 05, 2004, 09:18:02 pm »
Thanks for the assist guys, I'm going to give it a try tonight.
We're on an express elevator to Hell! Goin' down!

HagHore

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 133
  • Last login:October 24, 2007, 02:24:00 pm
  • Game Over Man, Game Over!
Re:MAME v36 Nag screen/Compiling
« Reply #4 on: April 07, 2004, 11:12:54 am »
As it turns out, the compiler files from mameworld did not work with the old version of MAME I was working with.  No problem though as I got excellent assistance from theNasty, so all is well and good in the world of classic gaming with older PCs. :D
We're on an express elevator to Hell! Goin' down!