Various Problems: GameEx on Win7 x64/Lenovo T500

[Geronimo]

This is my first post here, so i'd like to say "Hi" to everyone. (;

Let me begin by making clear that i'm not a PC noob. I've been "working" with emulators and frontends for more than 10 years now, and i've tested GameEx for short periods a few times in the past (my machines were not powerful enough to handle GameEx easily, so i didn't donate until now).

Nearly a year ago i got a new machine, A Lenovo T500 (Switchable graphics, 4GB RAM). I've switched from Vista x64 to Win 7 x64 some months ago, and the machine is running perfectly well. I use the machine for working and, of course, for lots of gaming and emulating (; . I've played about 50 native Windows games from various years on the machine, and tested maybe 30 emulators for various systems. Everything worked perfectly well, no problems at all.

Today i started evaluating GameEx (again). Install went smooth, but i quickly encountered a number of very frustrating problems. After lots of tweaking GameEx itself is running very well, but there's other issues. I'll start with the most annoying problem for now. Oh, i've searched this forum for about two hours but couldn't find any answers.

My main problem:

It takes a very long time to return to GameEx after exiting an emulator, usually about 5 to 10+ seconds. That may not sound like much time but i can see no reason at all for the delay, and it's very annoying, especially when quickly "browsing" through a number of games. It makes GameEx "feel" very unresponsive. The problem happens with the latest MAME build (both official and mameuifx32) and Snes9x (didn't test others yet). I've disabled all artwork and extended functionality in GameEx and the emulator's config, as well as controller support and other stuff. I've basically tried to disable _everything_ that might interfere. The log doesn't show anything ununsual. To describe the effect more precisely: i have the "hide desktop" and "hide taskbar" functions disabled so i can see what's going on while i'm in the phase of setting up GameEx (the problem occurs both in windowed and full screen modes). What happens is that immediately after i exit an emulator GameEx springs up from the taskbar, and then just sits there for some time, doing nothing. CPU usage is around 0% during that time. The emulator's proccess is definitely gone _before_ GameEx restores itself from the taskbar. After the long delay GameEx refreshes its screen and becomes responsive again.

Question(s): is this a known problem, and can i fix it? Is there a way to switch to a more verbose logging level so i can see what's going on between closing the emu and GameEx resuming normal operation? Can someone explain to me what exactly happens during that delay, so i can identify a possible bottleneck?

That's it for now. Long post, but i wanted to give as much helful info as possible. I think GameEx is a wonderful piece of software and pretty much the only one of its kind, and i'd happily donate money if i can be sure it'll perform the way i expect it to on my system.

Please let me know if you need more information.

[Brian Hoffman]

This is my first post here, so i'd like to say "Hi" to everyone. (;

Let me begin by making clear that i'm not a PC noob. I've been "working" with emulators and frontends for more than 10 years now, and i've tested GameEx for short periods a few times in the past (my machines were not powerful enough to handle GameEx easily, so i didn't donate until now).

Nearly a year ago i got a new machine, A Lenovo T500 (Switchable graphics, 4GB RAM). I've switched from Vista x64 to Win 7 x64 some months ago, and the machine is running perfectly well. I use the machine for working and, of course, for lots of gaming and emulating (; . I've played about 50 native Windows games from various years on the machine, and tested maybe 30 emulators for various systems. Everything worked perfectly well, no problems at all.

Today i started evaluating GameEx (again). Install went smooth, but i quickly encountered a number of very frustrating problems. After lots of tweaking GameEx itself is running very well, but there's other issues. I'll start with the most annoying problem for now. Oh, i've searched this forum for about two hours but couldn't find any answers.

My main problem:

It takes a very long time to return to GameEx after exiting an emulator, usually about 5 to 10+ seconds. That may not sound like much time but i can see no reason at all for the delay, and it's very annoying, especially when quickly "browsing" through a number of games. It makes GameEx "feel" very unresponsive. The problem happens with the latest MAME build (both official and mameuifx32) and Snes9x (didn't test others yet). I've disabled all artwork and extended functionality in GameEx and the emulator's config, as well as controller support and other stuff. I've basically tried to disable _everything_ that might interfere. The log doesn't show anything ununsual. To describe the effect more precisely: i have the "hide desktop" and "hide taskbar" functions disabled so i can see what's going on while i'm in the phase of setting up GameEx (the problem occurs both in windowed and full screen modes). What happens is that immediately after i exit an emulator GameEx springs up from the taskbar, and then just sits there for some time, doing nothing. CPU usage is around 0% during that time. The emulator's proccess is definitely gone _before_ GameEx restores itself from the taskbar. After the long delay GameEx refreshes its screen and becomes responsive again.

