Ced-le-pingouin

Hi,

I don't know if something similar has been asked before on the forum, I searched for emulators and did not find anything.

I have had NeoRAGEx, Mame32, and Nebula emulators (mainly NeoGeo and CPS-1&2 games) for a very long time on my Inspiron 8600, and they always worked fine with the omega drivers. Then I quit playing these for a little while, and now I tried to launch them again, but I have many problems.

The most weird is NeoRAGEx. When I run it, the screen is black, but I know the app is running, because if I hit Esc, it quits, as it should. After scratching my head for a long time trying all sorts of things (enable or disable many options in Omega or ATT) without any luck, I finally discovered that, for an unknown reason, NeoRAGEx believes I have a second monitor attached, or kind of. But I have not. The second monitor is disabled in the Advanced options of the omega drivers, at least until I really connect a second monitor. But it is shown in the standard display properties in Windows (although it says it is not attached). If I connect a cable to the VGA output of my laptop, then NeoRAGEx runs and displays its menus, as it did before, and... on the laptop screen (thus display n°1). Weird.

As for Mame32 and Nebula, they worked very well before, too.

But now Mame32 (v70+) crashes if I enable Direct3D rendering, although it worked some time ago. Mame32 v109 is working though. So i'm wondering, has something changed in the drivers, regardind "older" DirectX support or functions, maybe DirectX/3D 7 ???

Nebula always worked with any gfx options if I recall correctly, but now it crashes badly (GPF-style) if I choose "Local Memory" (I think it means "video memory"), but works if I choose "System Memory" for screen rendering (RAM?). Here too, it seems something has changed in DirectX. And choosing Direct3D as a blitter crashes instantly no matter which memory I chose for screen rendering (worked before).

The weird thing is that Direct3D games like WoW work as usual.

Any ideas?

Ced