Recent Posts

Yikes, that does not look like fun.

I think I've already related how I once pulled apart the carbie from my Datsun 120Y, cleaned it, reassembled it, and everything worked 100%... but there were 4 parts left over!

Something like that clock we've probably all pulled apart as a kid.

Then there is the challenge of balancing twin carbs

Good luck! Give yourself a good clean space to work in. Take lots of photos (so you know how everything goes back together).

I tested it dozens of times and it only disconnected once, but in recent versions it always disconnects. In MAME 0249 the oscillations of the opposing cars are much smaller as well. Did you take the test? Does the same happen for you?

Hi,
I'm trying to configure Outrunners on LAN on a twin cab setup. It works fine on LAN but it displays 2 screens on 1 cab and 2 on the other. (So basically a 4 player). Is there a way to "eliminate" the second screen on each cab and only show the first one to get a basic 2 player LAN setup? I read that in older versions of MAME, there was a DIP switch in the ROM to set it to "single screen", but this no longer exist.
I tried to set numscreens to 2 in mame.ini but than I need to enable windowed mode because on fullscreen mode it crashes (I use bgfx as video driver). Sadly there is no "borderless" fullscreen in mame afaik, so windowed mode is not a good solution either.
Any input?
Thanks

With the game running, press the TAB key, select video options and screen 0. Do the same on the other PC.

My orunners.ini looks like this:

#
# Individual game CONFIGURATION OPTIONS
#

#
# OSD VIDEO OPTIONS
#
video                     auto
numscreens                2
window                    0
maximize                  1
waitvsync                 0
syncrefresh               0
monitorprovider           auto

#
# OSD PER-WINDOW VIDEO OPTIONS
#
screen                    auto
aspect                    auto
resolution                320x240
view                      auto
screen0                   auto
aspect0                   auto
resolution0               auto
view0                     auto
screen1                   auto
aspect1                   auto
resolution1               auto
view1                     auto

I think you can ignore that resolution line and put your own as i'm running on a real old CRT monitor. But you're saying that method is not going to work for you? In which case you might try loading both windows and then automating the process of selecting the correct screen and making it borderless fullscreen. Autohotkey will do this, using something like the below ahk textfile snippets, compiled into an exe if you like:

Run "C:\games\mame\outrunners.bat" ; i use a batfile but try however you want
sleep 6000
SetTitleMatchMode, 2
Winactivate, screen 0
sleep 1000
WinGet, WindowID, ID, A
WinSet, Style, -0xC40000, ahk_id %WindowID%
WinMove, ahk_id %WindowID%, , 0, 0

I'm using the ini file, and the first four lines of the above AHK script to load the game, then select the particular instance i want to bring to the top (screen 0 vs screen 1, here). You may need to run the game windowed (in two windows, here) and then use the full AHK script to select which window you want to bring to the front and then maximise into borderless fullscreen. Setting the resolution in MAME ini to be your desired screen res is probably still a good idea.

If you haven't used autohotkey before, it looks daunting. But it's pretty easy to learn and you can find lots of examples to copy or crib from. Running everything on the lists above really requires you to learn something like this I'm also probably not going to be able to troubleshoot this for you. I use the second part of that script to grab several other windowed games (each of which is at the time already in front/selected) and then maximise to borderless fullscreen.

I just bought a Joust cocktail cab in Connecticut on Marketplace.

I live in Illinois.

He asked for 800 bucks. I offered 500. He took 500.

My good friend Bperkins01 picked it up for me since he lives in MA.

The whole deal was easy peasy. Even though I was almost a thousand miles away and I was having someone else pick it up for me.

Facebook Marketplace is the best.

Hello,



I appreciate it's a weird title. Let me explain.


So I've made a few arcade machines using PCs and to light up the LED buttons, I use a SATA to Molex adaptor and connect the LEDs to the yellow (12v) and black ground cables. This has always worked fine.



This time, however, I'm using an old HP all-in-one (AIO - PC built into a monitor) and using the same method does not light up the LEDs. I have tested the exact same molex-LED apparatus on a normal desktop PC and it works fine, but not in this AIO. To make sure the SATA power is working on the AIO, I connect a HDD to it and it powers on and runs fine. Not only does it not work when I connect the LED apparatus to it, but testing the SATA power socket with a multimeter shows no power coming from it.



The only explanation for this is that the AIO only provides power to the SATA power socket if there is something plugged in to the *data* socket as well. Maybe this is some power saving feature, since it has a small PSU built into it? All power saving options on the BIOS have also been disabled.



Can anyone shed some light on this and how I could get around the issue? I want to avoid using a separate 12V power adaptor, since I want to LEDs to power on when I power on the AIO PC.



Much appreciated!

Getting rid if my old set of Actlabs S-Video Light Guns, as I converted my arcade from S-Video to RGB.

These work in daisy chain so you can get 2 player out of them, and work well without drivers within Mame on Win7 or higher.

Here's a link to the ebay listing, however available for local pickup externally if anyone is interested.
https://www.ebay.com/itm/126108826593

I know the latest version of mame can run on a lot and I have no idea how you got that my hardware is ancient or that I hate Windows.

From  your own words...

I understand why they've dropped the older OS's, but I have older hardware and would like a simpler setup. 

Anyway...

So I'm trying to understand the software, but if they're keeping pace to run on newer hardware and OSs then it's probably got it's own bloat.  Since they have every version of mame since they started available and I know at some point an older OS either can't or shouldn't run past a certain point.  With all of the historical data I was hoping there was an easy way to identify those OS limits.  I'll assume nothing like that exists or I still don't know enough about it yet.

Memory is fuzzy, but I think its indirectly tied to DirectX versions.  So you'd have to search the release notes and see when support for the major DirectX versions was added (9, 10, 11, 12), and then cross-reference that with Windows OS support. 

For reference, one of my cabinets is an old Intel i5-2600k with a Geforce GTX 660 Ti GPU (hardware that is over a decade old) running Windows 10 and MAME 0.254 (haven't updated to the newest version yet).   No issues to speak of.   That system can emulate everything up to PS2 easily, and some newer stuff.  It's been able to handle most Tekonoparrot games too that I've tried.  Mostly lightgun stuff.   

I'm not entirely happy with the direction Windows 11 is going (crazy amount of user telemetry, and adding "Bing AI" integration directly into the OS), so I'm not sure my cabinets will every see Win11 or beyond.  But Windows 10 is fine once you hack out Cortana.

You should also consider if your audio source has the power to drive the additional speakers.

I know the latest version of mame can run on a lot and I have no idea how you got that my hardware is ancient or that I hate Windows.  None of that was what I asked so let's just skip those.
I happen to have all Microsoft OS from DOS 3 to Server 2022.  I've used linux for years and have a few RPis lying around so my options are very broad for and OS and hardware isn't a problem either.  So I'm trying to understand the software, but if they're keeping pace to run on newer hardware and OSs then it's probably got it's own bloat.  Since they have every version of mame since they started available and I know at some point an older OS either can't or shouldn't run past a certain point.  With all of the historical data I was hoping there was an easy way to identify those OS limits.  I'll assume nothing like that exists or I still don't know enough about it yet.