Hi,
I've been toying around with romalizer to update my romset for 0.62. I've
now got a complete romset, I probably just need to remove obsolete zip
files etc now.
But (as yes, there is a but ;-)), I've got two strange things persisting
with romzalizer :
With spacecho : When using xmame with
Once upon a time, Matthias wrote :
With spacecho : When using xmame with -vr it says the archive is
missing a file pr09 of 256 bytes... and when running romalizer, that
file's presence isn't checked thus the archive is considered ok. My guess
would even be that romalizer actually removed that
Hmm, did I miss the .62 sources somewhere along the line ? I;ve been
trying to verify the romset using the xmame.x11 binary that was
made available, but with little success. The binary as downloaded apears
to be ELF branded as SYSV - I am assuming it's actually a Linux binary so
I rebranded it as
You can try to build it yourself though. Simply untar the xmame 0.61
sources, unzip the official winmame 0.62 sources over it, execute
make -f makefile.unix and try to correct compilation errors if there
are any.
O.K., might give that a shot then. I wish I'd found this out *before*
doing the
On Thu, Nov 21, 2002 at 03:14:08PM +, Pete French wrote:
I used that same bin to verify the 62 sets.
What are you running on? I ran it using
Redhat 8.0 with no issues at all.
FreeBSD 4.7-STABLE, using Redhat 7.1 libraries as far as I know. redhat 8
would explain it as thats a later
I could also make available the WIP xmame-0.62.1 sources, which work for
verification. If you want to play anything, you have to specify -norotate
and hope that the game has a vertical orientation. ;-)
That would be very useful if you could - at the moment I am just doing
verifications to
On Thu, Nov 21, 2002 at 03:35:52PM +, Pete French wrote:
That would be very useful if you could - at the moment I am just doing
verifications to make a .62 ppatchkit of ROMS available in the normal way.
Okay, I'll provide something this evening (U.S. Mountain time).
To determine if your video card supports the Xv extension, you may use
this command:
xdpyinfo | grep XVideo
If it returns the word XVideo on a line by itself, then the Xv extension
is supported on your machine.
This is wrong! xdpyinfo shows loaded modules, and the sole fact that Xv is
- Original Message -
From: Ben Saylor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 20, 2002 7:18 PM
Subject: [Xmame] neat Xv utility
http://freshmeat.net/projects/xvattr/?topic_id=100%2C125
It's a commandline + GTK utility to set Xv attributes (brightness,
On Thu, 21 Nov 2002 11:37:58 -0500
Simon Roby [EMAIL PROTECTED] wrote:
To determine if your video card supports the Xv extension, you may use
this command:
xdpyinfo | grep XVideo
If it returns the word XVideo on a line by itself, then the Xv
extension is supported on your machine.
On Wed, 20 Nov 2002 23:53:01 +0100
Matthias Saou [EMAIL PROTECTED] wrote:
Oh, and also : For those who were mentionning commenting out the drivers
for the games that need hard drive images... it's not useful as xmame
only checks the rom part as it does with all other games, thus they are
Hi Everyone,
I've been working on adding VIDIX support to XMAME recently, in an attempt to
squeeze a few more frames-per-second out of my EPIA motherboard :)
VIDIX is released under the GPL, so until or unless the MAME project goes
GPL, the VIDIX driver will have to be released as a separate
- Original Message -
From: Alastair Robinson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 19, 2002 7:06 PM
Subject: [Xmame] Xv cleanup in preparation for VIDIX driver - testing please
:)
Hi Everyone,
I've been working on adding VIDIX support to XMAME recently, in
I use joy2key (rawconsole mode) with xmame 0.61.1 (svgalib mode, SVGALib
1.9.16) to be able to use my joypad (Logitech Wingman USB). It works fine, if
I switch manually (Ctrl + Alt + F5) to console, log myself in and enter
joy2key -config xmame | xmame
It will not work, if I enter that command
Hi,
I use joy2key (rawconsole mode) with xmame 0.61.1
(svgalib mode, SVGALib
1.9.16) to be able to use my joypad (Logitech Wingman
USB). It works fine, if
I switch manually (Ctrl + Alt + F5) to console, log
myself in and enter
joy2key -config xmame | xmame
It will not work, if I enter that
Fogle Cpl Shawn B wrote:
Well, since we mention this.. there are some new mcpu opts. for GCC 3.X
that, maybe, should be in the makefile, i.e. mcpu=pentium3.
Hmmm, I've been compiling with march=athlon is mcpu= the same
as march= ?
We really should be using autoconf.
It's not hard to do, but
On Fri, Nov 22, 2002 at 05:59:10AM +1100, Kingsley wrote:
Hmmm, I've been compiling with march=athlon is mcpu= the same
as march= ?
-march implies -mcpu. For x86, -mcpu alone produces code that'll run on a
386 but is (in theory) optimized for a specific processor. -march goes
one step
Hmmm, I've been compiling with march=athlon is mcpu= the same
as march= ?
one contrils the instructons emitted, the other controls the ordering
for optimisation... (cant remember which is which at the mment!)
We really should be using autoconf.
autoconf just makes the code a lot harder to
joypad works fine for everything else
Box is running redhat 8.0 and I have done modprobe joydev
xmms and the gxmame GUI for example but completely ignored by xmame, here's
some more info:
when running GUI with joystick support:
joydev 1
when running GUI with joystick support:
joydev 0
when
just to add it's the xgl version.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Duncan Morison
Sent: 21 November 2002 23:04
To: [EMAIL PROTECTED]
Subject: [Xmame] joypad problems:
joypad works fine for everything else
Box is running redhat 8.0 and I
Check the joytype variable in .xmamerc
On Thu, 21 Nov 2002 23:03:57 -
Duncan Morison [EMAIL PROTECTED] wrote:
joypad works fine for everything else
Box is running redhat 8.0 and I have done modprobe joydev
xmms and the gxmame GUI for example but completely ignored by xmame,
here's
On Thursday 21 November 2002 06:46 am, Vincent Kieffer wrote:
This means that the xmame.x11 binary you downloaded was compiled on a
bleeding edge linux system that uses glibc 2.3 ... which is a bad idea
for many Linux distributions still uses glibc 2.1 (at least, my Debian
Woody do ... and
I don't have a .xmamerc file on my system ( after udatedb, locate .xmamerc )
I'm guessing this is a config file which isn't there because I'm using a
frontend ( gxmame ).
do you have a path to where it should be and a suggested contents of the
file?
quite happy to try from command line if that
Oops. That should have been .xmame/xmamerc.
Sorry about that, chief!
I've just sent you a copy of my xmamerc file. Edit to suit your system,
put it into the ~/.xmame directory.
On Fri, 22 Nov 2002 00:17:49 -
Duncan Morison [EMAIL PROTECTED] wrote:
I don't have a .xmamerc file on my
joypad works fine for everything else
Really?
Give this a shot and gimme the output if you have problems after this...
xmame.x11 -jt 4 -jdev /dev/js
or
xmame.x11 -jt 1 -jdev /dev/js
this is assuming that you're using the x11 target.
shawn
p.s. on further troubleshooting give command then
I don't have a .xmamerc file on my system ( after udatedb, locate .xmamerc
)
.xmamerc is usually located under your home tree. i.e. /home/user/.xmamerc
if not you can do a...
xmame -showconfig /home/user/.xmamerc
pull up your favorite editor (emacs ;p) and start editing away!
You can try
On Fri, 22 Nov 2002 00:43:09 -
Duncan Morison [EMAIL PROTECTED] wrote:
couple more questions:
what does the joypad 4 mean?
0 No joystick
1 i386 style joystick driver (if compiled
in)
2 Fm Town
27 matches
Mail list logo
