bkenobi

From what I've read, 104u6 is the last version that will support the WinGun driver. I know it's not supported under 125, but I haven't gone through and validated that 105 won't work. Either way, there's no patch for 105 that I've found either. The oldest hiscore patch I've seen is 108.

It's not the path. I think something must have changed between v0.104 and v0.105 (perhaps that's when MAME went to DX8?). I can compile 105, but I get errors on 104. I have been able to compile 104u6 with the MinGW stuff that Logiqx linked. I wasn't able to get things to work with the instructions from the MAME compiling board (mainly because the links were no good). So, it looks like MAME Compiler can compile anything from MAME v0.105 up to current. Oh well, I was able to apply the patches with Your code anyway. That made things a little quicker. Any chance there's a 104 diff file to remove the nag screen?

I think the error might have to do with the path. I was getting the same error with the instructions off logiqx's site until I included the c:\mingw\bin directory. I'm wondering if I should just add that to my windows path and try again?

Ok, I guess I may have posted a fraction of a second too soon. I found on logiqx site a guide and files for compiling MAME 104u4. I'm going to give it a try this evening, but I'm assuming all should work fine. It won't be as clean as using HK's tool, but if it works, it works! Link

Ok, so I think I've figured out why I'm getting an error. I'm trying to compile an older version of MAME that was designed to be compiled with a different version of MinGW etc. I found a discussion of what's required to compile an older version of MAME on the MAME compiling board at MAMEworld, but the files are all dead links. Link It sounds like I need this: Does anyone have these files backed up somewhere that they could post or email to me? Thanks

If it works outside of GameEx, then it's just a matter of getting the right command line setup in GameEx. For Zinc, there are 2 files that you can check: 1) "Run Last Game.bat" in the startup directory; 2) zinc log file (I forget the file name). Run the "Run Last Game.bat" file outside of GameEx and make sure it loads. If it does, then it's a problem with the GameEx setup. If it doesn't, then it's a problem with the command line you are sending. You can also check the zinc log file to see what the error is if you have the latter problem. If you can't get it going after checking both of those files, post them here and someone will take a look.

9.60 should have the fix, so checking the filters like you suggested would be a good way to go.