Question(s): is this a known problem, and can i fix it? Is there a way to switch to a more verbose logging level so i can see what's going on between closing the emu and GameEx resuming normal operation? Can someone explain to me what exactly happens during that delay, so i can identify a possible bottleneck?

That's it for now. Long post, but i wanted to give as much helful info as possible. I think GameEx is a wonderful piece of software and pretty much the only one of its kind, and i'd happily donate money if i can be sure it'll perform the way i expect it to on my system.

Please let me know if you need more information.

When gameex launches a game it minimises itself, the emulator runs, sets the screen to the resolution defined in the emulator settings, then you exit the emulator, the resolution switches agan to your desktop resolution, once completed the process is closed, gameex see's that the process is closed and comes into focus, if gameex is set to run at a diffrent resolution it switches again.

Try and set gameex to run at the same resolution as your desktop. Also define your emulators to also use that same resolution. This should speed things up. Also post your log, you may net think it is anything spectacular but we can see your specs and other usefull info.

[Geronimo]

Thanks for replying so quickly!

Try and set gameex to run at the same resolution as your desktop. Also define your emulators to also use that same resolution. This should speed things up. Also post your log, you may net think it is anything spectacular but we can see your specs and other usefull info.

Neither GameEx nor the emulators are set up to change the resolution.

Here's an exmaple log. I've noticed that Video RAM is not recognized correctly. I don't think this is the source of this current problem, but it could explain other issues i'm having (more on that later, probably).

