Re: [Xmame] FC6 x86_64 and sdlmame / QMC2

[Julian Sikorski]

I believe that SDLMAME-specific questions should go to the board
(http://www.bannister.org/forums/ubbthreads.php?ubb=postlistBoard=8page=1),
as you will find more users there.
As for QMC2, I've done some smoke tests and it seems to work nice. I
have some suggestions, though:
1. Could you add support for mameinfo.dat/history.dat?
2. Tools - Check ROMs does not work well. It has listed some of the
complete roms as Unknown, probably due to the fact that some of them
have ROM NEEDS REDUMP or NO GOOD DUMP KNOWN status. On the other hand,
ksys573 games were listed as Incorrect, although only the bios present
in rom directory. All ksys573 roms are marked as BAD DUMP, though.
3. An option to use parent previews for clones would make the frontend
mametitles-friendly.

Regards,
JS

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Front End for SDLMame?

[Julian Sikorski]

R. Reucher napisał(a):
 Hi,
 
 On Mi, Oktober 18, 2006 15:00, Julian Sikorski wrote:
 qmamecat2 partially works with sldmame too. And because it is configured via
 xml files, making it work better should be moderately easy task
 Well, QMC2 0.1.b5 should work just fine with xmame.sdl. I see no major
 troubles at least... but I only tried until xmame 0.106.
 
 Yes, if new or changed options exist for sdl-mame (since 0.106), the xml
 template needs to be updated to fully/correctly support them.
 
 See http://www.mamewold.net/mamecat/
 
 Cheers, René
Erm, I'm not sure you understood us correctly. sdlmame is an new port
done by Arbee and Olivier Galibert:
http://rbelmont.mameworld.info/?page_id=163 and not xmame compliled to
use SDL for various things.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Front End for SDLMame?

[Julian Sikorski]

Matthias Saou napisał(a):
 Frank Cox wrote :
 
 On Tue, 17 Oct 2006 17:34:52 -0400
 c.s.h. [EMAIL PROTECTED] wrote:

 Do any of the linux mame front ends work with SDLMame?
 http://it.geocities.com/pinguinogoloso/
 
 A frontend in tcl/tk hosted on geocities!? Ugh :-)
 
 And The web site you are trying to access has exceeded its allocated
 data transfer. now it seems.
 
 It would seem so trivial to make a simple yet powerful frontend in some
 nicer looking scripting language, in pygtk for instance.
 Unfortunately, it's way passed my basic skills :-p
 
 Matthias
 
qmamecat2 partially works with sldmame too. And because it is configured
via xml files, making it work better should be moderately easy task

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] ready to check out sdlmame, but how?

[Julian Sikorski]

theGREENzebra napisał(a):
 So, recently (a few minutes ago?) I wanted to check out sdlmame and
 hans' patches, but I 404 on all of the urls in his email. Is there a new
 spot I should be looking?
 
 B
Sdlmame has a new home at one of http://rbelmont.mameworld.info, so you
should be able to grab the 0.109u2 source from there.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] 0106u3 compilation patch -nt-

[Julian Sikorski]

0106u3.diff.bz2
Description: application/bzip

[Xmame] more 0.103u2 problems

[Julian Sikorski]

Well, it seems that 0.103u2 needs a bit more work than my compilation
patch. The command

/usr/local/bin/xmame.x11 -noloadconfig -listxml 2

which is invoked by kxmame while creating gamelist, slows system down to
an unusable level. There were some config file parsing changes made,
maybe they are the reason? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] more 0.103u2 problems

[Julian Sikorski]

Julian Sikorski napisał(a):
 Well, it seems that 0.103u2 needs a bit more work than my compilation
 patch. The command
 
 /usr/local/bin/xmame.x11 -noloadconfig -listxml 2
 
 which is invoked by kxmame while creating gamelist, slows system down to
 an unusable level. There were some config file parsing changes made,
 maybe they are the reason? Greets.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Here is what Aaron wrote:
The xmame code needs to be updated to call init_resource_tracking()
before calling the function that generates the XML output.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] 0.106u2 compitlation patch

[Julian Sikorski]

Attached a patch that removes translucency option, as it no longer
compiles with 0.106u2. Btw, the features Aaron's new rendering system
will offer seem to be awesome, it would me nice it at least some of them
were ported to unix. Greets.


0106u2.diff.bz2
Description: application/bzip

Re: [Xmame] some aspect ratio questions

[Julian Sikorski]

Hans de Goede napisał(a):
 
 With DGA the code will show some frames twice when the monitor refresh
 rate is higher then the games, and drop some frames when vica versa.
 
 Regards,
 
 Hans
 

Would it be a problem to add the same feature (which is mentioned as
method 3 in the article) to xvideo/opengl drivers, or is it possible
with dga only?

Now, back to the aspect ratio. Is the 4:3 arcade monitor size hard-coded
for single monitor horizontal games (vertical ones have 3:4, dual screen
ones 6:3, etc.) ? I'm asking because it is the one I'm getting as
gameboy output, and IIRC its screen was square.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] some aspect ratio questions

[Julian Sikorski]

Hi. I have some questions about -keepaspect and -displayaspectratio
options. To make the games look like in the arcade, I should use -ka
switch, right? This would mean that games with weird resolutions, e.g.
400x254 (mitwunit) were originally stretched in the arcade, or the
monitors used did not have square pixels.
Also, do I understand the purpose of -dar switch correctly? Is it used
to tell xmame the shape of pixels on the monitor?

Thanks for the clarification in advance.

P.S.
Lawrence, I think you've forgotten to commit src/unix/sound.c together
with other 0.106u1 fixes.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] some aspect ratio questions

[Julian Sikorski]

Hans de Goede napisał(a):
 
 Julian Sikorski wrote:
 Hi. I have some questions about -keepaspect and -displayaspectratio
 options. To make the games look like in the arcade, I should use -ka
 switch, right? This would mean that games with weird resolutions, e.g.
 400x254 (mitwunit) were originally stretched in the arcade, or the
 monitors used did not have square pixels.
 Correct
 
 Also, do I understand the purpose of -dar switch correctly? Is it used
 to tell xmame the shape of pixels on the monitor?
 nope, its used to tell xmame the shape of the monitor, so for a normal
 montior it would be 4:3=1.33 and for a widescreen 16:9, etc.
 
 Regards,
 
 Hans
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Now it is finally clear. So it means that using 1280x1024 on a normal
monitor leads to wrong aspect ratio.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] Aaron broke everything once again ;)

[Julian Sikorski]

As a result, MESS CVS ceased to compile. It stops here:

[OSDEPEND] Compiling src/unix/sound.c ...
src/unix/sound.c: In function ‘sound_update_refresh_rate’:
src/unix/sound.c:36: error: invalid operands to binary /
src/unix/sound.c: In function ‘osd_sound_enable’:
src/unix/sound.c:94: error: invalid operands to binary /
src/unix/sound.c:102: error: invalid operands to binary /
make: *** [xmess.obj/unix.x11/sound.o] Error 1

It looks like video code update can break sound compilation ;)

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Aaron broke everything once again ;)

[Julian Sikorski]

Julian Sikorski napisał(a):
 As a result, MESS CVS ceased to compile. It stops here:
 
 [OSDEPEND] Compiling src/unix/sound.c ...
 src/unix/sound.c: In function ‘sound_update_refresh_rate’:
 src/unix/sound.c:36: error: invalid operands to binary /
 src/unix/sound.c: In function ‘osd_sound_enable’:
 src/unix/sound.c:94: error: invalid operands to binary /
 src/unix/sound.c:102: error: invalid operands to binary /
 make: *** [xmess.obj/unix.x11/sound.o] Error 1
 
 It looks like video code update can break sound compilation ;)
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Here is the patch fixing the compilation


0106u1.diff.bz2
Description: application/bzip

Re: [Xmame] full sreen problems

[Julian Sikorski]

Frank Claycomb napisał(a):
 i was wondering if someone could please explain to me how to get xmame
 into fullscreen.  i tried the -fullscreen option but it is not working
 for me.  i even did the left alt and page-down and it still didnt work.
 
 any help would be greatly appreciated
 
 -Frank
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Which video mode are you using?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] mess cvs does not compile

[Julian Sikorski]

I tried to compile mess cvs today. Here is what I got:

[MESS] Compiling mess/vidhrdw/m6847.c ...
mess/vidhrdw/m6847.c: In function ‘m6847_init’:
mess/vidhrdw/m6847.c:1847: warning: implicit declaration of function
‘add_full_refresh_callback’
mess/vidhrdw/m6847.c: In function ‘video_update_m6847’:
mess/vidhrdw/m6847.c:1990: error: ‘do_skip’ undeclared (first use in
this function)
mess/vidhrdw/m6847.c:1990: error: (Each undeclared identifier is
reported only once
mess/vidhrdw/m6847.c:1990: error: for each function it appears in.)
make: *** [xmess.obj/mess/vidhrdw/m6847.o] Error 1

I guess some include is missing, but which one?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] mess cvs does not compile

[Julian Sikorski]

Lawrence Gold napisał(a):
 Julian Sikorski wrote:
 I tried to compile mess cvs today. Here is what I got:

 [MESS] Compiling mess/vidhrdw/m6847.c ...
 mess/vidhrdw/m6847.c: In function ‘m6847_init’:
 mess/vidhrdw/m6847.c:1847: warning: implicit declaration of function
 ‘add_full_refresh_callback’
 mess/vidhrdw/m6847.c: In function ‘video_update_m6847’:
 mess/vidhrdw/m6847.c:1990: error: ‘do_skip’ undeclared (first use in
 this function)
 mess/vidhrdw/m6847.c:1990: error: (Each undeclared identifier is
 reported only once
 mess/vidhrdw/m6847.c:1990: error: for each function it appears in.)
 make: *** [xmess.obj/mess/vidhrdw/m6847.o] Error 1

 I guess some include is missing, but which one?
 
 No such problem here.  You might have done an update when someone was in
 the middle of committing.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Got it to work, it was some problem on my side. Btw, I have some questions:
-what are files in artwork dir for?
-why checking out messonly fetches mame tree?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] yet another heads up

[Julian Sikorski]

This time the thing is connected with change how 0.105u1 handles clones:

