djrobx

Are you using some sort of front end for it? I helped someone get ePSXeCuTor working a while back. Whatever the case, you need to list all the different executables that need to be terminated using your setup. If you know a key sequence that reliably exits it, you can place it in the KeysToSendOnExit area, too. Either way, the advanced config is what you'll want to use for sure. What's in that copy.bat file?

In advanced config, can you support POV HAT positions for key mappings as well? On both my PSX and XBox game pads, the D-pad is assigned as a POV hat. So for visual pinball, I use the D-pad left for the left flipper. (The left and right triggers aren't crisp enough ... idea of using D-pad stolen from the old NES pinball game ) Also in the sample configs, the assign for exit buttons go up to 6. Does it support numbers higher than 6? Now that we have assignable exit coes, can they be assigned for MAME as well?

This is a job for the new advanced emulator config option. If you go into C:\Program Files\GameEx\CONFIG\EMULATORS, you'll see a couple .cfg files for Project 64 and Visual Pinball. Make a new file, EPSXE.cfg. I'm removing comments to make it more concise for posting. See the other files for comments on how to use this. I don't have ESPXE installed so I can't test this, but it should work. Once that's in place, open the GameEx config program and select EPSXE on the advanced config from the drop-down list for your EPSXE emulator section. [GENERAL] Enabled=True MapBack=True MapEscape=True KeysToSendOnExit= EmuWaitForKeys=True Process1=epsxe.exe Process2= Process3= Process4= [JOYMAPPING] JoymappingEnabled=FALSE [GAMEPADEXIT] MapGamePadExit=false

I am very interested in StepMania, but I couldn't find music for it. Any tips? -- Rob

I'm just running 32 bit windows on my A64. I don't want the headaches. -- Rob

I'd say yes, create a coffee house type of forum. I think the need for it will be inevitable as your userbase grows. You might move the arcade cab discussion there, too, to keep the focus here more on GameEx and GameEx support. -- Rob

There's an option "Enable Random Game" under the "Disable/Enable Features" config screen. Or if you prefer to edit the ini, in the C:\program files\GameEx\config\GameEx.ini there's ShowRandomGame=True Is it not working? I haven't tried to disable it.

Either some component of 2.0 beta 1 is not uninstalling properly on your system, or 2.0 beta 1 is a way to consistently reproduce an unrelated issue. Version 4 also worked fine on my 2.0 beta 1 system.

Have you tried rebooting post uninstall? Can you verify that the C:\windows\Microsoft.NET\Framework\v2.0.40607 is gone? Tom, would definitely still try recompiling after installing the VC6 service pack. I lived through those, they made some VERY significant changes with regards to the standard headers and macros. -- Rob

Gibbon, uninstall Framework 2.0 ... and download new 2.0 from the link I posted above. Should fix the problem. You should also try leaving it uninstalled and seeing if it it will work with 1.1. You can have both 1.1 and 2.0 installed at the same time. Yes, Tom, it works fine on both my systems now.

Ok here's what happened with my testing. Installed GameEx. Copied my config. Tried to run. Failed to create fonts. I recognized that one - video acceleration was not turned up. Turned up video acceleration. GameEx runs fine. Installed the latest version of .NET framework 2.0 Bombs in exactly the same spot as thefunkygibbon's Updated to the latest GameEx on my desktop PC. The same bomb now happens on my desktop, too. It wasn't a problem before, but now you really do have an app that's incompatible with 2.0! *Edit* ... Argh, after re-reading avast's post, I realized I downloaded the wrong .NET version. Microsoft calls the new version "Beta 2" and has not updated their "Beta" site to point to the new download. Here is the correct place to download 2.0 beta 2 http://www.microsoft.com/downloads/details...&displaylang=en *Edit* and now it's working again on my desktop...

He probably can't reinstall DirectX. Once you have XP SP2, the DX installer does absolutely nothing, and I'm assuming the same is true of Windows Server SP1. Did you compile PlayVideoBak.dll yourself, or is it an existing API? It has some downright strange dependencies listed if you open it with depends.exe. MSJAVA.DLL, WZCSVC.DLL (wifi config service) to name a couple. I don't have MSJAVA.DLL so I don't think it's an issue, just something odd. I'm going to install GameEx 5 on our server 2003 as soon as my rooomie leaves. I'll see if I can duplicate the problem.

If you're running 2k3 server, make sure video acceleration is turned up. GameEx doesn't boot on my machine if acceleration is turned all the way to None, which is the default for Microsoft server OS's. You may have already changed that though since you use it for HTPC functions, but something to check.

taskkill /im EPSXE.exe should do the trick. If EPSXE doesn't want to play nice with a standard kill request, you can also do taskkill /f /im EPSXE.exe which force-kills it. Try without /f first. -- Rob

Sounds like a nice idea for the pinned feature requests topic up above. I suggest placing this sort of thing there, so Tom can refer to it when he's considering what features to add next.

I really wish Nvidia would get it together with the 7 series drivers. I moved from ATI to NVidia because I was tired of ATI driver headaches, and NVidia has been worse!

Run dxdiag and make sure you get through the graphics, sound and input tests. Try removing the nvram files, cfg files, etc. Start fresh. -- Rob

Snes9x is the only other "100%" SNES emulator out there, but ZSnes is the better of the two for Windows. First delete zsnesw.cfg and try again. If Zsnes doesn't run on your PC, I'd first be looking into upgrading the video drivers. There's probably something wrong there that may affect other emulators as well. Snes9x shouldn't be too difficult to get working under GameEx. -- Rob

*Bows to the almighty Tom* Can't wait to play with these features!! -- Rob

I don't think gameex supports it yet. It has been requested, though.

You can run Project64 with show desktop=false if you're using a DirectX video plugin. You will need to specify "Fullscreen after ROM load" in the Project64 options. Always set "Showdesktop=True" until you've got the emulator working the way you want it. That way you can see what's going on and make changes to the emulator configs. My config is: Enabled=True StartPageName=Nintendo 64 Games TitleText=Nintendo 64 Games StartPageLogo=n64 RomFilter=*.v64;*.zip;*.z64;*.rom RomsInFolders=False ROMPath=R:\Games\n64\roms SnapPath=R:\Games\n64\snaps WorkingPath=R:\Games\n64\Project64 MapKeys=True WaitBeforeKeys= SendKeys= ReplaceDash=True ReplaceUnder=True Capitals=True RemoveBrackets=True AlsoLaunch= ShowDesktop=False Debug=False MapFile= OLDatZip= Command=Project64.exe [ROMPath]\[RomFile] TitlePath= BoxPath= LaunchBefore= LaunchAfter= CartPath=

Sure, that sounds like a good idea. Better than flooding your forum with attachments. I'll let you know when I'm ready - work decided to slam me for the holiday weekend. Nice!

When you are first setting up the emulators, set "Show Desktop" to true. ZSnesW appears in a window by default, and will be hidden from view. You need to set it for one of the full screen modes in the video configuration menu. Once you are happy with the way the emualtor works, you can try changing "Show Desktop" to false, to hide the Windows desktop while the emulator is launched.

I don't think 2.0 installs 1.1. For me they're all independent entries. I can uninstall either 1.1, 1.1 hotfix, and 2.0 from add/remove programs. If the issue is that he has 2.0 and not 1.1, you should just require 1.1. I'll try removing 1.1 to find out if that causes that behavior.

He says he's tried two different options (1 and 2) and still has the problem. You might try editing GameEx.ini directly and looking for the MediaCenterMode line and making sure it's set to 2. MediaCenterMode=2