18:30:58.6  23.01.2010:  GameEx: Version 10.37: Starting Log
18:30:58.6  23.01.2010:  Operating System Platform: Win32NT
18:30:58.6  23.01.2010:  Operating System Name: Windows 7
18:30:58.6  23.01.2010:  Operating System Version: 6.1.7600
18:30:58.6  23.01.2010:  Aero running
18:30:58.6  23.01.2010:  Initializing Vista/Windows 7 volume control
18:30:58.6  23.01.2010:  Checking for versions of .net Framework installed
18:30:58.6  23.01.2010:  .net Framework 2.0 Installed
18:30:58.6  23.01.2010:  .net Framework 3.0 Installed
18:30:58.6  23.01.2010:  .net Framework 3.5 Installed
18:30:58.6  23.01.2010:  Intel(R) Core(TM)2 Duo CPU T9550 @ 2.66GHz, 3990MB
18:30:58.6  23.01.2010:  2,66Ghz - 2 Cores or CPU's
18:30:58.6  23.01.2010:  Running Randomize()
18:30:58.6  23.01.2010:  Loading PlugIns
18:30:58.6  23.01.2010:  Checking for applications to Launch On Startup
18:30:58.6  23.01.2010:  Running Misc startup tasks
18:30:58.6  23.01.2010:  Setting Menu types
18:30:58.6  23.01.2010:  Opening Configuration File
18:30:58.6  23.01.2010:  Getting Configuration Values
18:30:58.6  23.01.2010:  Using Theme: Default - Default
18:30:58.6  23.01.2010:  Checking for alternate Image Directory for Theme: Default - Default
18:30:58.6  23.01.2010:  Launching HideOS.exe
18:30:58.6  23.01.2010:  Initialising Video/MNG DLL's
18:30:58.6  23.01.2010:  Hiding Taskbar
18:30:58.7  23.01.2010:  Is Media Center running?
18:30:58.7  23.01.2010:  Checking/Creating LCD Registry values
18:30:58.7  23.01.2010:  Check Media Center Exit/Start Mode
18:30:58.7  23.01.2010:  Media Center Mode 0
18:30:58.7  23.01.2010:  Snap Delay set to: 2
18:30:58.7  23.01.2010:  Get other settings
18:30:58.7  23.01.2010:  Mouse Input is disabled
18:30:58.7  23.01.2010:  Using DirectInput for keyboard input
18:30:58.7  23.01.2010:  Start work for Form
18:30:58.7  23.01.2010:  Getting Original Screen Size
18:30:58.7  23.01.2010:  Compacting Database
18:30:58.9  23.01.2010:  Opening Database Connection
18:30:58.9  23.01.2010:  Initializing Component
18:30:58.9  23.01.2010:  Retrieving resolution setting
18:30:58.9  23.01.2010:  MAME Path is: Z:\Emulators\Arcade\MAME 0.136
18:30:58.9  23.01.2010:  MAME EXE file is: mame.exe
18:30:59.0  23.01.2010:  ROM Path is: Z:\Roms\Arcade\MAME SuperSet
18:30:59.0  23.01.2010:  Catver.ini is located at: C:\Program Files (x86)\GameEx\DATA\catver.ini
18:30:59.0  23.01.2010:  controls.ini is located at: C:\Program Files (x86)\GameEx\data\controls.ini
18:30:59.0  23.01.2010:  History.dat is located at: C:\Program Files (x86)\GameEx\DATA\history.dat
18:30:59.0  23.01.2010:  nplayers.ini is located at: C:\Program Files (x86)\GameEx\DATA\nplayers.ini
18:30:59.0  23.01.2010:  MAMEinfo.dat is located at: C:\Program Files (x86)\GameEx\DATA\mameinfo.dat
18:30:59.0  23.01.2010:  Loading Controls.ini map file
18:30:59.0  23.01.2010:  Snap Path: Not Found
18:30:59.0  23.01.2010:  AVI Snap Path: Not Found
18:30:59.0  23.01.2010:  Flyer Path: Not Found
18:30:59.0  23.01.2010:  Cabinet Path: Not Found
18:30:59.0  23.01.2010:  Title Path: Not Found
18:30:59.0  23.01.2010:  PCB Path: Not Found
18:30:59.0  23.01.2010:  Artwork Preview Path: Not Found
18:30:59.0  23.01.2010:  Panel Path: Not Found
18:30:59.0  23.01.2010:  Manual Path: Not Found
18:30:59.0  23.01.2010:  Icon Path: Not Found
18:30:59.0  23.01.2010:  Marquee Path: Not Found
18:30:59.0  23.01.2010:  Loading Custom Emulators
18:30:59.0  23.01.2010:  Loading Emulator 1: [Console] Nintendo SNES (Snes9x)
18:30:59.1  23.01.2010:  Using Version 3 Themes Animations
18:30:59.1  23.01.2010:  Using General Font: Trebuchet MS
18:30:59.1  23.01.2010:  Using Title Font: Trebuchet MS
18:30:59.4  23.01.2010:  Initialising DirectDraw
18:30:59.4  23.01.2010:  Creating DirectDraw Device
18:30:59.4  23.01.2010:  Using Device: ATI Mobility Radeon HD 3650 
18:30:59.5  23.01.2010:  1983mb video memory available
18:30:59.8  23.01.2010:  Setting Resolution to 1680x1050 32 bit color
18:30:59.8  23.01.2010:  Creating DirectDraw Surfaces
18:30:59.8  23.01.2010:  Creating Primary Surface - Full Screen Mode
18:30:59.8  23.01.2010:  Creating Back Buffer
18:30:59.8  23.01.2010:  Loading graphic Surfaces
18:30:59.8  23.01.2010:  Display is running at: 1680x1050 32bit color, 60hz
18:30:59.9  23.01.2010:  Creating Surfaces Flags
18:30:59.9  23.01.2010:  Creating Surfaces Misc and Dialogs
18:31:00.0  23.01.2010:  Creating Surfaces Volume
18:31:00.0  23.01.2010:  Creating Surfaces Arrows
18:31:00.0  23.01.2010:  Creating Surfaces GameEXlogo Text
18:31:00.0  23.01.2010:  Creating Surfaces Toolbar
18:31:00.0  23.01.2010:  Creating Surfaces Backgrounds
18:31:00.0  23.01.2010:  Creating Surfaces Toolbar Controls
18:31:00.0  23.01.2010:  Creating Surfaces GameEx Logo
18:31:00.0  23.01.2010:  Creating Surface Unselected
18:31:00.0  23.01.2010:  Creating Surfaces Home & Exit
18:31:00.1  23.01.2010:  Creating Surfaces Snaps
18:31:00.1  23.01.2010:  Creating Surfaces Menu and List Bars
18:31:00.3  23.01.2010:  Creating Fonts
18:31:00.3  23.01.2010:  Creating Game Font
18:31:00.4  23.01.2010:  Creating Game Font Faded
18:31:00.4  23.01.2010:  Creating Title Font
18:31:00.4  23.01.2010:  Restoring Title Font From Cache
18:31:00.6  23.01.2010:  Creating Font Black
18:31:00.7  23.01.2010:  Creating Font Black Small
18:31:00.8  23.01.2010:  Fonts Created Succesfully
18:31:00.8  23.01.2010:  1920mb video memory left available
18:31:00.8  23.01.2010:  Creating instance of global keyboard hook
18:31:05.8  23.01.2010:  Initialising Bass Audio Library
18:31:05.8  23.01.2010:  Attempting to load game list
18:31:05.9  23.01.2010:  Applying Language/Text
18:31:05.9  23.01.2010:  Text/Language: English
18:31:06.0  23.01.2010:  MAME CMD options: -nowindow -joy -skip_gameinfo
18:31:06.0  23.01.2010:  Loading last used Game List
18:31:06.1  23.01.2010:  Loading Start Page
18:31:06.1  23.01.2010:  Cannot Load Play List. Check Path and filename
18:31:06.1  23.01.2010:  Creating DirectSound Device
18:31:06.1  23.01.2010:  Trying: Primärer Soundtreiber
18:31:06.1  23.01.2010:  Loading Sound Files
18:31:06.1  23.01.2010:  DirectSound Device Created Successfully
18:31:06.1  23.01.2010:  Gamepad/Joystick disabled
18:31:06.1  23.01.2010:  Initialising DirectInput for Keyboard support
18:31:11.2  23.01.2010:  Initializing MCE Remote
18:31:11.2  23.01.2010:  Playing intro sound file
18:31:11.2  23.01.2010:  Initialization OK! Starting GameEx!
18:31:11.3  23.01.2010:  Testing Main Loop Once: Processing Frame
18:31:11.5  23.01.2010:  Testing Main Loop Once: Main Loop ran successfully
18:31:18.4  23.01.2010:  Validating: Emulator_1: Custom Background: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Custom Background Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Snap Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Snap Path Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Custom Art Path 1: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Custom Art Path 1 Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Custom Art Path 2: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Custom Art Path 2 Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Custom Art Path 3: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Custom Art Path 3 Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Control Panel Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Control Panel Path Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Instructions Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Instructions Path Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Database: [Console] Nintendo SNES
18:31:18.4  23.01.2010:  Validating: Emulator_1: Title Snap Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Title Snap Path Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Box Art Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Box Art Path Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Cart Art Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Cart Art Path Does not exist
18:31:18.4  23.01.2010:  Validating: Emulator_1: Manual Path: 
18:31:18.4  23.01.2010:  Warning: Emulator_1: Manual Path Does not exist
18:31:18.5  23.01.2010:  Restoring Emulator from Cache
18:31:18.5  23.01.2010:  Restoring Emulator Database From Cache
18:34:16.4  23.01.2010:  Exiting GameEx!
18:34:16.4  23.01.2010:  Saving Settings
18:34:18.2  23.01.2010:  Disposing Plugins
18:34:18.2  23.01.2010:  Closing database connection
18:34:18.2  23.01.2010:  Checking for applications to Launch On Exit