[OSDEPEND] Compiling src/unix/video.c ...
src/unix/video.c: In function `osd_create_display':
src/unix/video.c:558: error: structure has no member named `clone_of'
--snip--
src/unix/video.c:567: error: structure has no member named `clone_of'
make: *** [xmame.obj/unix.x11/video.o] Error 1

Happy easter, xmame devs!

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] xmess 0.105 does not build

[Julian Sikorski]

Here is the console output:

xmess.obj/unix.x11/fileio.o: In function `init_errorlog':
fileio.c:(.text+0x43): undefined reference to `options'
collect2: ld returned 1 exit status
make: *** [imgtool] Error 1

I have unix tree from mess cvs and win mess 0.105 source. xmame 0.105
built fine. Just a heads up.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] some problems with 0.104u4

[Julian Sikorski]

Luo Yong napisał(a):
 Here's the problem:
 
 src/cpu/m68000/m68kmame.h:8:20: driver.h: No such file or directory
 src/cpu/m68000/m68kmame.h:9:22: cpuintrf.h: No such file or directory
 src/cpu/m68000/m68kmame.h:11:22: debugger.h: No such file or directory
 src/cpu/m68000/m68000.h:4:21: osd_cpu.h: No such file or directory
 
 These files might be placed in wrong directory.

The mentioned files are present in mame tree in src, src, src/debug and
src/unix respectively. My bet is that something is wrong with include
dirs. Btw, I'm using unix.mak from latest mess cvs.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] some problems with 0.104u4

[Julian Sikorski]

Have a look here. Something strange is happening. Isn't the space after
 gcc too long?
[EMAIL PROTECTED] mame]$ LANG=en_GB make
/opt/gcc34/bin/gcc   -std=gnu89 -Wall -Wno-unused -O3 -march=prescott
-Ixmame.obj/cpu/m68000 -c src/cpu/m68000/m68kmake.c -o
xmame.obj/cpu/m68000/m68kmake.o
M68K make src/cpu/m68000/m68kmake.c...
Generating M68K source files...

Musashi v3.3 68000, 68008, 68010, 68EC020, 68020 emulator
Copyright 1998-2000 Karl Stenerud ([EMAIL PROTECTED])

Generated 1964 opcode handlers from 515 primitives
Generating M68K source files...
xmame.obj/cpu/m68000/m68kmake xmame.obj/cpu/m68000 src/cpu/m68000/m68k_in.c

Musashi v3.3 68000, 68008, 68010, 68EC020, 68020 emulator
Copyright 1998-2000 Karl Stenerud ([EMAIL PROTECTED])

Generated 1964 opcode handlers from 515 primitives
Compiling src/cpu/m68000/m68kcpu.c...

/opt/gcc34/bin/gcc   -std=gnu89 -Wall -Wno-unused -O3 -march=prescott
-Ixmame.obj/cpu/m68000 -c src/cpu/m68000/m68kcpu.c -o
xmame.obj/cpu/m68000/m68kcpu.o
In file included from src/cpu/m68000/m68k.h:363,
 from src/cpu/m68000/m68kcpu.h:29,
 from src/cpu/m68000/m68kcpu.c:36:
src/cpu/m68000/m68kmame.h:8:20: driver.h: No such file or directory
src/cpu/m68000/m68kmame.h:9:22: cpuintrf.h: No such file or directory
src/cpu/m68000/m68kmame.h:11:22: debugger.h: No such file or directory
In file included from src/cpu/m68000/m68kmame.h:12,
 from src/cpu/m68000/m68k.h:363,
 from src/cpu/m68000/m68kcpu.h:29,
 from src/cpu/m68000/m68kcpu.c:36:
src/cpu/m68000/m68000.h:4:21: osd_cpu.h: No such file or directory
In file included from src/cpu/m68000/m68kmame.h:12,
 from src/cpu/m68000/m68k.h:363,
 from src/cpu/m68000/m68kcpu.h:29,
 from src/cpu/m68000/m68kcpu.c:36:
src/cpu/m68000/m68000.h:18: error: `CPUINFO_PTR_CPU_SPECIFIC' undeclared
here (not in a function)
src/cpu/m68000/m68000.h:18: error: enumerator value for
`CPUINFO_PTR_M68K_RESET_CALLBACK' not integer constant
src/cpu/m68000/m68000.h:29: error: parse error before offs_t
src/cpu/m68000/m68000.h:29: warning: no semicolon at end of struct or union
src/cpu/m68000/m68000.h:30: error: parse error before '*' token
src/cpu/m68000/m68000.h:30: warning: type defaults to `int' in
declaration of `UINT8'
src/cpu/m68000/m68000.h:30: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:30: error: `UINT8' declared as function
returning a function
src/cpu/m68000/m68000.h:30: warning: data definition has no type or
storage class
src/cpu/m68000/m68000.h:31: error: parse error before '*' token
src/cpu/m68000/m68000.h:31: warning: type defaults to `int' in
declaration of `UINT16'
src/cpu/m68000/m68000.h:31: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:31: error: `UINT16' declared as function
returning a function
src/cpu/m68000/m68000.h:31: warning: data definition has no type or
storage class
src/cpu/m68000/m68000.h:32: error: parse error before '*' token
src/cpu/m68000/m68000.h:32: warning: type defaults to `int' in
declaration of `UINT32'
src/cpu/m68000/m68000.h:32: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:32: error: `UINT32' declared as function
returning a function
src/cpu/m68000/m68000.h:32: warning: data definition has no type or
storage class
src/cpu/m68000/m68000.h:33: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:34: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:35: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:36: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:40: error: parse error before '*' token
src/cpu/m68000/m68000.h:40: warning: type defaults to `int' in
declaration of `UINT8'
src/cpu/m68000/m68000.h:40: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:40: error: `UINT8' declared as function
returning a function
src/cpu/m68000/m68000.h:40: warning: data definition has no type or
storage class
src/cpu/m68000/m68000.h:41: error: parse error before '*' token
src/cpu/m68000/m68000.h:41: warning: type defaults to `int' in
declaration of `UINT16'
src/cpu/m68000/m68000.h:41: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:41: error: `UINT16' declared as function
returning a function
src/cpu/m68000/m68000.h:41: warning: data definition has no type or
storage class
src/cpu/m68000/m68000.h:42: error: parse error before '*' token
src/cpu/m68000/m68000.h:42: warning: type defaults to `int' in
declaration of `UINT32'
src/cpu/m68000/m68000.h:42: warning: parameter names (without types) in
function declaration
src/cpu/m68000/m68000.h:42: error: `UINT32' declared as function
returning a function

Re: [Xmame] rom comparaison assuption

[Julian Sikorski]

[EMAIL PROTECTED] napisał(a):
 P. Cizaire [EMAIL PROTECTED] écrit :
 Afaik SHA1 is enough, btw the tools you are planing to write already
 exists. there is clrmame and others, see mame rom manager
 
 yes those tools exists. but as I mentioned I'm a Mac User and linux PPC user
 (thus no Wine)
 clrmame does not run on MacOS and does not run in Linux ;-)
 
   Eric
 
 
How about Darwine? Or maybe mamory works ur MacOS? Or AdvanceSCAN?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0.104u3 does not compile... blame Aaron ;)

[Julian Sikorski]

Lawrence Gold napisał(a):
 Julian Sikorski wrote:
 
The first problem was connected with removed common.h - I have managed
to solve it. The second one it too difficult for me, though:
 
 
 The attached patch to the 0.104 src/unix should allow you to build.  I
 haven't tested it much, but it appears to work.
Seems to be working OK.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0.104u3 does not compile... blame Aaron ;)

[Julian Sikorski]

Lawrence Gold napisał(a):
 Julian Sikorski wrote:
 
The first problem was connected with removed common.h - I have managed
to solve it. The second one it too difficult for me, though:
 
 
 The attached patch to the 0.104 src/unix should allow you to build.  I
 haven't tested it much, but it appears to work.

Btw I have noticed that skip_disclaimer option is still present in
xmame. Wasn't it removed from the core?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0.104u3 does not compile... blame Aaron ;)

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Feb 24, 2006, at 1:19 AM, Julian Sikorski wrote:
 
 Btw I have noticed that skip_disclaimer option is still present in
 xmame. Wasn't it removed from the core?
 
 
 It doesn't appear to have been. The 0.104u3 patch references it in a 
 couple of places.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Well, it does not seem to do antything though. I have made a quick
browse through mameworld forums, and found this:

http://www.mameworld.info/ubbthreads/showflat.php?Cat=Board=emuadviceNumber=45852

According to Twisty, it was removed in 0.99u2. It is confirmed by the
changelog:

Removed -skip_disclaimer since it automatically goes away after the
first time execution. [Aaron Giles]

Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] eolith eolith16 drivers with FC4

[Julian Sikorski]

Frank Cox napisał(a):
 The eolith and eolith16 games crash with a segfault when compiled with -02 on
 Fedora Core 4.  Compiling with -01 seems to work, though.
 
The official supported compiler for mame is gcc 3.4.2. Fedora contains
4.0.2, which is known to cause problems, such as miscompilation of v60 core.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0104u2-game uses non-existent cpu?

[Julian Sikorski]

Julian Sikorski napisał(a):
 Julian Sikorski napisał(a):
 
I have managed to compile 0.104u2. The problem is that when trying to
run namcos11 or namcos22 (or probably any other game using
m37710/m37702) something similar appears:

[EMAIL PROTECTED] ~]$ xmame.x11 raveracw
GLINFO: loaded OpenGL library libGL.so!
GLINFO: loaded GLUlibrary libGLU.so!
GLINFO: glPolygonOffsetEXT (2): not implemented !
info: trying to parse: /usr/local/share/xmame/xmamerc
info: trying to parse: /home/xxx/.xmame/xmamerc
info: trying to parse: /usr/local/share/xmame/xmame-x11rc
info: trying to parse: /home/xxx/.xmame/xmame-x11rc
info: trying to parse: /usr/local/share/xmame/rc/raveracwrc
info: trying to parse: /home/xxx/.xmame/rc/raveracwrc
src/drivers/namcos22.c: ridgerac uses non-present CPU
src/drivers/namcos22.c: ridgeraj uses non-present CPU
src/drivers/namcos22.c: acedrvrw uses non-present CPU
src/drivers/namcos22.c: ridgera2 uses non-present CPU
src/drivers/namcos22.c: ridger2a uses non-present CPU
src/drivers/namcos22.c: ridger2b uses non-present CPU
src/drivers/namcos22.c: raveracw uses non-present CPU
src/drivers/namcos22.c: raveracj uses non-present CPU
src/drivers/namcos22.c: cybrcomm uses non-present CPU
src/drivers/namcos22.c: victlapw uses non-present CPU

Has Arbee made a mistage, or did I mess something up? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 
 I have compiled 0.104u2 once more. I believe someting has screwed up
 with m37702 cpu. All drivers which are using it fail to start. Any ideas
 waht can be wrong here? Thx in advance.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
It seems that I'm alone with this problem...

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0104u2-game uses non-existent cpu?

[Julian Sikorski]

Lawrence Gold napisał(a):
 Julian Sikorski wrote:
 
It seems that I'm alone with this problem...
 
 
 I don't see that problem here.  Have you done a clean build?  Could
 there be some files that are modified on your end?  You can check by
 running cvs -n update and seeing if any are marked with an M.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Yes, I have done a clean build. I have run prep-new-mame on win32
0.104u2 und unix 0.104 source, with 4 files gabbed from cvs: config.c,
xmess.c, fileio.c and fronthlp.c. I'll try to compile pure xmess cvs and
see what happens.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0104u2-game uses non-existent cpu?

[Julian Sikorski]

Julian Sikorski napisał(a):
 Lawrence Gold napisał(a):
 
Julian Sikorski wrote:


It seems that I'm alone with this problem...


I don't see that problem here.  Have you done a clean build?  Could
there be some files that are modified on your end?  You can check by
running cvs -n update and seeing if any are marked with an M.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 
 Yes, I have done a clean build. I have run prep-new-mame on win32
 0.104u2 und unix 0.104 source, with 4 files gabbed from cvs: config.c,
 xmess.c, fileio.c and fronthlp.c. I'll try to compile pure xmess cvs and
 see what happens.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

mess cvs works fine, I have to figure out what is wrong with my method
of preparing an xmame u release...

P.S.
I think src/unix/unix.mak should be synced with the one from 0.104 release.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0104u2-game uses non-existent cpu?

[Julian Sikorski]

Julian Sikorski napisał(a):
 Julian Sikorski napisał(a):
 
Lawrence Gold napisał(a):


Julian Sikorski wrote:



It seems that I'm alone with this problem...


I don't see that problem here.  Have you done a clean build?  Could
there be some files that are modified on your end?  You can check by
running cvs -n update and seeing if any are marked with an M.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame



Yes, I have done a clean build. I have run prep-new-mame on win32
0.104u2 und unix 0.104 source, with 4 files gabbed from cvs: config.c,
xmess.c, fileio.c and fronthlp.c. I'll try to compile pure xmess cvs and
see what happens.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 
 mess cvs works fine, I have to figure out what is wrong with my method
 of preparing an xmame u release...
 
 P.S.
 I think src/unix/unix.mak should be synced with the one from 0.104 release.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Ok, i have figured it out. for some reason cpu.mak patch got rejected.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0104u2-game uses non-existent cpu?

[Julian Sikorski]

Julian Sikorski napisał(a):
 I have managed to compile 0.104u2. The problem is that when trying to
 run namcos11 or namcos22 (or probably any other game using
 m37710/m37702) something similar appears:
 
 [EMAIL PROTECTED] ~]$ xmame.x11 raveracw
 GLINFO: loaded OpenGL library libGL.so!
 GLINFO: loaded GLUlibrary libGLU.so!
 GLINFO: glPolygonOffsetEXT (2): not implemented !
 info: trying to parse: /usr/local/share/xmame/xmamerc
 info: trying to parse: /home/xxx/.xmame/xmamerc
 info: trying to parse: /usr/local/share/xmame/xmame-x11rc
 info: trying to parse: /home/xxx/.xmame/xmame-x11rc
 info: trying to parse: /usr/local/share/xmame/rc/raveracwrc
 info: trying to parse: /home/xxx/.xmame/rc/raveracwrc
 src/drivers/namcos22.c: ridgerac uses non-present CPU
 src/drivers/namcos22.c: ridgeraj uses non-present CPU
 src/drivers/namcos22.c: acedrvrw uses non-present CPU
 src/drivers/namcos22.c: ridgera2 uses non-present CPU
 src/drivers/namcos22.c: ridger2a uses non-present CPU
 src/drivers/namcos22.c: ridger2b uses non-present CPU
 src/drivers/namcos22.c: raveracw uses non-present CPU
 src/drivers/namcos22.c: raveracj uses non-present CPU
 src/drivers/namcos22.c: cybrcomm uses non-present CPU
 src/drivers/namcos22.c: victlapw uses non-present CPU
 
 Has Arbee made a mistage, or did I mess something up? Greets.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

I have compiled 0.104u2 once more. I believe someting has screwed up
with m37702 cpu. All drivers which are using it fail to start. Any ideas
waht can be wrong here? Thx in advance.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] 0104u2-game uses non-existent cpu?

[Julian Sikorski]

I have managed to compile 0.104u2. The problem is that when trying to
run namcos11 or namcos22 (or probably any other game using
m37710/m37702) something similar appears:

[EMAIL PROTECTED] ~]$ xmame.x11 raveracw
GLINFO: loaded OpenGL library libGL.so!
GLINFO: loaded GLUlibrary libGLU.so!
GLINFO: glPolygonOffsetEXT (2): not implemented !
info: trying to parse: /usr/local/share/xmame/xmamerc
info: trying to parse: /home/xxx/.xmame/xmamerc
info: trying to parse: /usr/local/share/xmame/xmame-x11rc
info: trying to parse: /home/xxx/.xmame/xmame-x11rc
info: trying to parse: /usr/local/share/xmame/rc/raveracwrc
info: trying to parse: /home/xxx/.xmame/rc/raveracwrc
src/drivers/namcos22.c: ridgerac uses non-present CPU
src/drivers/namcos22.c: ridgeraj uses non-present CPU
src/drivers/namcos22.c: acedrvrw uses non-present CPU
src/drivers/namcos22.c: ridgera2 uses non-present CPU
src/drivers/namcos22.c: ridger2a uses non-present CPU
src/drivers/namcos22.c: ridger2b uses non-present CPU
src/drivers/namcos22.c: raveracw uses non-present CPU
src/drivers/namcos22.c: raveracj uses non-present CPU
src/drivers/namcos22.c: cybrcomm uses non-present CPU
src/drivers/namcos22.c: victlapw uses non-present CPU

Has Arbee made a mistage, or did I mess something up? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] make install suggestion

[Julian Sikorski]

Hi. I have noticed that make install installs only the emulator binaries
(xmame.x11, xmess.x11 and so on). In my opinion, it would be nice if
imgtool, romcmp, chdman and so on would be installed too. Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] unable to compile 0.103u5

[Julian Sikorski]

Hi. This is probably connected with Aaron's changes:

Made a clean-up pass over all the makefiles. rules.mak is gone now,
replaced by cpu.mak and sound.mak. mame.mak has been reorganized. All
the makefiles are now commented and should be easier to follow.
[Aaron Giles]

The proplen itself is as follows:

[EMAIL PROTECTED] mame]$ LANG=en_GB make
src/unix/unix.mak:243: src/rules.mak: No such file or directory
make: *** No rule to make target `src/rules.mak'.  Stop.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] kxmame 2.x to support xmess

