Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: SirPeale on July 05, 2004, 03:21:48 pm

Title: Mame .84u1 Released
Post by: SirPeale on July 05, 2004, 03:21:48 pm

0.84u1

Driver Improvements:

Fixed missing sound in Borderline (bootleg). [Aaron Giles]

Changes to the main program:

Fully obsoleted the old input ports, modifying all drivers to use the new forms.

Added a number of new PORT_* macros to handle all the previously-defined flags.
[Aaron Giles]

Fixed several issues with the new input port system. [Aaron Giles]
Removed support for older format CFG files. [Aaron Giles]
Removed support for "cheat" ports and "reset CPU 0" ports. [Aaron Giles]
Fixed several i960 bugs. [R. Belmont]

Fixed bugs in the concmpo, concmpi, and modi instructions
Added "text" and hex displays of the AC register for debugging
Added TESTx opcodes to the disassembler

Changed listxml to output all game flags. [Fujix]

New Clones supported or promoted from GAME_NOT_WORKING status:

Crazy Kong (Alternative levels) [Lee, Martin White]
Nibbler (set 3) [David Haywood]

New Non-Working games / clones supported

Super Qix (set 2) [David Haywood]
Conquer [David Haywood]

Title: Re:Mame .84u1 Released
Post by: SirPeale on July 05, 2004, 04:09:50 pm

Hm, just tried compiling it with mame32 support, here's what I got:

Code: [Select]

H:\MAME84~1>make WINUI=1 SUFFIX=32
Compiling src/ui/m32util.c...
src/ui/m32util.c: In function `DriverUsesTrackball':
src/ui/m32util.c:401: `IPF_MASK' undeclared (first use in this function)
src/ui/m32util.c:401: (Each undeclared identifier is reported only once
src/ui/m32util.c:401: for each function it appears in.)
src/ui/m32util.c: In function `DriverUsesLightGun':
src/ui/m32util.c:438: `IPF_MASK' undeclared (first use in this function)
make: *** [obj/mame32/ui/m32util.o] Error 1

Title: Re:Mame .84u1 Released
Post by: SirPoonga on July 05, 2004, 09:20:35 pm

new cfg files, huh?

Title: Re:Mame .84u1 Released
Post by: cdbrown on July 06, 2004, 12:33:22 am

mmm - wonder if I'm using the old or the new cfg format?

Title: Re:Mame .84u1 Released
Post by: u_rebelscum on July 06, 2004, 05:02:04 pm

Quote from: cdbrown on July 06, 2004, 12:33:22 am

mmm - wonder if I'm using the old or the new cfg format?

Open cfg/*.cfg file in hex editor
Look at the eighth character (first seven should be ASCII "MAMECFG")
If it's less than hex 09, the cfg is old.

History:
Mame used to have legacy code so it could read versions 08, 07, 06, 05 cfg files. AFAIK, 09 is the exact same as 08 except for having players 5-8 (version 0.74). 08 has been around since 36b16. Even cfg files 10 versions old often don't work or cause crashes, you better not be using the same cfgs since from .036b15! ;)

clipk from (old) source:

/* header identifying the version of the game.cfg file */
/* mame 0.36b11 */
#define MAMECFGSTRING_V5 "MAMECFG\5"
#define MAMEDEFSTRING_V5 "MAMEDEF\4"

/* mame 0.36b12 with multi key/joy extension */
#define MAMECFGSTRING_V6 "MAMECFG\6"
#define MAMEDEFSTRING_V6 "MAMEDEF\5"

/* mame 0.36b13 with and/or/not combination */
#define MAMECFGSTRING_V7 "MAMECFG\7"
#define MAMEDEFSTRING_V7 "MAMEDEF\6"

/* mame 0.36b16 with key/joy merge */
#define MAMECFGSTRING_V8 "MAMECFG\x8"
#define MAMEDEFSTRING_V8 "MAMEDEF\7"

Title: Re:Mame .84u1 Released
Post by: Howard_Casto on July 07, 2004, 02:15:37 am

Rebel, while you are here......

Mame apparently has new input ports this verison too. Anything useful? I haven't gotten a chance to really look yet.

Title: Re:Mame .84u1 Released
Post by: u_rebelscum on July 08, 2004, 02:10:54 am

Haven't had much time to look at it, dang it. :( And since Analog+ is all about inputs, that means no new analog+ until I figure it out.

I did notice there is a new input alias macro, that looks like it can take the place of the input part of the GAME macros (the fifth arguement). If that means even more core + all drivers changes, or just leave that area as-is looks like it's up to Aaron. (Makes me hesitate working on analog+ if the first thing I see hints a more changes to come. :o )

I'll let you know if I see anything else interesting.

Title: Re:Mame .84u1 Released
Post by: Howard_Casto on July 09, 2004, 04:44:39 am

Hmm... perhaps I am correct in assuming that they are trying to phase out non-standardized input ports then.

Maybe the time has finally come to start phasing the input part out of the cfg files.

Title: Re:Mame .84u1 Released
Post by: Minwah on July 09, 2004, 05:42:22 am

Quote from: Howard_Casto on July 09, 2004, 04:44:39 am

Maybe the time has finally come to start phasing the input part out of the cfg files.

Would be a good move IMO...

Would also be cool to see the Analog Settings stuff move from the CFG files to ctrlr ini's...

Title: Re:Mame .84u1 Released
Post by: john12301 on July 21, 2004, 10:47:03 am

I have the same problem. Do you still have it??

Quote from: Peale on July 05, 2004, 04:09:50 pm

Hm, just tried compiling it with mame32 support, here's what I got:

Code: [Select]
H:\MAME84~1>make WINUI=1 SUFFIX=32 Compiling src/ui/m32util.c... src/ui/m32util.c: In function `DriverUsesTrackball': src/ui/m32util.c:401: `IPF_MASK' undeclared (first use in this function) src/ui/m32util.c:401: (Each undeclared identifier is reported only once src/ui/m32util.c:401: for each function it appears in.) src/ui/m32util.c: In function `DriverUsesLightGun': src/ui/m32util.c:438: `IPF_MASK' undeclared (first use in this function) make: *** [obj/mame32/ui/m32util.o] Error 1

Title: Re:Mame .84u1 Released
Post by: SirPeale on July 21, 2004, 01:02:33 pm

Nope! John IV updated the source, so you'll have to download the Mame32 source for the 'u' version. After that, worked like a charm.