[Brian Hoffman]

try turning off Windows aero, use a basic theme.

[Geronimo]

Just tried switching to the "Windows 7 Basic" theme, no change with the delay unfortunately. I've tried "measuring" the delay, seems like it's very close to 10 seconds every time. I'll gladly try any other suggestions.

[headkaze]

It's not really that long when you consider how fickle Windows can be about changing between apps/windows. But there are some things you can try. First of all some anti-virus software can slow processes down as they scan on the fly so you can try disabling it and see if it improves things. Another thing to try is download Process Monitor and have a look at exactly what is going on. I don't remember GameEx taking long to exit a game but it may just be designed to wait for things such as changing resolution (even though you don't change resolution GameEx has no way of knowing so probably waits just incase). On top of that it has to reinitialize itself and that would understandably take a bit of time.

[Tom Speirs]

Just wanted to add this has been a previously reported problem with Windows 7 if I recall. I dont see any problems here though, although it could be that 5 seconds does not seem long to me.

Are you running latest drivers and updates? What video card is in the machine?

Also, at higher resolutions there is the potential for reloasing the graphics to take longer. Although you say its the same when windowed.

[Geronimo]

Thanks again for the replies guys.

Well, i've tried disabling my virus scanner (didn't think of that before), but the issue persists. As i've said, both GameEx and the emulators i'm testing are set up to not change the resolution from what the desktop is set at, so mode switching is not the issue i'd say. Besides, i can clearly see what's happening on the desktop, as i'm currently not using any of the "hide os" features in GameEx because i'm still setting up stuff. I can see GameEx "springing" from the taskbar and getting focus, and the _real_ wait starts just after that.