[Julian Sikorski]

Toan T Nguyen napisał(a):
 Happy New Year everybody!
 
 Damn, it rains so much in LA. I decided let you all know that there's
 an unstable branch (named xmess) in kxmame CVS that supports xmess.
 Here is the mandatory screenshot.
 
 http://kde-apps.org/content/preview.php?preview=3id=28270file1=28270-1.jpgfile2=28270-2.pngfile3=28270-3.jpegname=kxmame
 
 Please give it a try (it's quite stable in my opinion). I need the
 feedback on the following isues:
 
 More systems tested: I'm able to test this on a few systems (NES,
 Genesis) but more testing is needed to make sure kxmame is able to run
 all systems that xmess supports.
 
 Better UI: I'm not very satisfied with the user interface. I'm looking
 for a way to keep kxmame interface simple yet, at the same time,
 allowing easy browsing of (potentially) large number of rom images.
 Ideas are welcomed.
 
 Translations: Due to the need to switch back and forth between xmame/xmess,
 kxmame cannot fully reuse gxmame messages anymore. New translations are 
 needed.
 
 Toan
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Other thing: xmess should store its config in ~/.xmess, not in ~/.xmame
(I have noticed this for cfg files, they go to ~/.xmame/cfg).

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] kxmame 2.x to support xmess

[Julian Sikorski]

Toan T Nguyen napisał(a):
 Hi,
 
 Thanks for the report. I put up kxmame-1.90 for download on sf.net. It
 supports zip file and properly uses .xmess/cfg (nvram, ini, ...)
 instead of .xmame/cfg when running xmess. Let me know how it goes.
 
 Toan
 
 On 1/3/06, Julian Sikorski [EMAIL PROTECTED] wrote:
 
Toan T Nguyen napisał(a):

Happy New Year everybody!

Damn, it rains so much in LA. I decided let you all know that there's
an unstable branch (named xmess) in kxmame CVS that supports xmess.
Here is the mandatory screenshot.

http://kde-apps.org/content/preview.php?preview=3id=28270file1=28270-1.jpgfile2=28270-2.pngfile3=28270-3.jpegname=kxmame

Please give it a try (it's quite stable in my opinion). I need the
feedback on the following isues:

More systems tested: I'm able to test this on a few systems (NES,
Genesis) but more testing is needed to make sure kxmame is able to run
all systems that xmess supports.

Better UI: I'm not very satisfied with the user interface. I'm looking
for a way to keep kxmame interface simple yet, at the same time,
allowing easy browsing of (potentially) large number of rom images.
Ideas are welcomed.

Translations: Due to the need to switch back and forth between xmame/xmess,
kxmame cannot fully reuse gxmame messages anymore. New translations are 
needed.

Toan

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame


Other thing: xmess should store its config in ~/.xmess, not in ~/.xmame
(I have noticed this for cfg files, they go to ~/.xmame/cfg).

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 ^fŚzf˘�)ŕ�+-^fŚzÚ2n�mÂ+-yÚ+�é!śÚ�ţÚ2n�mÂ+-yÚ+�é?�¨Ľ�Š˙�+-�wč˙�me==

Seems to be working okay/ Tell me when you are 'featurefull', I'll
update the transaltion then. Greets. Btw, kxmame (all branches) has some
problems with displaying Polish fonts in some places, for instance in
the title of rom loading window. ? signs appear instead of
Polish-specific characters. Maybe an encoding problem?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] kxmame 2.x to support xmess

[Julian Sikorski]

Toan T Nguyen napisał(a):
 Happy New Year everybody!
 
 Damn, it rains so much in LA. I decided let you all know that there's
 an unstable branch (named xmess) in kxmame CVS that supports xmess.
 Here is the mandatory screenshot.
 
 http://kde-apps.org/content/preview.php?preview=3id=28270file1=28270-1.jpgfile2=28270-2.pngfile3=28270-3.jpegname=kxmame
 
 Please give it a try (it's quite stable in my opinion). I need the
 feedback on the following isues:
 
 More systems tested: I'm able to test this on a few systems (NES,
 Genesis) but more testing is needed to make sure kxmame is able to run
 all systems that xmess supports.
 
 Better UI: I'm not very satisfied with the user interface. I'm looking
 for a way to keep kxmame interface simple yet, at the same time,
 allowing easy browsing of (potentially) large number of rom images.
 Ideas are welcomed.
 
 Translations: Due to the need to switch back and forth between xmame/xmess,
 kxmame cannot fully reuse gxmame messages anymore. New translations are 
 needed.
 
 Toan
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

There is no suppoer for zipped software (carts, disks, etc).

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] RB's changes in u4 cause xmame to hang

[Julian Sikorski]

I have noticed this behaviour for tekken3, so this issue may be
connected with h8/3002 update. Xmame hangs as soon as the window
appears, even before 'press any key' screen. It can't even be killed
with killall -9 xmame.x11. Does anybody experience the same issue?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] Xmame and kernel bug

[Julian Sikorski]

It seems that the problem is more serious. Here is the output of
/var/log messages of the first xmame.x11 exit. An the first look it
seems tobe some problem with new nvidia drivers.


