ragbak

OK, @tthurman and @Tom Speirs: thank you for your help, I will upgrade Mame and then be cautious with Gamex updates from that point onward, i.e. I will read release notes first. I like the product very much!

Sorry, I misunderstood your initial request. Attached is the log right after update of the gamelist. With update I assume you mean updating mame and roms accordingly right? Is there a recommended Mame version to take, or just the latest version? log_newpc2.txt

Hello Tom, Thanks for looking into this. The path is indeed slightly different on the new machine, but will work. It does work with a number of donkey kong roms when started from Gamex. I updated the gamelist on the new system, but I don't see different behavior. I also updated gamex on the old system, so both systems are now on the same version level, and I updated the gamelist on the old system as well. Afterwards the 1942.zip rom does not work anymore on the old pc either... Problem is the same now on the old system as on the new. Well at least it's consistent behavior now in both systems, so I am getting somewhere. How to go forward from here, can I fix this? In what way? Thank you for taking your time with this. B.t.w. new logs of both systems attached. Regards, Peet log_newpc1.txt log_oldpc1.txt

I am running into a strange phenomenon which I cannot explain. I hope somebody can point me to the right path ;-) The problem: I have a game cabinet now ever since 2013 using Gameex as a front end and MAME (ver 0.145b) as one of the emulators. The PC running this is a windows 7 machine and kind off sluggish. I want to replace the PC with a newer and faster one running windows 10 Home edition. So I installed Gamex again on the new machine, and since I don't want the hassle of finding proper working roms with the lastest mame version, I decided to go for version 0.145b again (being quite lazy I admit, but time is an issue nowadays and I am quite happy with the library of roms gathered sofar). Next step is to go through the Gamex wizard. Completed it. Now I notice that not all MAME roms are functioning, some do, but others don't. How can that be? I ran the two systems (old and new) side by side and singled out just one of roms which does work on the old setup, but will not on the new setup: 1942.zip I took a peek in gamex' log.txt file and noticed the following difference: Old system: 19:17:28.8 4-12-2017: Running: cmd.exe /c C: C:\Emulators\Mame\mame.exe 1942a -rompath C:\Roms\MAME\Roms -nowindow -joy -skip_gameinfo -bezel -artpath artworkgameex New system: 19:15:12.30 4-12-2017: Running: cmd.exe /c C: C:\Emulators\Mame\Mame\mame.exe 1942 -rompath C:\Roms\MAME\Roms -nowindow -joy -skip_gameinfo -bezel -artpath artworkgameex In the roms directory there is only a file called 1942.zip (so no 1942a.zip there!) and all roms are in C:\Roms\MAME\Roms In fact the rom dirs are the same on both systems, with identical contents. I am sure about this because on the new system I copied the rom dir from the old to the new system. If I issue the following command on the new system, the game will run correctly: C:\Emulators\Mame\mame.exe 1942a -rompath C:\Roms\MAME\Roms -nowindow -joy -skip_gameinfo -bezel -artpath artworkgameex But apparently Gamex sees things differently and issues a command referring to 1942.zip. What also strikes me as strange is that when I start Gamex on the old system and go to All Mame games, it will show "1942 (Revision A)" at the top of the list. However the new system shows "1942 (Revision B)". How can that be, it's the same rom! Yes, I am 100% positive about that, checked and double checked. I also checked this behavior for a second rom: 1943.zip. Same issue, old system starts it as 1943u where new system tries to start it as 1943 so this is hapening with more roms, but not all. Totally puzzles me. I attached the config files of both systems and logs Oh, the versions used: old system: Gamex 14.40 new system: Gamex 15.05 Hope somebody can help. Regards, Peet GameEx newpc.ini GameEx oldpc.ini log_newpc.txt log_oldpc.txt

OK, thanks for paying attention to this issue. I will buy a second hand video card to get around this problem, that seems like the only way to go from here. Peet

OK, hope this log is better. But I have to tell tou I could only access this log after the PC was rebooted (but gameex wasn't started yet, so should be the log of the crash). Reason: when it crashes the PC is still powered on but completely isolated. I had the C: drive shared and mapped on another PC in my network, but I could not access it any longer over the network (no ping reply either). Peet log.txt

Lenovo model 832678G is a desktop system. I upgraded the Intel video driver to the latest from the intel website (see above). It's a driver problem I'm sure. I am just looking for any good advice to bypass the problem via Gameex (if possible at all) as I am pretty sure the main cause isn't solvable by anybody else but Intel...

I recently installed gameex version 12.98 on a clean XP SP3 system (home edition). Gameex crashes while navigating through random Gameex menus (or sometimes when I startup the radio or jukebox). The screen freezes. Pressing crtl+alt+del doesn't do a thing. After some time (about one or two minutes) the screen goes dark and pretty much the only thing left to do is to hold the power button for 5 seconds to power it down and boot the system again. Specs of my system: Lenovo model 832678G Pentium-D 2.8 GHZ with 3GB of RAM Intel 82945G Express chipset family DirectX version: 9.0c (4.09.0000.0904) In windows event log I see the OS crashes everytime because of: event ID 1003 Error code; 000000ea, parameter1: 890e74b8, parameter2: 89bdeb58, parameter3: 891cb0b8, parameter4: 00000001 (THREAD_STUCK_IN_DEVICE_DRIVER) Searching the internet I get the impression that the cause is the intel 82945G driver hanging in a loop. So I upgraded the driver to version 6.14.10.5402 (previous was 6.14.10.4906) but this did not help. Tried to switch of advanced graphics: did not help Tried to switch resolution to 800x600: did not help Also tried to disable or reduce HW acceleration in the OS: did not help, in fact I cannot disable it all together since then Gameex will detect that there is a problem with DirectX (which I can imagine). Hmm, I guess I'm stuck with an older system with Intel graphic drivers that do not really work great with directX and probably will not be updated anytime soon i.e. never. Just my luck Is there someway to bypass this problem? I would be happy to switch off some of the advanced graphical stuff on gameex, but what I have tried sofar doesn't work. Any suggestions and help would be welcome Attached are the gameex.ini and log.ini GameEx.ini log.txt

Hi Tom, Yes I did also enabled to option for advanced keyboard controls

Hello, I am fairly new to Gameexe, set it up a couple of weeks ago and purchased the lifetime membership. Got Mame and ZX spectrum emulation going and working. One issue though, no matter what I do (direct keyboard input or not), I cannot get the volume buttons to work. I configured buttons C and V for volume up/down but pressing them while gameex is running does not have any effect. This might be something stupid, I tried to find the answer on this forum and FAQ but did not see any. I use an IPAC-2 b.t.w. (don't know if that is of any concern). Attached the log and gameex.ini file Any ideas are welcome. Peet GameEx.ini log.txt