Tom, thanks for chiming in. I wouldn't have a problem with 5 seconds, but i've seen delays from ~10 to over 20 seconds. As i've said, this doesn't sound like much time, but it's annoying having to look at a black screen on a machine that is powerful enough to easily handle GameEx and the emulators as such. To experience my pain, just look at your Desktop with your hand on the mouse and do nothig while counting "1-Mississippi, 2-Mississippi, 3-Mississippi etc." up to 10 or 15. This should give you pretty good impression on how horribly long 10 seconds can be if you're waiting for stuff to happen (; .

The graphics card is a ATI Mobility Radeon 3650. As this machine is a notebook with special features i have to use the drivers supplied by Lenovo. All drivers are up-to-date (i'm quite anal about using the latest drivers).

Some additional info that might be important:

- I'm using a Logitech G13 unit, but the problem persists no matter if the unit is hooked up or not. I've tried ending all "Logitech processes", too, as well as disabling all "hooking" functions in GameEx.

- My emulators and Roms are stored on a file server (Windows 2008 Server via 100mbit), on a share i'm mapping to my "Z:" drive. The share is mapped automatically on startup, and i can access it from all Windows apps without entering user credentials (i'm using the same username/pw on the client and server). When i start GameEx after booting the client machine it gives me an error message about not being able to access Rom directories though. I have to start the config app once, browse to the Rom location and then start GameEx again to make the error message in GameEx disappear. The odd thing is that the drive is marked with a little red "x" symbol in the config app's dir browser, but can be browsed and selected as a source without entering user credentials. This could be or could not be connected to the original problem, and is a major pita by itself. Could it be that GameEx is reading Rom directories each time a emulator is exited, and/or is using methods of reading network drives that Win 7 doesn't like? If GameEx has to wait for a complete dir scan, this could explain the delay i'm seeing.

[headkaze]

- My emulators and Roms are stored on a file server (Windows 2008 Server via 100mbit), on a share i'm mapping to my "Z:" drive.

Try moving a few Roms to a local drive and see how fast it returns then.

[Tom Speirs]

- My emulators and Roms are stored on a file server (Windows 2008 Server via 100mbit), on a share i'm mapping to my "Z:" drive. The share is mapped automatically on startup, and i can access it from all Windows apps without entering user credentials (i'm using the same username/pw on the client and server). When i start GameEx after booting the client machine it gives me an error message about not being able to access Rom directories though. I have to start the config app once, browse to the Rom location and then start GameEx again to make the error message in GameEx disappear. The odd thing is that the drive is marked with a little red "x" symbol in the config app's dir browser, but can be browsed and selected as a source without entering user credentials. This could be or could not be connected to the original problem, and is a major pita by itself. Could it be that GameEx is reading Rom directories each time a emulator is exited, and/or is using methods of reading network drives that Win 7 doesn't like? If GameEx has to wait for a complete dir scan, this could explain the delay i'm seeing.

The mapped drive issue is because of the .net framework. Not much you can about it other than use UNC paths. Cant see it would cause slowdown though.

[Geronimo]