Dec  9 21:47:19 DOMOWY kernel: [ cut here ]
Dec  9 21:47:19 DOMOWY kernel: kernel BUG at mm/page_alloc.c:1019!
Dec  9 21:47:19 DOMOWY kernel: invalid operand:  [#1]
Dec  9 21:47:19 DOMOWY kernel: SMP
Dec  9 21:47:19 DOMOWY kernel: Modules linked in: nvidia(U) cdemu(U)
ipv6 parport_pc lp parport autofs4 it87 hwmon_vid hwmon eeprom i2c_isa
sunrpc ipt_REJECT ipt_state ip_conntrack nfnetlink iptable_filter
ip_tables vfat fat nls_utf8 ntfs(U) yealink sd_mod dm_mod video button
battery ac uhci_hcd usb_storage scsi_mod ohci_hcd ehci_hcd shpchp
hw_random i2c_i801 i2c_core snd_intel8x0 snd_ac97_codec snd_ac97_bus
snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc
sk98lin floppy ext3 jbd
Dec  9 21:47:19 DOMOWY kernel: CPU:0
Dec  9 21:47:19 DOMOWY kernel: EIP:0060:[c0149730]Tainted: P
VLI
Dec  9 21:47:19 DOMOWY kernel: EFLAGS: 00210257   (2.6.14-1.1644_FC4smp)
Dec  9 21:47:19 DOMOWY kernel: EIP is at __free_pages+0x47/0x51
Dec  9 21:47:19 DOMOWY kernel: eax:    ebx:    ecx:
c146ea80   edx: c146ea80
Dec  9 21:47:19 DOMOWY kernel: esi:    edi:    ebp:
e35fa7b8   esp: ea06dee8
Dec  9 21:47:19 DOMOWY kernel: ds: 007b   es: 007b   ss: 0068
Dec  9 21:47:19 DOMOWY kernel: Process xmame.x11 (pid: 3535,
threadinfo=ea06d000 task=f7f4c030)
Dec  9 21:47:19 DOMOWY kernel: Stack: badc0ded ea6de380 fa0b0b37
0163  0100 ea6de380 e2d07be8
Dec  9 21:47:19 DOMOWY kernel:e2d07be8 ea088a80 fa0ad468
 fa0ed6e0 ea6de380  f6033000
Dec  9 21:47:19 DOMOWY kernel:f7acbe4c f7acbe80 c0155de6
e2d07b8c e2d07be8 f7984980 f79849d0 c01580a1
Dec  9 21:47:19 DOMOWY kernel: Call Trace:
Dec  9 21:47:19 DOMOWY kernel:  [fa0b0b37] nv_vm_free_pages+0xb6/0x109
[nvidia]
Dec  9 21:47:19 DOMOWY kernel:  [fa0ad468]
nv_kern_vma_release+0x7d/0x98 [nvidia]
Dec  9 21:47:19 DOMOWY kernel:  [c0155de6] remove_vm_struct+0x55/0x7b
Dec  9 21:47:19 DOMOWY kernel:  [c01580a1] exit_mmap+0x126/0x172
Dec  9 21:47:19 DOMOWY kernel:  [c011e459] mmput+0x20/0x97
Dec  9 21:47:19 DOMOWY kernel:  [c012329c] do_exit+0xe1/0x3e7
Dec  9 21:47:19 DOMOWY kernel:  [c0107dc6] do_syscall_trace+0x1e4/0x1f6
Dec  9 21:47:19 DOMOWY kernel:  [c01235f7] do_group_exit+0x29/0x91
Dec  9 21:47:19 DOMOWY kernel:  [c01039e1] syscall_call+0x7/0xb
Dec  9 21:47:19 DOMOWY kernel: Code: 2a f0 83 41 04 ff 0f 98 c0 84 c0 74
0c 85 db 75 10 89 c8 5b e9 14 f8 ff ff 5b 90 c3 8b 51 0c eb d8 89 da 89
c8 5b e9 72 f2 ff ff 0f 0b fb 03 30 98 33 c0 eb cc 85 c0 75 01 c3 05
00 00 00 40 c1
Dec  9 21:47:19 DOMOWY kernel:  1Fixing recursive fault but reboot is
needed!

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Xmame and kernel bug

[Julian Sikorski]

Julian Sikorski napisał(a):
 It seems that the problem is more serious. Here is the output of
 /var/log messages of the first xmame.x11 exit. An the first look it
 seems tobe some problem with new nvidia drivers.
 
 
 Dec  9 21:47:19 DOMOWY kernel: [ cut here ]
 Dec  9 21:47:19 DOMOWY kernel: kernel BUG at mm/page_alloc.c:1019!
 Dec  9 21:47:19 DOMOWY kernel: invalid operand:  [#1]
 Dec  9 21:47:19 DOMOWY kernel: SMP
 Dec  9 21:47:19 DOMOWY kernel: Modules linked in: nvidia(U) cdemu(U)
 ipv6 parport_pc lp parport autofs4 it87 hwmon_vid hwmon eeprom i2c_isa
 sunrpc ipt_REJECT ipt_state ip_conntrack nfnetlink iptable_filter
 ip_tables vfat fat nls_utf8 ntfs(U) yealink sd_mod dm_mod video button
 battery ac uhci_hcd usb_storage scsi_mod ohci_hcd ehci_hcd shpchp
 hw_random i2c_i801 i2c_core snd_intel8x0 snd_ac97_codec snd_ac97_bus
 snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device
 snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc
 sk98lin floppy ext3 jbd
 Dec  9 21:47:19 DOMOWY kernel: CPU:0
 Dec  9 21:47:19 DOMOWY kernel: EIP:0060:[c0149730]Tainted: P
 VLI
 Dec  9 21:47:19 DOMOWY kernel: EFLAGS: 00210257   (2.6.14-1.1644_FC4smp)
 Dec  9 21:47:19 DOMOWY kernel: EIP is at __free_pages+0x47/0x51
 Dec  9 21:47:19 DOMOWY kernel: eax:    ebx:    ecx:
 c146ea80   edx: c146ea80
 Dec  9 21:47:19 DOMOWY kernel: esi:    edi:    ebp:
 e35fa7b8   esp: ea06dee8
 Dec  9 21:47:19 DOMOWY kernel: ds: 007b   es: 007b   ss: 0068
 Dec  9 21:47:19 DOMOWY kernel: Process xmame.x11 (pid: 3535,
 threadinfo=ea06d000 task=f7f4c030)
 Dec  9 21:47:19 DOMOWY kernel: Stack: badc0ded ea6de380 fa0b0b37
 0163  0100 ea6de380 e2d07be8
 Dec  9 21:47:19 DOMOWY kernel:e2d07be8 ea088a80 fa0ad468
  fa0ed6e0 ea6de380  f6033000
 Dec  9 21:47:19 DOMOWY kernel:f7acbe4c f7acbe80 c0155de6
 e2d07b8c e2d07be8 f7984980 f79849d0 c01580a1
 Dec  9 21:47:19 DOMOWY kernel: Call Trace:
 Dec  9 21:47:19 DOMOWY kernel:  [fa0b0b37] nv_vm_free_pages+0xb6/0x109
 [nvidia]
 Dec  9 21:47:19 DOMOWY kernel:  [fa0ad468]
 nv_kern_vma_release+0x7d/0x98 [nvidia]
 Dec  9 21:47:19 DOMOWY kernel:  [c0155de6] remove_vm_struct+0x55/0x7b
 Dec  9 21:47:19 DOMOWY kernel:  [c01580a1] exit_mmap+0x126/0x172
 Dec  9 21:47:19 DOMOWY kernel:  [c011e459] mmput+0x20/0x97
 Dec  9 21:47:19 DOMOWY kernel:  [c012329c] do_exit+0xe1/0x3e7
 Dec  9 21:47:19 DOMOWY kernel:  [c0107dc6] do_syscall_trace+0x1e4/0x1f6
 Dec  9 21:47:19 DOMOWY kernel:  [c01235f7] do_group_exit+0x29/0x91
 Dec  9 21:47:19 DOMOWY kernel:  [c01039e1] syscall_call+0x7/0xb
 Dec  9 21:47:19 DOMOWY kernel: Code: 2a f0 83 41 04 ff 0f 98 c0 84 c0 74
 0c 85 db 75 10 89 c8 5b e9 14 f8 ff ff 5b 90 c3 8b 51 0c eb d8 89 da 89
 c8 5b e9 72 f2 ff ff 0f 0b fb 03 30 98 33 c0 eb cc 85 c0 75 01 c3 05
 00 00 00 40 c1
 Dec  9 21:47:19 DOMOWY kernel:  1Fixing recursive fault but reboot is
 needed!
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
It only happens for video mode 2.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Withh video-mode 1 and 2, some games are stretched by default

[Julian Sikorski]

Hans de Goede napisał(a):
 
 
 Julian Sikorski wrote:
 
 Hi. I have noticed this behaviour for psx and stv games for now. If
 video-mode 0 is used, htese games are not stretched. Is this the rifht
 behaviour? Greets.

 
 Actually Xvideo and opengl can do hardwarescaling and uee this to gain
 the exact ratio as specified in the driver, assuming that you have
 configured your monitor ratio correctly.
 
 Note that this can be turned off, see -help output,
 
 Regards,
 
 Hans
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Here is the config file I use. I have disabled keepaspect and set my
monitor ratio to 1.3, but the hwscaling is enabled by default.
Anyway, how is that that the driver specifies one resolution and video
is displayed at different one?


xmamerc.bz2
Description: application/bzip

Re: [Xmame] Withh video-mode 1 and 2, some games are stretched by default

[Julian Sikorski]

smf napisał(a):
 Anyway, how is that that the driver specifies one resolution and video
 is displayed at different one?
 
 
 The driver specifies a maximum resolution that it will use. It can
 change it to a lower one at runtime. You really need hardware stretching
 or the aspect ratio will not be maintained. For example PSX has a
 maximum resolution of 640x480 but it might change to 512x240, 384x480
 etc at run time. In theory you could switch resolutions when this
 happens, but that can lead to your monitor having to resync ( AFAIK only
 advance mame is the only port that might even attempt to do this ).
 
 Phill
 
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

OK. Seems to be clear now. Most of the times I run mame in a window, so
probably there will be no resync problem here. Normal video mode
switches resolutions at runtime if running in window, so how to make X11
 OpenGL ones do the same?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] Withh video-mode 1 and 2, some games are stretched by default

[Julian Sikorski]

Hi. I have noticed this behaviour for psx and stv games for now. If
video-mode 0 is used, htese games are not stretched. Is this the rifht
behaviour? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Re: dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 29, 2005, at 12:40 AM, Julian Sikorski wrote:
 
 Maybe we're getting somewhere? Moreover, a selinux and kernel update
 have arrived. I'll check them as soon as livna releases updated kernel
 modules. Greets.
 
 
 It's encouraging to see that that changed the behavior, but it also 
 means there could be a problem with xmame's osd_alloc_executable() 
 implementation or in the way that function is used by the core. I'll 
 have a look around and see if anything stands out.
 
 In the meantime, is there any chance you could try a non-se kernel  just
 to see if that makes the segfault go away?
 
 Thanks.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

What do you mean by non-se? There are three main kernels for FC: i386,
i686 and i686-smp. Now I'm using the smp one to benefit from HT.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Re: dynarec cores crash

[Julian Sikorski]

Carl M. Fongheiser napisał(a):
 Julian Sikorski wrote:
 
 I have enabled HAVE_MPROTECT, now the backtrace is different:

 (gdb) bt
 #0  0x08501f04 in drc_cache_reset (drc=0x0) at src/x86drc.c:114
 #1  0x0835ac3e in ppcdrc603_reset (param=0xab12c60)
at src/cpu/powerpc/ppcdrc.c:1135
 #2  0x080ac3fd in cpunum_reset (cpunum=0, param=0xab12c60,
irqack=0x80aa616 cpu_0_irq_callback) at src/cpuintrf.c:1460
 #3  0x080a68c2 in cpu_pre_run () at src/cpuexec.c:410
 #4  0x080a694b in cpu_run () at src/cpuexec.c:462
 #5  0x080fb6b1 in run_machine_core () at src/mame.c:598
 #6  0x080fb550 in run_machine () at src/mame.c:529
 #7  0x080fb268 in run_game (game=2968) at src/mame.c:361
 #8  0x09ed0aec in main (argc=2, argv=0xbfa6ec74) at src/unix/main.c:104
 (gdb)
  

 I'm seeing the same thing on my system.  I did some digging around, and
 found out that osd_alloc_executable() is returning NULL because the
 mprotect() call fails.  It's getting EINVAL.  Digging around even more,
 I found that Linux requires that the addr argument to be page-aligned. 
 I changed osd_alloc_executable() to use the following mmap call:
 
