Recent Posts

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.

Carbie. Notice the choke is quite a complicated beastie. Carbie also compensates for altitude so that it means out the higher it goes. Not perfect, but acceptable

Nitrogen widget, yeah notice it was fine to start and then went really rough? First I thought the carbs might simply be unbalanced, but I'm pretty sure now there's a blocked jet or cracked O ring etc in one or both carbies. I was able to easily get the bowls off to have a look. First glance looked good but then noticed the petrol 'varnish' that can build up. Cleaned all that out and checked the pilot jets but nothing out of the ordinary . So this weekend I'm taking them off completely and giving them a more thorough inspection at home. Mat need overhaul kits, which are over 200 USD each carbie. Ouch!

PBL, oil and fuel pressure lines in the cab give me the Willie's, for exactly your unfortunate experience. Electrical for me.
And yes, I'll be double quadruple checking everything. The aircraft mechanic at the field will also get his boys to go over it too. He will do the first hour flying. I'd love to be the first but it's not recommended. This guy has tested probably hundreds of aircraft in his time.

Both shows for The National were great.  The setlists were pretty diverse and we got to hear some new songs.

Tool is up next in November but I also got tix for King Gizzard and the Lizard Wizard for August 2024.  Can't wait for that one as I've been obsessed with this band for the last few years.