headkaze, i'll try copying the stuff needed for testing GameEx to a local hd, and will report back later. I doubt this will make a difference though, unless GameEx is reading lots of info from the drive each time an emulator is exited. It's worth a try anyway.

Tom, is there a chance of fixing this network share thing, or maybe creating a workaround? It's kind of a showstopper for me with the current setup i'm using. I'd have to completely change my approach to the whole frontend subject (and lots of other emulation/gaming related stuff i'm doing) to compensate for this problem. I have my whole "emulation/gaming framework" set up to use that mapped drive letter, in order to be able to use stuff on various machines and make everything portable.

Thanks again for the suggestions and support.

[Drakendoder]

i have no clue as to resolve the issue, but for clarification about OS, Anti-Virus and such. I use Win7 x64 with AVG total security running constantly(4GB of DDR2Ram, quick processor though Phenom X4 965) and i experience no delay. It takes approx. 1-1.5 seconds to return to game-ex. Just an fyi for future contemplation.. good luck

[Tom Speirs]

i have no clue as to resolve the issue, but for clarification about OS, Anti-Virus and such. I use Win7 x64 with AVG total security running constantly(4GB of DDR2Ram, quick processor though Phenom X4 965) and i experience no delay. It takes approx. 1-1.5 seconds to return to game-ex. Just an fyi for future contemplation.. good luck

Thanks for posting, are you using an NVIDIA video card?

[Drakendoder]

no ATI Radeon HD4850 512MB DDR3

[Geronimo]

Sorry for the late reply, RL got in the way.

As a test i've now copied my whole emulation setup to a local hd. the delay when exiting games is still there. Maybe it's a bit shorter than before but still very noticeable (approx. between 5 -10 secs.). I've also noticed another post with a problem which appears to be similar to mine.

This is just a hunch, but i think the Logitech G13 and/or its drivers may be the source of the problem. I've noticed the backlight of the unit switching off and on sometimes when GameEx is in the "hang" phase. The G13 drivers install both a mouse-type and a joystick-type device by default. One of these devices can then be mapped to the thumbstick on the G13. This means the two devices are "dummies" without any actual functionality unless they are mapped.

[bkenobi]

The best way to determine if hardware is the source of your problem is to remove it and try again. I had a computer that wouldn't boot (wouldn't even post actually). It turns out that my USB printer had locked up and was screwing up the system. I NEVER would have thought that could happen.

Anyway, I'd unplug all peripherals down to the basics (it's a laptop, so that's pretty much everything) and turn off all extra software/services (including anti-virus, etc). If that fixes things, AWESOME! Just add stuff back in in small groups until you see what's breaking things.

[T. Goodchild]

Are you using the same HD for your OS and data/games? If so, I've noticed heavy disk usage with win7 without necessarily doing anything, probably indexing nonstop so I'd look into disabling some services to make sure it's not constantly accessing and cataloging files which may add to any apparent response lag. Also try defragging the drive or upgrade to a 10k or ssd. One other weird solution I might suggest is to disable some 3rd party input/usb devices. One time it had really slowed my emulation when I had several controllers hooked up at once while using Joy2Key for all of them.

[Lancerguy]