void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE | PROT_EXEC,
  MAP_ANON | MAP_SHARED, -1, 0);
 
 This works fine.
 
 The only problem with this is that munmap() requires a length argument,
 but osd_free_executable() doesn't have one.  Therefore, for the moment,
 I'm not freeing the memory.  I'm not sure how to fix this properly
 without doing some bookkeeping behind the scenes.
 
 Carl Fongheiser
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Hmm, I'm not C-savvy, so could you tell me what to change exactly? Sorry
for inconvienence.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Re: dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 29, 2005, at 10:47 AM, Julian Sikorski wrote:
 
 What do you mean by non-se? There are three main kernels for FC: i386,
 i686 and i686-smp. Now I'm using the smp one to benefit from HT.
 
 
 I meant a regular, non-SELinux kernel. I was under the impression  that
 you were using SELinux, but I may have misread one of the messages.
 
 At any rate, please try the code change I just posted. If it works, 
 I'll commit it to CVS and also add a FAQ entry on the homepage.
 
 Thanks!
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Yes, I am using selinux but there is no such thing here as se and non-se
kernels :(. I may just try to disable selinux.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Re: dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 29, 2005, at 10:47 AM, Julian Sikorski wrote:
 
 What do you mean by non-se? There are three main kernels for FC: i386,
 i686 and i686-smp. Now I'm using the smp one to benefit from HT.
 
 
 I meant a regular, non-SELinux kernel. I was under the impression  that
 you were using SELinux, but I may have misread one of the messages.
 
 At any rate, please try the code change I just posted. If it works, 
 I'll commit it to CVS and also add a FAQ entry on the homepage.
 
 Thanks!
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

OMG it works. Big HOOAH to all ml subscribers who halped to solve this
issue. It seems taht one of selinux updates must have changed something
with mprotect...

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Hans de Goede napisał(a):
 
 
 Julian Sikorski wrote:
 
 Hans de Goede napisał(a):

 nothing obvious in your updates list, have you tried an older kernel?

 Regards,

 Hans


 Both 2.6.13_1532 and 2.6.14 something. Maybe selinux? Is thre a command
 to disable it for a while to check?

 You get a segfault right, selinux doesn't cause that highly unlikely.
 
 Regards,
 
 Hans
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Agreed. However, I was expreiencing selinuxsegfaults problem a while
ago, but it always left a log in /var/log/messages. xmame problem leaves
nothing. I am out of ideas. Probably will have to wait till it fixes
itself automagically with some update/fc5 :(

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Re: dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 28, 2005, at 2:29 AM, Adam D. Moss wrote:
 
 Julian is using a processor (implied by -march=prescott) which  supports
 the NX bit.  SELinux (or a kernel reconfig, or Linux 2.6.8+ by  default)
 may very well be configured to enable no-execute on process data  pages,
 which is a nice security move but would cause a fault as soon as a
 process jumps to dynamically generated code in a data/heap area,
 as I would guess dynarec cores and many other JITs do.

 I think that execute-protection can be lowered by mmapping the
 appropriate area with PROT_EXEC, or using mprotect, though I've
 never had the hardware to try.
 
 
 Good idea.  I'd forgotten about the NX bit.
 
 Julian: Look for HAVE_MPROTECT in the makefile.  I don't think this  has
 ever been tested, so you'll be a guinea pig.  :-)
 
 Thanks.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

I have enabled HAVE_MPROTECT, now the backtrace is different:

(gdb) bt
#0  0x08501f04 in drc_cache_reset (drc=0x0) at src/x86drc.c:114
#1  0x0835ac3e in ppcdrc603_reset (param=0xab12c60)
at src/cpu/powerpc/ppcdrc.c:1135
#2  0x080ac3fd in cpunum_reset (cpunum=0, param=0xab12c60,
irqack=0x80aa616 cpu_0_irq_callback) at src/cpuintrf.c:1460
#3  0x080a68c2 in cpu_pre_run () at src/cpuexec.c:410
#4  0x080a694b in cpu_run () at src/cpuexec.c:462
#5  0x080fb6b1 in run_machine_core () at src/mame.c:598
#6  0x080fb550 in run_machine () at src/mame.c:529
#7  0x080fb268 in run_game (game=2968) at src/mame.c:361
#8  0x09ed0aec in main (argc=2, argv=0xbfa6ec74) at src/unix/main.c:104
(gdb)

The othe with HAVE_MPROTECT disabled:

(gdb) bt
#0  0x08502056 in drc_execute (drc=0xd47e908) at src/x86drc.c:156
#1  0x0835ac66 in ppcdrc603_execute (cycles=83)
at src/cpu/powerpc/ppcdrc.c:1155
#2  0x080ac343 in cpunum_execute (cpunum=0, cycles=83)
at src/cpuintrf.c:1444
#3  0x080a74b8 in cpu_timeslice () at src/cpuexec.c:1042
#4  0x080a6951 in cpu_run () at src/cpuexec.c:477
#5  0x080fb671 in run_machine_core () at src/mame.c:598
#6  0x080fb510 in run_machine () at src/mame.c:529
#7  0x080fb228 in run_game (game=2968) at src/mame.c:361
#8  0x09ed0a76 in main (argc=2, argv=0xbfe6ad84) at src/unix/main.c:104
(gdb)

Maybe we're getting somewhere? Moreover, a selinux and kernel update
have arrived. I'll check them as soon as livna releases updated kernel
modules. Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Julian Sikorski napisał(a):
 Hans de Goede napisał(a):
 
Could be, if the problem only happens when a certain access pattern
happens. I've seen stranger problems.

Regards,

Hans
 
 
 Memtest86+ was running for almost nine hours, 28 tests passed, no errors
 found.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

I's probably not a memmory problem. As for fedora updates, I noticed the
breakage at 5th November 2005. Here is my yum.log:

Oct 11 17:17:17 (yumex) Updated: wget.i386 1.10.1-4.fc4
Oct 15 09:07:01 (yumex) Updated: openssl.i686 0.9.7f-7.10
Oct 15 09:07:02 (yumex) Updated: info.i386 4.8-4.1
Oct 15 09:07:05 (yumex) Updated: lftp.i386 3.2.1-4_FC4
Oct 15 09:07:07 (yumex) Updated: openssl097a.i386 0.9.7a-3.1
Oct 15 09:07:09 (yumex) Updated: texinfo.i386 4.8-4.1
Oct 15 09:07:18 (yumex) Updated: openssl-devel.i386 0.9.7f-7.10
Oct 18 18:35:19 (yumex) Updated: wget.i386 1.10.2-0.fc4
Oct 18 18:35:21 (yumex) Updated: yumex.noarch 0.42-7.0.fc4
Oct 18 18:35:56 (yumex) Updated: selinux-policy-targeted.noarch 1.27.1-2.6
Oct 18 18:35:58 (yumex) Updated: dhclient.i386 10:3.0.2-24.FC4
Oct 19 12:16:01 Erased: yumex
Oct 19 12:16:51 Installed: yumex.noarch 0.42-7.0.fc4
Oct 19 20:17:34 (yumex) Installed: kasumi.i386 0.9-4.fc4
Oct 19 20:17:37 (yumex) Updated: scim-anthy.i386 0.7.1-1.fc4
Oct 19 20:17:45 (yumex) Updated: d4x.i386 2.5.5-1.fc4
Oct 19 20:59:11 (yumex) Installed: lm_sensors-devel.i386 2.8.8-5
Oct 19 20:59:13 (yumex) Installed: ksensors.i386 0.7.3-3
Oct 19 21:14:22 (yumex) Installed: gkrellm.i386 2.2.4-4
Oct 19 21:14:23 (yumex) Installed: gkrellm-devel.i386 2.2.4-4
Oct 21 12:45:55 (yumex) Installed: kernel-smp.i686 2.6.13-1.1532_FC4
Oct 21 12:47:38 (yumex) Installed: kernel-smp-devel.i686 2.6.13-1.1532_FC4
Oct 21 15:01:13 Installed: xorg-x11-Mesa-libGLU.i386 6.8.2-37.FC4.49.2
Oct 21 19:21:40 (yumex) Updated: gimp-help.noarch 2-0.1.0.9.0.fc4.1
Oct 22 08:00:53 (yumex) Updated: libdvdcss.i386 1.2.9-0.lvn.1.4
Oct 22 08:00:54 (yumex) Updated: libdvdcss-devel.i386 1.2.9-0.lvn.1.4
Oct 22 08:04:37 (yumex) Installed:
kernel-module-ntfs-2.6.13-1.1532_FC4smp.i686 2.1.22-0.lvn.3.4
Oct 22 08:12:31 Installed: nvidia-glx.i386 1.0.7676-0.lvn.2.4
Oct 22 08:12:33 Installed:
kernel-module-nvidia-2.6.13-1.1532_FC4smp.i686 1.0.7676-0.lvn.2.4
Oct 22 08:29:55 (yumex) Installed: fonts-ISO8859-2-100dpi.noarch 1.0-14
Oct 22 08:29:59 (yumex) Installed: fonts-ISO8859-2-75dpi.noarch 1.0-14
Oct 22 09:01:54 (yumex) Installed: fedora-rpmdevtools.noarch 1.2-1.fc4
Oct 23 22:20:02 Installed: freetype.i386 2.1.9-2
Oct 25 08:13:31 (yumex) Updated: logwatch.noarch 7.0-1.fc4
Oct 25 22:30:00 Installed: gnu-crypto-jce-jdk1.4.noarch 2.0.1-1jpp_5fc
Oct 25 22:30:01 Installed: gnu-crypto-sasl-jdk1.4.noarch 2.0.1-1jpp_5fc
Oct 25 22:30:03 Installed: gnu-crypto.noarch 2.0.1-1jpp_5fc
Oct 25 22:30:05 Installed: gjdoc.i386 0.7.5-3
Oct 25 22:30:08 Installed: java-1.4.2-gcj-compat.i386
1.4.2.0-40jpp_31rh.FC4.2
Oct 25 22:31:03 Installed: openoffice.org-core.i386 1:2.0.0-3.2.1
Oct 25 22:31:04 Installed: jessie.noarch 1.0.0-8
Oct 25 22:41:29 (yumex) Installed: libwpd.i386 0.8.2-1.fc4
Oct 25 22:41:36 (yumex) Installed: openoffice.org-calc.i386 1:2.0.0-3.2.1
Oct 25 22:41:38 (yumex) Installed: openoffice.org-math.i386 1:2.0.0-3.2.1
Oct 25 22:41:43 (yumex) Installed: openoffice.org-writer.i386 1:2.0.0-3.2.1
Oct 25 22:41:51 (yumex) Installed: openoffice.org-impress.i386 1:2.0.0-3.2.1
Oct 25 22:41:53 (yumex) Installed: openoffice.org-draw.i386 1:2.0.0-3.2.1
Oct 25 22:52:34 Erased: gjdoc
Oct 25 22:52:35 Erased: openoffice.org-calc
Oct 25 22:52:37 Erased: openoffice.org-math
Oct 25 22:52:38 Erased: openoffice.org-writer
Oct 25 22:52:40 Erased: java-1.4.2-gcj-compat
Oct 25 22:52:41 Erased: openoffice.org-impress
Oct 25 22:52:46 Erased: openoffice.org-core
Oct 25 22:52:56 Erased: openoffice.org-draw
Oct 25 22:52:57 Erased: libwpd
Oct 25 22:52:58 Erased: jessie
Oct 25 22:53:53 Erased: gnu-crypto
Oct 25 22:53:55 Erased: gnu-crypto-sasl-jdk1.4
Oct 25 22:53:58 Erased: gnu-crypto-jce-jdk1.4
Oct 27 08:08:09 (yumex) Updated: bind-libs.i386 24:9.3.1-14_FC4
Oct 27 08:08:11 (yumex) Updated: bind-utils.i386 24:9.3.1-14_FC4
Oct 27 08:08:15 (yumex) Updated: bind.i386 24:9.3.1-14_FC4
Oct 27 08:08:21 (yumex) Updated: gawk.i386 3.1.4-5.3
Oct 27 08:08:23 (yumex) Updated: sudo.i386 1.6.8p8-2.3
Oct 27 08:08:33 (yumex) Updated: krusader.i386 1.60.0-4.fc4
Oct 27 08:08:35 (yumex) Updated: mt-st.i386 0.9b-1.fc4
Oct 27 20:28:32 (yumex) Installed: kdeedu.i386 3.4.2-0.fc4.2
Oct 27 20:28:32 (yumex) Installed: kdeedu-devel.i386 3.4.2-0.fc4.2
Oct 27 21:30:45 Erased: libvisual-devel
Oct 27 21:30:47 Erased: libvisual-plugins
Oct 27 21:30:50 Erased: libvisual
Oct 28 14:50:00 (yumex) Updated: esound.i386 1:0.2.36-0.fc4.1
Oct 28 14:50:06 (yumex) Updated: pam.i386 0.79-9.6
Oct 28 14:50:07 (yumex) Updated: esound-devel.i386 1:0.2.36-0.fc4.1
Oct 28 14:50:09 (yumex) Updated: fedora-rpmdevtools.noarch 1.3-1

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Hans de Goede napisał(a):
 nothing obvious in your updates list, have you tried an older kernel?
 
 Regards,
 
 Hans
 

Both 2.6.13_1532 and 2.6.14 something. Maybe selinux? Is thre a command
to disable it for a while to check?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 Julian Sikorski wrote:
 

 I surrender :( I have no idea what might have broken drc cores. Any help
 would be appreciated.
 
 
 In case it isn't a hardware problem as Hans suggests, is there any
 possibility you could try some older releases to see if it works in
 them?  If it does, then you could narrow it down further by trying some
 intermediate u builds.
 
 Thanks.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
The problem is that hte segfault is most likely caused by one of fedo

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Hans de Goede napisał(a):
 
 
 Julian Sikorski wrote:
 
 Julian Sikorski napisał(a):

 Lawrence Gold napisał(a):

 On Nov 17, 2005, at 3:43 PM, Julian Sikorski wrote:


 Did this crash occur in 0.101, or just since 0.101u5?


 If you'd like to get u5, It is still mon mamedev.com:
 http://mamedev.com/updates/0101u5_diff.zip
 same as other u releases.


 I looked at the diff for u5 in MESS CVS this morning, and it doesn't
 seem the change should have any effect:

 +#define _prefetch_m8abs(type, addr) \
 +do { OP1(0x0f); OP1(0x18); MODRM_MABS(type, addr); } while (0)
 +#define _prefetch_m8bd(type, base, disp) \
 +do { OP1(0x0f); OP1(0x18); MODRM_MBD(type, base, disp); } while (0)
 +
 +
 +

 As far as I can tell, _prefetch_m8abs and _prefetch_m8bd aren't used
 anywhere, unless through some macro magic that isn't apparent from a
 casual glance. Have you tried reverting just the change to x86drc.h  to
 see if it fixes the crash?


 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame

 Hmm, something is wrong with my box rather than with mame. I have
 compiled vanilla 0.101 just in case, but it segfaults with the same
 backtrace. And I do remember myself checking model3 games after Aaron's
 chages to memroy system in u1 and model3.c games were working. Now I
 just have to figure out which update broke mame.

 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame


 I surrender :( I have no idea what might have broken drc cores. Any help
 would be appreciated.

 
 What hardware are you using and what version of Fedora are you running
 exactly?
 
 I myself have an x86_64 with both an x86_64 and an i386 version of
 Rawhide installed I can try reproducing it. If I succeed its a Fedora
 problem, if not it might be a hardware problem (which imho is more likely).
 
 You could also try running memtest86 on your box, just leave it running
 for a night. Another option is the old burnit kernel compile script
 which compiles kernels non-stop and compares them to see if you've got
 any hardware problems in my experience burnit is the best way to find
 CPU/mem related problems. Dunno if burnit works 2ith the 2.6 kernel
 otherwise just download an old kernel source tarball.
 
 Regards,
 
 Hans
 
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
I am using up-to-date fedora core 4 on x86 (P4 3.0E). I think that it is
a problem with one of fedora updates, but I may be wrong. Do you thnk
that cpu/memory problem may cause a segfault of xmame every time and no
other problems?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Hans de Goede napisał(a):
 Could be, if the problem only happens when a certain access pattern
 happens. I've seen stranger problems.
 
 Regards,
 
 Hans

Memtest86+ was running for almost nine hours, 28 tests passed, no errors
found.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Julian Sikorski napisał(a):
 Lawrence Gold napisał(a):
 
On Nov 17, 2005, at 3:43 PM, Julian Sikorski wrote:


Did this crash occur in 0.101, or just since 0.101u5?


If you'd like to get u5, It is still mon mamedev.com:
http://mamedev.com/updates/0101u5_diff.zip
same as other u releases.


I looked at the diff for u5 in MESS CVS this morning, and it doesn't 
seem the change should have any effect:

+#define _prefetch_m8abs(type, addr) \
+do { OP1(0x0f); OP1(0x18); MODRM_MABS(type, addr); } while (0)
+#define _prefetch_m8bd(type, base, disp) \
+do { OP1(0x0f); OP1(0x18); MODRM_MBD(type, base, disp); } while (0)
+
+
+

As far as I can tell, _prefetch_m8abs and _prefetch_m8bd aren't used 
anywhere, unless through some macro magic that isn't apparent from a 
casual glance. Have you tried reverting just the change to x86drc.h  to
see if it fixes the crash?


___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 Hmm, something is wrong with my box rather than with mame. I have
 compiled vanilla 0.101 just in case, but it segfaults with the same
 backtrace. And I do remember myself checking model3 games after Aaron's
 chages to memroy system in u1 and model3.c games were working. Now I
 just have to figure out which update broke mame.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

I surrender :( I have no idea what might have broken drc cores. Any help
would be appreciated.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 17, 2005, at 3:43 PM, Julian Sikorski wrote:
 
 Did this crash occur in 0.101, or just since 0.101u5?


 If you'd like to get u5, It is still mon mamedev.com:
 http://mamedev.com/updates/0101u5_diff.zip
 same as other u releases.
 
 
 I looked at the diff for u5 in MESS CVS this morning, and it doesn't 
 seem the change should have any effect:
 
 +#define _prefetch_m8abs(type, addr) \
 +do { OP1(0x0f); OP1(0x18); MODRM_MABS(type, addr); } while (0)
 +#define _prefetch_m8bd(type, base, disp) \
 +do { OP1(0x0f); OP1(0x18); MODRM_MBD(type, base, disp); } while (0)
 +
 +
 +
 
 As far as I can tell, _prefetch_m8abs and _prefetch_m8bd aren't used 
 anywhere, unless through some macro magic that isn't apparent from a 
 casual glance. Have you tried reverting just the change to x86drc.h  to
 see if it fixes the crash?
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

OMG. Reverting the changes does not help. I have run out of ideas now.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 17, 2005, at 3:43 PM, Julian Sikorski wrote:
 
 Did this crash occur in 0.101, or just since 0.101u5?


 If you'd like to get u5, It is still mon mamedev.com:
 http://mamedev.com/updates/0101u5_diff.zip
 same as other u releases.
 
 
 I looked at the diff for u5 in MESS CVS this morning, and it doesn't 
 seem the change should have any effect:
 
 +#define _prefetch_m8abs(type, addr) \
 +do { OP1(0x0f); OP1(0x18); MODRM_MABS(type, addr); } while (0)
 +#define _prefetch_m8bd(type, base, disp) \
 +do { OP1(0x0f); OP1(0x18); MODRM_MBD(type, base, disp); } while (0)
 +
 +
 +
 
 As far as I can tell, _prefetch_m8abs and _prefetch_m8bd aren't used 
 anywhere, unless through some macro magic that isn't apparent from a 
 casual glance. Have you tried reverting just the change to x86drc.h  to
 see if it fixes the crash?
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Hmm, something is wrong with my box rather than with mame. I have
compiled vanilla 0.101 just in case, but it segfaults with the same
backtrace. And I do remember myself checking model3 games after Aaron's
chages to memroy system in u1 and model3.c games were working. Now I
just have to figure out which update broke mame.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 16, 2005, at 11:25 AM, Julian Sikorski wrote:
 
 This is not mess-specific change and _not_ to ppc core as mips drc  also
 crashes with same backtrace. Moreover the crash appeared in vanilla u5
 with unix subdir from released xmame-0.101. That time there was a  change
 to src/x86drc.h. I have never bootstrapped a compiler, but I wan
 thinking about bootstarping gcc 3.4.4 just for compiling mame as it is
 the only supported build tool. Could you help me a bit?
 
 
 We're talking about two different problems: the MESS changes to the  PPC
 core ARE interfering with scudrace, quite apart from the segfault 
 you're seeing. When I use vanilla MAME 0.102 code, scudrace runs  fine;
 when I apply the MESS changes, scudrace ceases to run.
 
 As for bootstrapping GCC, it's surprisingly easy:
 
 1. Extract the source code from the GCC tarball.
 2. Create a build directory, preferably outside the GCC source tree; 
 let's call it build.
 3. Go into the build directory and run
 
 /path/to/gcc/sources/configure --prefix=/usr/local/gcc3  make 
 bootstrap
 
 4. make install
 
 You should then be able to set CC to /usr/local/gcc3/bin/gcc in your 
 makefile and build away. If this takes care of the problem, it's 
 anyone's guess as to the cause. I'd be kind of surprised if two 
 different Fedora compilers cause the same segfault, but who knows.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

It's not hte compiler. I have bootstrapped gcc 3.4.4 and it still
segfaults. But thx anyway, now I have the official mame build tool.
We'll have to investigate further. Maybe SMP issue? I'm using p4 ht and
an smp kernel.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 16, 2005, at 11:25 AM, Julian Sikorski wrote:
 
 This is not mess-specific change and _not_ to ppc core as mips drc  also
 crashes with same backtrace. Moreover the crash appeared in vanilla u5
 with unix subdir from released xmame-0.101. That time there was a  change
 to src/x86drc.h. I have never bootstrapped a compiler, but I wan
 thinking about bootstarping gcc 3.4.4 just for compiling mame as it is
 the only supported build tool. Could you help me a bit?
 
 
 Did this crash occur in 0.101, or just since 0.101u5?
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
u5. IMO it is connected with a change to /src/x86drc.h.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 16, 2005, at 11:25 AM, Julian Sikorski wrote:
 
 This is not mess-specific change and _not_ to ppc core as mips drc  also
 crashes with same backtrace. Moreover the crash appeared in vanilla u5
 with unix subdir from released xmame-0.101. That time there was a  change
 to src/x86drc.h. I have never bootstrapped a compiler, but I wan
 thinking about bootstarping gcc 3.4.4 just for compiling mame as it is
 the only supported build tool. Could you help me a bit?
 
 
 Did this crash occur in 0.101, or just since 0.101u5?
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

If you'd like to get u5, It is still mon mamedev.com:
http://mamedev.com/updates/0101u5_diff.zip
same as other u releases.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 Julian Sikorski wrote:
 

 Disabling -march=prescott also does not help here. Here is the backtrace
  from scudrace:
 
 
 Ah-hah, now we're getting somewhere.  Xmame built from MESS CVS is not
 segfaulting for me when I try scudrace, but it's dying with
 
 ctrl_w: 06, 0308, 
 
 printed to the console.  In a clean MAME 0.102 tree, it runs fine. Could
 you please edit src/cpu/powerpc/ppc_mem.c, search for exception: in
 the ppc_translate_address() function, and place return 1; just before
 that line?  This probably isn't a proper fix, but it gets scudrace
 working for me, and I'd like to know if it works for you too.
 
 Thanks.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

I can try after returning home, but you should also know that kinst
(mips drc) crashes with very similar backtrace.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 
 Ah-hah, now we're getting somewhere.  Xmame built from MESS CVS is not
 segfaulting for me when I try scudrace, but it's dying with
 
 ctrl_w: 06, 0308, 
 
 printed to the console.  In a clean MAME 0.102 tree, it runs fine. Could
 you please edit src/cpu/powerpc/ppc_mem.c, search for exception: in
 the ppc_translate_address() function, and place return 1; just before
 that line?  This probably isn't a proper fix, but it gets scudrace
 working for me, and I'd like to know if it works for you too.
 
 Thanks.

Changing the file has not helped, the backtrace is the same. As for the
mips backtrace, only the #1 is different as it is about mips core. Also
note that FC4 compilers are not vanilla ones, they contain some amount
of patches. Some more info is located also at mametesters forum, in
edited: dynarec cores segfault in u5 thread. Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 Any chance you could try a vanilla compiler?  You can install to an 
 isolated directory, such as /usr/local/gcc4.
 
 Either way, the MESS changes to the PPC code interfere with scudrace, 
 so I'll work with Bletch to see what the best solution to that  problem
 is.  (If nothing else, wrapping it in #ifdef MESS should do  the
 trick.)  Now if we can just figure out the cause of your  segfaults,
 we'll be set. :-)
 
 Thanks.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

This is not mess-specific change and _not_ to ppc core as mips drc also
crashes with same backtrace. Moreover the crash appeared in vanilla u5
with unix subdir from released xmame-0.101. That time there was a change
to src/x86drc.h. I have never bootstrapped a compiler, but I wan
thinking about bootstarping gcc 3.4.4 just for compiling mame as it is
the only supported build tool. Could you help me a bit?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] dynarec cores crash

[Julian Sikorski]

Hi. I have just compiled latest mess cvs and dynarec cores still
segfault. According to mametesters, the issue does not exist in windows
build. Can anybody help?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 15, 2005, at 3:06 AM, Julian Sikorski wrote:
 
 Hi. I have just compiled latest mess cvs and dynarec cores still
 segfault. According to mametesters, the issue does not exist in  windows
 build. Can anybody help?
 
 
 I tried yesterday or the day before and didn't run into any problems, 
 at least with kinst and kinst2 and one other game (forgot which one).
 
 Have you tried adjusting your CFLAGS to see if some optimization is 
 responsible?
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

with the attached makefile it still crashes.


makefile.unix.debug.bz2
Description: application/bzip

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Julian Sikorski napisał(a):
 Lawrence Gold napisał(a):
 
On Nov 15, 2005, at 3:06 AM, Julian Sikorski wrote:


Hi. I have just compiled latest mess cvs and dynarec cores still
segfault. According to mametesters, the issue does not exist in  windows
build. Can anybody help?


I tried yesterday or the day before and didn't run into any problems, 
at least with kinst and kinst2 and one other game (forgot which one).

Have you tried adjusting your CFLAGS to see if some optimization is 
responsible?


___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 
 with the attached makefile it still crashes.

Disabling -march=prescott also does not help here. Here is the backtrace
 from scudrace:

(gdb) bt
#0  0x0853eef3 in drc_execute (drc=0xcad3908) at src/x86drc.c:156
#1  0x08372b62 in ppcdrc603_execute (cycles=83)
at src/cpu/powerpc/ppcdrc.c:1155
#2  0x08085f24 in cpunum_execute (cpunum=0, cycles=83)
at src/cpuintrf.c:1444
#3  0x08080fb6 in cpu_timeslice () at src/cpuexec.c:1042
#4  0x080803ca in cpu_run () at src/cpuexec.c:477
#5  0x080d3b90 in run_machine_core () at src/mame.c:600
#6  0x080d3a31 in run_machine () at src/mame.c:531
#7  0x080d370d in run_game (game=2965) at src/mame.c:363
#8  0x09b99498 in main (argc=2, argv=0xbfcd73a4) at src/unix/main.c:104
(gdb)

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] dynarec cores crash

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Nov 15, 2005, at 11:29 AM, Julian Sikorski wrote:
 
 with the attached makefile it still crashes.
 makefile.unix.debug.bz2
 
 
 Which version of GCC are you using?
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

4.0.1 and 3.2.3

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] model3.c games crash in u5 when ppc_drc is active.

[Julian Sikorski]

Julian Sikorski napisał(a):
 Have a look here:
 
 http://www.mameworld.info/ubbthreads/showflat.php?Cat=Number=54112
 
 I have tried building with gcc 3.2.3 and 4.0.1, same result for both.
 Does anybody have the same issue? Greets.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

MIPS drc also triggers the crash.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] model3.c games crash in u5 when ppc_drc is active.

