On Wed, Mar 12, 2003 at 05:16:12PM +0100, Frank Everdij wrote:
>
> So people? What about this piece of code? Why is it only SGI specific?
> Is it superfluous, maybe?
> If you would be so kind to fix this in 0.66.1, then maybe we finally
> have a xmame build which compiles and runs out of the box o
Here it is !
This new version introduces the SPLIT, MERGE and FULL storage mode.
It also fixes a lot of memory leaks, which makes Mamory much more
stable: I succeeded in migrating my 0.63 MAME roms set from a SPLIT
storage mode to a MERGE storage mode, without any problem ... without
the test optio
[EMAIL PROTECTED] wrote:
> That's pretty simple alright. Is there a way to find out what games
currently
> use test drivers?
You could:
grep TESTDRIVER driver.c
and get the full list of games with test drivers. But virtually all of them
aren't enabled because they don't work for one reason or
That's pretty simple alright. Is there a way to find out what games currently
use test drivers?
-- Epicenter
On 16 Mar 2003 at 9:54, XulChris wrote:
> On Wednesday 30 October 2002 09:28 am, [EMAIL PROTECTED] wrote:
> > In the manufacturer's driver file, I assume? ..
> >
>
> no, its real easy,
On Wednesday 30 October 2002 09:28 am, [EMAIL PROTECTED] wrote:
> In the manufacturer's driver file, I assume? ..
>
no, its real easy, in driver.c just change TESTDRIVER to DRIVER. It's as
simple as that.
___
Xmame mailing list
[EMAIL PROTECTED]
http:
In the manufacturer's driver file, I assume? ..
-- Epicenter
On 16 Mar 2003 at 11:55, Simon Roby wrote:
therefore XMAME too) has a policy on not having games recently released.
> Note that you could add it yourself, as a matter of fact it's actually
> in the code, only commented out.
___
christoffer wrote:
It would be very nice if metalslug 4 would be incorperated into xmame.
right now i am playing it in neoragex :(.
This game won't be officially here until (I think) 2004, as MAME (and
therefore XMAME too) has a policy on not having games recently released.
Note that you could ad
I think this maybe a gcc problem but when I try to turn on logging with
-log I get a segmentation fault early on. On investigation the
first parameter to logerror, char *text, is the value 1, so naturally it
seg faults. What happens is when the LOG macro is used and has more
than two parameters,