Ya, I hate to just randomly add to the conversation, but I don't think I saw whether you had tried headkaze's suggestion about checking for heavy CPU or hard drive activity during the "hang". If you run in windowed mode, an easy way to see would be to open task manager (ctrl+alt+del). You can watch the CPU at the bottom of the task manager, or go to the processes tab for a better look at what is using CPU. You might report back what % is being used while it's hanging, and what processes are using what % (especially GameEx). If you've copied your whole emulation setup to the local hard drive that the OS is on (which I definitely recommend for testing), you should also note the amount of hard drive activity during the hanging (i.e. Is the hard drive light on constantly, blinking rapidly, or not really on that much. That way at least we'll know if it's just slow, or if something is actually causing the system to pause or time out before re-loading GameEx.

Also, your system shows it has an ATI Mobility Radeon HD 3650. The ATI site shows that it doesn't have "switchable graphics" on it. Even so, if it DOES, I might suggest trying to disable it in BIOS. I'm not sure what your options will be in BIOS, but it's probably under "dynamic switching" or something of that sort, but there should be 3 options. There should be one for integrated, one for discrete, and an option that dynamically switches between the two as needed. I would suggest trying the integrated option for maximum performance (lower battery life though). GameEx shows 1920MB of video memory available because of ATI's "HyperMemory", which shares all available memory with the graphics card, so the card 'technically' has your entire RAM available to it. You probably have 1920MB of RAM available in general.

Also, I really don't think it has anything to do with the G13 device.

[Geronimo]

Of course i've monitored CPU and hd activity while running GameEx and trying to analyse my problem. As i've written before i have everything setup to not hide the OS and not change resolutions. No anomalies there, GameEx and the emulators aren't taxing my system very much. I've also written before that i'm playing numerous games and emulators without any problems at all, so i guess my system is basically working OK. GameEx is as of now the only gaming/emulation app that's giving me grief.

It's nice that you don't think the G13 is the source of the problem, but i beg to differ. I wrote before that sometimes when an emulator is exited the device light (backlit LCD display and keys) will briefly go off and on, as if the device is receiving a reset. That's not normal behaviour.

The graphics card could be the source of the problem as well. The machine has 4 GB of RAM, and GameEx is detecting "1983mb video memory available" which strikes me as odd. AFAIK the ATI graphics adapter has 256MB of dedicated memory.

To conclude this, let me repeat that there are at least two other users with a problem very similar to mine. A possible common denominator is Win 7 x64, which is used in all three cases IIRC.

[Geronimo]

Sorry for double posting, but i'm still looking for a fix to my problem. Tom, would you please inform me about whether you're looking into that problem or not? If i can try additional stuff or supply additional data i'd be happy to do so.

As i wrote, the fact that at least two other users are seeing what looks like the same problem i've described strongly hints towards a general problem or "effect" with the GameEx/Win 7 x64 combination. As more and more people are migrating to Win 7 and x64 Windows versions i guess the problem could become more urgent in the near future. If there was a way of finding out what exactly GameEx is doing after closing an emulator and before becoming active and responsive again it'd be much easier to analyze what is happening. Something like a debug build with extended logging would help tremendously, for example.

[GBBBS]

Sorry for double posting, but i'm still looking for a fix to my problem. Tom, would you please inform me about whether you're looking into that problem or not? If i can try additional stuff or supply additional data i'd be happy to do so.

As i wrote, the fact that at least two other users are seeing what looks like the same problem i've described strongly hints towards a general problem or "effect" with the GameEx/Win 7 x64 combination. As more and more people are migrating to Win 7 and x64 Windows versions i guess the problem could become more urgent in the near future. If there was a way of finding out what exactly GameEx is doing after closing an emulator and before becoming active and responsive again it'd be much easier to analyze what is happening. Something like a debug build with extended logging would help tremendously, for example.

Hi

i have absolute the same problem... my gameex toke also 15-20 second to back gameex..

hope anyone can help to fix that problem

Cya

[Tom Speirs]

Im happy to look into it, but its very difficuly to identify a problem when its not affecting everyone. I run Windows 7 x64 on three pcs, one running via remote desktop, and GameEx has always run like silk. Let me take some time to look over the thread again, I need to look it over to see exactly what the problem is again, as its got a little long!

[Tom Speirs]

Just wanyted to add - other than graphics, sound conflicts, which I think this is related to. The only other things that can affect delay returning GameEx, it if your listening to a radsio station, and possibly with MAME as it can post statistics over the network to provide the most played mame games list.

I see people suggested running at a lower resolution etc. Maybe you already tried this? Does the problem exist when running in windowed mode?

[Tom Speirs]

Just wanyted to add - other than graphics, sound conflicts, which I think this is related to. The only other things that can affect delay returning GameEx, it if your listening to a radsio station, and possibly with MAME as it can post statistics over the network to provide the most played mame games list.

I see people suggested running at a lower resolution etc. Maybe you already tried this? Does the problem exist when running in windowed mode?

Edit: Ill provide a version that provides additionaly logging shortly, so we an see where the delay is occuring.

[Tom Speirs]

Edit: Ill provide a version that provides additionaly logging shortly, so we an see where the delay is occuring.

I attach a GameEx.exe with more logging when exiting MAME. Let us know where the delay is occuring..

Cheers.

Tom.

GameEx.7z