[Julian Sikorski]

Have a look here:

http://www.mameworld.info/ubbthreads/showflat.php?Cat=Number=54112

I have tried building with gcc 3.2.3 and 4.0.1, same result for both.
Does anybody have the same issue? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] debug_halt_on_next_instruction bug in mips3drc.c still present in u4

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Oct 31, 2005, at 12:19 AM, Julian Sikorski wrote:
 
 Could you forward this to Aaron so that it will be fixed in next 
 release?
 
 
 Done.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
Thx.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] debug_halt_on_next_instruction bug in mips3drc.c still present in u4

[Julian Sikorski]

Could you forward this to Aaron so that it will be fixed in next release?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] I am unable to build 0.101u3

[Julian Sikorski]

Linking xmame.x11 ...
xmame.obj/cpu/mips/mips3drc.o(.text+0x188): In function `tlbp':
mips3drc.c: undefined reference to `debug_halt_on_next_instruction'
collect2: ld returned 1 exit status
make: *** [xmame.x11] Error 1

I though it is an error with empty file, but I'm unable to find which
one, so it may be some other issue. Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] PPC drc depends on MIPS drc?

[Julian Sikorski]

Hi. I have tried to disable MIPS3_DRC in order to work around the
previous issue, but here is what happens:

xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x134c): In function
`append_generate_exception':
ppcdrc.c: undefined reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x1475):ppcdrc.c: undefined
reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x14a0):ppcdrc.c: undefined
reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x14c0): In function `ppcdrc_reset':
ppcdrc.c: undefined reference to `drc_append_restore_volatiles'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x1714): In function
`append_branch_or_dispatch':
ppcdrc.c: undefined reference to `drc_get_code_at_pc'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x1751):ppcdrc.c: undefined
reference to `drc_append_standard_epilogue'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x1780):ppcdrc.c: undefined
reference to `drc_append_tentative_fixed_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x22cd): In function
`recompile_bcctrx':
ppcdrc.c: undefined reference to `drc_append_standard_epilogue'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x22d5):ppcdrc.c: undefined
reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x24f1): In function `recompile_bclrx':
ppcdrc.c: undefined reference to `drc_append_standard_epilogue'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x24f9):ppcdrc.c: undefined
reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7e8d): In function `ppcdrc403_exit':
ppcdrc.c: undefined reference to `drc_exit'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7eb2): In function
`ppcdrc403_execute':
ppcdrc.c: undefined reference to `drc_execute'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7ee5): In function `ppcdrc603_exit':
ppcdrc.c: undefined reference to `drc_exit'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7f2f): In function
`ppcdrc603_execute':
ppcdrc.c: undefined reference to `drc_execute'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7f91):ppcdrc.c: undefined
reference to `drc_execute'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7fb5): In function `ppcdrc602_exit':
ppcdrc.c: undefined reference to `drc_exit'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x7ff9): In function
`ppcdrc602_execute':
ppcdrc.c: undefined reference to `drc_execute'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0x8055):ppcdrc.c: undefined
reference to `drc_execute'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xc1e0): In function `ppcdrc403_init':
ppcdrc.c: undefined reference to `drc_init'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xc4d1): In function `ppcdrc603_init':
ppcdrc.c: undefined reference to `drc_init'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xca8c): In function `ppcdrc602_init':
ppcdrc.c: undefined reference to `drc_init'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xcee8): In function
`ppcdrc_recompile':
ppcdrc.c: undefined reference to `drc_begin_sequence'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xcf3f):ppcdrc.c: undefined
reference to `drc_append_verify_code'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xcf87):ppcdrc.c: undefined
reference to `drc_append_call_debugger'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xcfe0):ppcdrc.c: undefined
reference to `drc_append_standard_epilogue'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd035):ppcdrc.c: undefined
reference to `drc_register_code_at_cache_top'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd09f):ppcdrc.c: undefined
reference to `drc_exit'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd0c5):ppcdrc.c: undefined
reference to `drc_append_verify_code'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd0d2):ppcdrc.c: undefined
reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd24c):ppcdrc.c: undefined
reference to `drc_append_dispatcher'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd189):ppcdrc.c: undefined
reference to `drc_end_sequence'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd81d): In function `ppcdrc403_reset':
ppcdrc.c: undefined reference to `drc_cache_reset'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xd9ab): In function `ppcdrc603_reset':
ppcdrc.c: undefined reference to `drc_cache_reset'
xmame.obj/cpu/powerpc/ppcdrc.o(.text+0xe116): In function `ppcdrc602_reset':
ppcdrc.c: undefined reference to `drc_cache_reset'
collect2: ld returned 1 exit status
make: *** [xmame.x11] Error 1

Does it mean that PPC drc depends on MIPS3 drc? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] PPC drc depends on MIPS drc?

[Julian Sikorski]

Sorry, my fault, did not run make clean. Probably that's the reason of
failure.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] I am unable to build 0.101u3

[Julian Sikorski]

Lawrence Gold napisał(a):
 On Oct 25, 2005, at 2:27 PM, Julian Sikorski wrote:
 
 Linking xmame.x11 ...
 xmame.obj/cpu/mips/mips3drc.o(.text+0x188): In function `tlbp':
 mips3drc.c: undefined reference to `debug_halt_on_next_instruction'
 collect2: ld returned 1 exit status
 make: *** [xmame.x11] Error 1

 I though it is an error with empty file, but I'm unable to find which
 one, so it may be some other issue. Greets.
 
 
 Just comment out the problem line for now. It was added by mistake  and
 should be fixed in the core soon. (I'm surprised it wasn't fixed  in
 0.101u3, but Aaron might have forgotten.)
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
That did the trick, thx.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] makefile.unix

[Julian Sikorski]

Hi. I have noticed that -march=athlon64 has been added to the makefile.
How about adding -march=prescott too? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Performance Issues

[Julian Sikorski]

William Edsall napisał(a):
 Hello!
  
 This is my first post, hopefully I'm doing it right.
 
 Anyways. I've been working with Fedora Core 3 and Xmame for the last few
 weeks. I'm using the mamed front end.
 My problem is, everything runs at high processor utilization. Games like
 x-men run at something like 87%, and Killer Instinct 1/2 are peaked at
 99%, unplayable.
 I've swapped out my chip and memory for significantly better, and made
 no difference.
 
 I'd like to know if the bottleneck lies with Xmame before I swap my
 video card and such. Even ZSNES runs high, so maybe I just have
 something misconfigured in Fedora, who knows.
 Thanks in advance for the input. I'd like to continue with Xmame and
 avoid windows.
 
 Will
 

Mame depends almost only on the cpu. Which one do you have?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] xmame on pentium I

[Julian Sikorski]

Federico napisał(a):
 hi all,
 I have a question. I have an old laptop with a Pentium I 100Mhz and 32
 MB ram. Do you think xmame can run in this pc? I have installed the last
 version of xmame and I have 20% cpu usage for X and 80% cps usage for
 xmame... naturally it doesn't work well Are there some
 comfigurations (in Makefile) for to do xmame a light xmame?
 
 
 
 bye Federico
I don't think that you'd even be able to run pacman pull-speed. Try some
older xmame versions (0.36) and fidle with frameskip.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Effects + GL mode

[Julian Sikorski]

Matheus Villela wrote:
 Are the effects code working with xmame.x11 in GL mode? (video-mode 2)? 
 I remember using effects in GL mode some months ago but now it isn't 
 working.
 
 My xmamerc relevant configs:
 video-mode   2
 effect   3
 
 I've also tried with control + page up/down with no luck, with every 
 other video mode i can have effects but not with GL one.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
No. GL is an effect itself.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] kxmame-1.0 released

[Julian Sikorski]

Christopher Stone wrote:
 Does kxmame need to be installed in order to run correctly?  I
 compiled it and ran it under the ./src/ directory and it didn't last
 very long. :)
 
 KCrash: Application 'kxmame' crashing...
 
 On 8/25/05, Toan T Nguyen [EMAIL PROTECTED] wrote:
 
Hello everyone,

I'm pleased to annouce the first release of kxmame, a KDE port of the
GXmame frontend for xmame. Besides fully compatible with gxmame and
full integration with KDE, kxmame offers the following additional
improvements:

- Customizable toolbar where one can add, remove and change icons of
the toolbar buttons.
- Customized game icon size (8, 16, 24, 32 pixels or set to 0 pixel to
disable game icons.)
- Fast. Kxmame is noticably more responsive than gxmame due to various 
caching.

The source code for kxmame can be downloaded at

http://sourceforge.net/projects/kxmame/

Very bests,

Toan

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Probably, I have installed it and is running close to perfect.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] 0.99u3 build failure

[Julian Sikorski]

src/unix/video.c: In function `update_params':
src/unix/video.c:651: `ui_dirty' undeclared (first use in this function)
src/unix/video.c:651: (Each undeclared identifier is reported only once
src/unix/video.c:651: for each function it appears in.)
src/unix/video.c: In function `update_game_vis_area':
src/unix/video.c:836: warning: implicit declaration of function
`set_ui_visarea'
src/unix/video.c: In function `osd_update_video_and_audio':
src/unix/video.c:1123: `ui_dirty' undeclared (first use in this function)
src/unix/video.c: In function `should_sleep_idle':
src/unix/video.c:1425: warning: implicit declaration of function
`setup_active'
make: *** [xmame.obj/unix.x11/video.o] Error 1
[EMAIL PROTECTED] xmame-0.99u3]$

That's probably because of the changes made by Aaron. video.c may not be
the single file that is not compiling. Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Announcing kxmame frontend

[Julian Sikorski]

Toan T Nguyen wrote:
 Hello,
 
 I add support to kxmame for viewing the marquees, flyers, ... with
 proper scaling  and hide the BIOS category as you requested. I also
 add the translation files from gxmame. They compile and install. But I
 have no idea if it works properly or not. (I tried the French
 translation and it seems fine).
 
 Could you tell me if the translation works for pl locale ? If it
 works, I might make a beta release soon.
 
 Thanks,
 
 Toan

Huh:
Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /viewcvs.py/kxmame.

Reason: Max-Forwards has reached zero - proxy loop?

I can't access sf.net cvs.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Announcing kxmame frontend

[Julian Sikorski]

Is mailing list for kxmame set up? It may be annoying for Lawrence to
use theirs for a longer period. Locale works fine, same as in gxmame.
What I really meant concerning the bioses in not to hide the bios
category, but rather not to list them in e.g available folder. The only
bios that is able to run by itself is taito g-net iirc. Keep up the good
work!

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] [Mamory] 0.2.20 released

[Julian Sikorski]

Pierre Maziere wrote:
 
 minor fix
 
 Changes:
  - fix clrmamepro dat file parsing, allowing the use of titles
clrmamepro dat files and possibly others
(thanks to Julian Sikorski for reporting)
 
 -
 Pierre Maziere
 http://mamory.sourceforge.net
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

God, you're quick ;)

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Announcing kxmame frontend

[Julian Sikorski]

I am unable to compile it:
if g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/kde
-I/usr/lib/qt-3.3/include -I/usr/X11R6/include   -DQT_THREAD_SUPPORT
-D_REENTRANT -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include-Wnon-virtual-dtor -Wno-long-long -Wundef
-ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion
-Wchar-subscripts -Wall -W -Wpointer-arith -Wno-non-virtual-dtor -O2
-Wformat-security -Wmissing-format-attribute -fno-exceptions
-fno-check-new -fno-common -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include   -DKXMAME  -MT kxmame.o -MD -MP -MF
.deps/kxmame.Tpo \
  -c -o kxmame.o `test -f 'kxmame.cpp' || echo './'`kxmame.cpp; \
then mv -f .deps/kxmame.Tpo .deps/kxmame.Po; \
else rm -f .deps/kxmame.Tpo; exit 1; \
fi
kxmame.cpp: In member function ‘void kxmame::setupActions()’:
kxmame.cpp:153: warning: unused variable ‘mPlayAction’
kxmame.cpp:156: warning: unused variable ‘mRecordAction’
kxmame.cpp:159: warning: unused variable ‘mReplayAction’
kxmame.cpp:162: warning: unused variable ‘mAddFavoriteAction’
kxmame.cpp:165: warning: unused variable ‘mRemoveFavoriteAction’
kxmame.cpp:168: warning: unused variable ‘mAuditAllAction’
kxmame.cpp:172: warning: unused variable ‘mExitAction’
kxmame.cpp:217: warning: unused variable ‘mExpandAction’
kxmame.cpp:220: warning: unused variable ‘mCollapseAction’
kxmame.cpp:226: warning: unused variable ‘mDirSetupAction’
kxmame.cpp:233: warning: unused variable ‘mGameListAction’
kxmame.cpp:236: warning: unused variable ‘mCloneColorAction’
kxmame.cpp: In member function ‘void kxmame::setupExecutablesSelection()’:
kxmame.cpp:264: warning: unused variable ‘cur_exec’
kxmame.cpp: At global scope:
kxmame.cpp:300: warning: unused parameter ‘val’
kxmame.cpp: In member function ‘void kxmame::gameAudit()’:
kxmame.cpp:489: error: ‘round’ was not declared in this scope
kxmame.cpp:583: error: ‘round’ was not declared in this scope
make[2]: *** [kxmame.o] Error 1
make[2]: Leaving directory `/home/jsikorski/cvs/kxmame/kxmame/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/jsikorski/cvs/kxmame/kxmame'
make: *** [all] Error 2
[EMAIL PROTECTED] kxmame]$