I don't know. I personally just go with the most recent version of MAME that can do what I need. For most things, I'm using 0.125 (I just haven't updated to 0.128 yet). For rotary joystick games, I'm using MAME Analog+ 0.90u1 because it's the most recent version available. For gun games, I'm using 0.104u6 since it's the newest version that will work with the WinGun drivers.

There was a reason I wanted to launch multiple versions of MAME.... This is one of those reasons. Sometimes you have to use an older version of MAME to run specific games. It would be nice to have a single version of MAME, but it just doesn't seem to work out that way.

If "Allow Imperfect Games" doesn't fix it (it should), then you might want to check what version of GameEx you are running. Tom fixed a bug where games were still being filtered off even when added to the "do not filter" list. I don't remember what version that was, but it was a few months back.

Galaga is imperfect last I checked, so it will be filtered out by "only working". You need to add the rom to the "do not filter" list.

There's also more information on the main GameEx homepage regarding added features for registered users. It may be more readable than what you find with a forum search. Either way will work though! http://www.gameex.com/Donate/tabid/71/Default.aspx Also, the registration fee has been temporarily dropped to $22. There's a blurp about that on the linked page.

I got the guns working in MAME 0.104u6 which is apparently the last version that works with that driver. The only down side to using it is that it has the nag screen enabled and the cross hairs are turned on by default. I grabbed the 0.104 source and the updates from u1 through u6 and applied them with HK's MAME Compiler and then manually edited the code to remove the nag and cross hairs. The problem is that I get an error during compile. I posted a question about it in the compiler thread, so hopefully HK will get a chance to take a look today. I suspect the error has to do with different versions of MinGW (or is it MinWG). Anyway, Once I get that going, I'll be good to go! I already added the gun games to my MAME_Loader code. Once I get MAME compiled, I can put the keyboard away!

I need to compile an older version of MAME (0.104u6) to get my guns working. I am able to apply patches and edit the code manually to get what I want, but when I try to compile I get an error. I'm assuming this is due to different MinGW versions, but I don't know. Does anyone have a suggestion? Deleting Object Folder... Compiling Mame... Using Parameters ARCHOPTS=-march=athlon-xp ... cc1.exe: error: unrecognized command line option "-Wno-unused-functions" mingw32-make: *** [obj/mame/artwork.o] Error 1 Finished! 0 Hours 0 Minutes and 2 Seconds Elapsed. After playing around for a few more minutes, I found that if I set "Disable Warnings as Errors" I can get farther, but it still crashes. Here's the much longer error... Deleting Object Folder... Compiling Mame... * snip for readablility *

Heh, doesn't really matter to me anyway. I went with No-Intro...

I totally agree. There are hundreds of games to start with. If you add all the variants, the list would be easily in the thousands if not higher! I'm not sure if it's really a problem using the base game for the description of a hacked version anyway. Perhaps GameEx will automatically match them to the official game anyway?

So if it's not finished, can you just call it "User Configurable" instead

Any of those 3 would be great! SNES, NES, and Genesis are the 3 main systems for me! N64 has never played that well due to poor controls (course I just got my Logitech Rumble Pads the other day, so that may not be an issue anymore ).

This is a silly suggestion since it could be more easily included in GameEx directly, which would make it easier and a lot more user friendly. BUT, you could use a script that runs at startup to copy one of your files from your audio files to an intro audio location. You could even use a Hard Link to keep from actually copying the file (reduces HDD usage and file copy time). Then, just point GameEx to that file. If I understand the problem correctly, this could be a usable workaround. EDIT: There are several programs out there that appear to do just this task I described. The one I'm linking was written primarily for copying a random bitmap to your system directory for a random background each time you start up Windows. This would work just fine for this task too! link - DOH, Dead linky!!! EDIT2: Well, since that link is dead, I found another way to do it with AHK. Read this thread if you want to see the details... total = 0 Loop, %a_musicdir%\*.mp3 { total += 1 } Random, select, 1, %total% Loop, %a_musicdir%\*.mp3 { IfEqual, A_Index, %select%, Setenv, file, %A_LoopFileFullPath% } FileCopy, %file%, C:\Music\IntroSong.mp3 Just adjust the location you want the file stored and point to that file in GameEx. Good to go!

I just got my Namco's working with the driver over the weekend. I still have to test them in MAME, but I think I should just need to get it configured and start shooting! The WinGun driver actually allows for up to 4 guns at once! That means that you could have your 2 Namco's and your 2 TopGun's hooked up at once Tempest!!!!

There is limited customization available for editing menus. Basically, there are only 2 ways you can display your menus... standard (everything is in sub-menus) and flat (everything is on the front page). I think you want to enable "flat menus" for what you are describing.

You can set it up to work however you want. AHK scripts are just programs that do whatever you code them to do. If you want them to run something and then exit, you can do that. If you want the script to stay active until you kill it, that also can be done. If you want it to stay active until another process ends, that's easily doable too. I wrote a little wrapper for MAME called MAME_Launcher that launches MAME as I want and then waits till the mame.exe process no longer exists. It then ends that AHK script and GameEx takes over. AHK is just a programming language, so it isn't limited by anything other than your imagination, creativity, and coding capabilities! If you need help with the coding, just ask and we'll try to help out the best we can.

Yup, stripped down versions of WinXP have been a problem in the past. That thread will explain the problem...

Sounds like a complicated solution, but sometimes that's the only way. The only other thing I could suggest if you were interested in changing the way you load games is to use AHK scripts rather than batch files. You get more control with that and you can even set up hot keys right in the script. It makes things a nice, clean, single file solution. I wouldn't change things as long as what you have is working, but it might be a better way to go if you redo things or others read this thread. Nice work!

Perhaps that would be a good work around that Tom could consider implementing. It seems a bit like a hack (closing the game then reloading it), but I don't know of any other way to get around getting the sound back.