Using Fedora Core 4 here.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Announcing kxmame frontend

[Julian Sikorski]

Toan T Nguyen wrote:
 Hi, 
 
 It's fixed in the latest CVS. I also complete the support for game
 filters and fix a problem with setting catver directory. Please wait
 for a few hours before the latest modifications to appear in CVS.
 
 Toan

Now everything works ok. I presume that support for title screenshots
and custom icons will appear. kxmame seems to be a bit faster han
gxmame. Also listing bioses in gamelist is a bit stupid as they cannot
be run bu themselves. I wish you best of luck.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Auditing title screenshots

[Julian Sikorski]

Ren Hoek wrote:
 On 8/17/05, Lawrence Gold [EMAIL PROTECTED] wrote:
 
On Aug 17, 2005, at 12:35 AM, Julian Sikorski wrote:


Hi. I am using Mametitles and I would like to audit them with provided
clrmamepro dat file. I was trying to use mamory, but I was
unsuccessful.
 Do you have any ideas? Greets.

I don't know about getting mamory working, but clrmamepro runs fine
for me under Wine, so that would be a good option to fall back on.

 
 
 I use wine as well, and I have a great deal of success there, as well.
  But I keep getting dialogs disappearing on me.  For instance, from
 the 'Settings' dialog, if I press 'OK', the dialog disappears, but the
 main button bar never returns.  Wine is still running, and I can use
 Ctrl-C to terminate wine, so it doesn't appear as if wine has crashed.
  Also, when I restart ClrMamePro, the settings are remembered, so this
 is simply an annoyance rather than unusable.
 
 Do you see the same thing?  Is there some secret to making it work
 cleaner?  I have asked these same questions on the clrmame forums and
 received somewhat caustic responses, but that was a couple of years
 ago, too.  If it 'just works' for you, then I'm happy for you.  I'm
 mainly asking just in case I've missed an options that cures some of
 ClrMamePro's ills.
 
 Great list, by the way, and God bless xmame.  Keep up the good work.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

I have managed to get mamory working. I zipped the titles into
titles.zip and added the dat header from logiqx dat as mamory is quite
restrictive. Pierre was informed about this and promised to check this.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Announcing kxmame frontend

[Julian Sikorski]

Toan T Nguyen wrote:
Now everything works ok. I presume that support for title screenshots
and custom icons will appear.
 
 
 Title screenshot is already supported. You can set it by
 
 Menu-Directories-Xmame additional paths-Snapshots path
 
 Bests,
 Toan
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Oh, right. But I meant the option to choose what is displayed (marquee,
cabinet, title or ingame screenhot). They also shouldn't be stretched
without consaerving the proportion. But everything is most probably on
the way.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] Announcing kxmame frontend

[Julian Sikorski]

 I keep the bios listing to make things compatible with gxmame.
 
 Toan

I have suggested the same thing on gxmame mailinglist, but no one seemed
to reply. as the developers state, gxmame is 'not dead, but almost'.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] Auditing title screenshots

[Julian Sikorski]

Hi. I am using Mametitles and I would like to audit them with provided
clrmamepro dat file. I was trying to use mamory, but I was unsuccessful.
 Do you have any ideas? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] I can't get a debug build

[Julian Sikorski]

Hi. I am attaching the makefile I use. I compile with make -f
makefile.unix.debug. Unfortunately, I am unable to get debugging symbols:

(gdb) bt
#0  0x084751d8 in ?? ()
#1  0x01f0 in ?? ()
#2  0x0018 in ?? ()
#3  0xb0aa2008 in ?? ()
#4  0x00204a86 in ?? ()
#5  0xb0aa2008 in ?? ()
#6  0x0020 in ?? ()
#7  0xbff9c478 in ?? ()

and so on. What can be wrong here? Greets.
###
# #
# makefile for xmame/xmess#
# #
# Original version by Juan Antonio Martinez and Hans de Goede.#
# Current version by Lawrence Gold, with much inspiration from XviD.  #
# http://x.mame.net   #
# mailto:[EMAIL PROTECTED]#
# #
# #
# READ COMMENTS AND MODIFY CONFIGURABLE OPTIONS WITH CARE.#
# #
# Members of the MAME and Xmame projects assume no responsibility #
# implicit or explicit about illegal or incorrect use of this #
# sofware and about possible hardware or software damage caused   #
# by its use. #
# #
# THIS SOFTWARE IS DISTRIBUTED AS IS.  USE AT YOUR OWN RISK #
# #
# MAME and Xmame are Copyright (c) Nicola Salmoria and Mirko buffoni  #
# and distributed under terms simular to the GNU General Public   #
# License.  See doc/readme.unix for more details  # 
# #
# Arcade ROM images are copyrighted by their authors.  DISTRIBUTING   #
# MAME OR XMAME WITH ROM IMAGES IN THE SAME PACKAGE IS ILLEGAL AND#
# CONSTITUTES A VIOLATION OF TERMS OF COPYRIGHT.  #
# #
###


###
# Xmame or xmess or...?
###

# Uncomment one of these.
TARGET = mame
# TARGET = mess
# TARGET = mage
# TARGET = mmsnd
# example for a tiny compile
# TARGET = tiny


###
# Special features
###

# Enable experimental network support.  See 
# src/unix/doc/multiplayer-readme.txt for more information.  (CURRENTLY 
# BROKEN)
# XMAME_NET = 1

# Uncomment to use DRC MIPS3 engine
X86_MIPS3_DRC = 1

# Uncomment to use DRC PowerPC engine
X86_PPC_DRC = 1

# Uncomment if you'd like to disable effects.  This can considerably speep 
# up compilation of the blit files.
DISABLE_EFFECTS = 1

# Uncomment the line below to enable the MMX assembly-language optimized
# routines for the light scanlines and 6-tap filter effects. This
# requires an IA-32 processor with MMX capability and the NASM assembler.
#
# On Linux-i386 you can enable this without causing problems on non
# MMX capable processors: the Linux code will autodetect if an MMX
# capable processor is present and use the right code.
# EFFECT_MMX_ASM = 1


###
# Development environment options 
###

# GNU make is MANDATORY!!!


###
# Choose your compiler.
###

# Support for the Intel C++ Compiler is new and experimental.  Be sure
# to check the CFLAGS, RANLIB, IL, LD, and MY_CPU sections in this 
# makefile.  If you've set up a nice environment or alias or wrapper
# script, then you can use `icc'.
#
# Use of `c89' is recommend for Ultrix as it generates faster code, which
# means fewer frames to be skipped and better graphics, but `gcc' works 
# just as well.  However, stay away from the `cc' Ultrix compiler if 
# possible.

CC  = gcc32
# CC= cc
# CC= icc
# CC= c89

# Uncomment for Sun Forte 7 and above C/C++ compiler, see below for
# additional optimizations.
# CC = sun-forte

# Compiler for host compilations in cross-compiling environments (used 
# in src/unix/unix.mak for m68k).
HOST_CC = $(CC)
# HOST_CC = gcc

Re: [Xmame] I can't get a debug build

[Julian Sikorski]

Carl M. Fongheiser napisał(a):
INSTALL_PROGRAM = $(INSTALL) -c -s -o $(INSTALL_USER) -g $(INSTALL_GROUP) 
-m  555
 
 
 The -s in this line is what is causing your problem.  The copy in your
 build directory should have debug symbols, but the installed copy is
 stripped.
 
 Carl Fongheiser
 [EMAIL PROTECTED]
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Hmm, IMHO the -s option should be removed from that place. It is already
present in normal linking part, so the double declaration will only
cause problems. Lawrence?

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] error linking 0.99u1

[Julian Sikorski]

The error results from double definition of config_init. I have renamed
all it's occurences in unix tree to config_init_unix. Is it a good fix?
Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] error linking 0.99u1

[Julian Sikorski]

Julian Sikorski wrote:
 The error results from double definition of config_init. I have renamed
 all it's occurences in unix tree to config_init_unix. Is it a good fix?
 Greets.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Hmm, apparently something is wrong as gxmame is unable to detect xmame
executable.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] error linking 0.99u1

[Julian Sikorski]

Julian Sikorski wrote:
 Julian Sikorski wrote:
 
The error results from double definition of config_init. I have renamed
all it's occurences in unix tree to config_init_unix. Is it a good fix?
Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 
 Hmm, apparently something is wrong as gxmame is unable to detect xmame
 executable.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Huh, it must have been some error on gxmame's side. Works ok now.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] error linking 0.99u1

[Julian Sikorski]

Lawrence Gold wrote:
  I made the same fix in the MESS CVS sources, except I named it
 xmame_config_init and also renamed config_exit to xmame_config_exit  to
 be consistent.

IMO it is a better name ;)

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] gcc 4.0.1 still miscompiles v60 core

[Julian Sikorski]

I have just upgraded to gcc 4.0.1 and recompiled xmame-0.98u2.
Unfortunately, v60 core still gets miscompiled. Maybe we should file in
a bug in gcc? Greets.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0.98u2 problem

[Julian Sikorski]

Julian Sikorski wrote:
 Lawrence Gold wrote:
 
Julian Sikorski wrote:


Compiling src/sndhrdw/mcr.c ...
In file included from src/sndhrdw/mcr.c:19:
src/includes/mcr.h:16: error: array type has incomplete element type
make: *** [xmame.obj/sndhrdw/mcr.o] Error 1
[EMAIL PROTECTED] xmame-0.98u2]$


I committed a change to src/includes/mcr.h last week that should fix
this.  If it's still a problem, let me know.


___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

 
 No, it isn't. I should have cheched the cvs first.
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 

Btw, why is the cvs timing out? I can't fetch sysdep_display.h at which
the compilation fails.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0.98u1 and #pragma problem

[Julian Sikorski]

So fedora sucks once again. I have to use gcc 3.2.3 which deprecates
#pragma once, or gcc 4.0.0 miscompiling v60 core :(.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

[Xmame] 0.98u2 problem

[Julian Sikorski]

Compiling src/sndhrdw/mcr.c ...
In file included from src/sndhrdw/mcr.c:19:
src/includes/mcr.h:16: error: array type has incomplete element type
make: *** [xmame.obj/sndhrdw/mcr.o] Error 1
[EMAIL PROTECTED] xmame-0.98u2]$

Using fc4 here.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Re: [Xmame] 0.98u2 problem

[Julian Sikorski]

Lawrence Gold wrote:
 Julian Sikorski wrote:
 
 Compiling src/sndhrdw/mcr.c ...
 In file included from src/sndhrdw/mcr.c:19:
 src/includes/mcr.h:16: error: array type has incomplete element type
 make: *** [xmame.obj/sndhrdw/mcr.o] Error 1
 [EMAIL PROTECTED] xmame-0.98u2]$
 
 
 I committed a change to src/includes/mcr.h last week that should fix
 this.  If it's still a problem, let me know.
 
 
 ___
 Xmame mailing list
 Xmame@toybox.twisted.org.uk
 http://toybox.twisted.org.uk/mailman/listinfo/xmame
 
No, it isn't. I should have cheched the cvs first.

___
Xmame mailing list
Xmame@toybox.twisted.org.uk
http://toybox.twisted.org.uk/mailman/listinfo/xmame