[me:]
>>anyway, the MAMEBoy I downloaded displays the menu at the
>>top of the screen and somehow manages to move Windows
>>CE's taskbar to the bottom of the screen.

>>The MAMEBoy I built does neither - I don't get menus, and
>>parts of the taskbar get overwritten. I poked around in
>>the Embedded Visual help files and the platform SDK but
>>couldn't find any way to move the taskbar, so I assume
>>it's some sort of undocumented hack or registry
>> setting...

[marconelly:]
> Taskbar on the bottom is the standard 2.11 feature. Not
> tricks and hacks there.
> Menu on the top is also standard for 2.11

But the MAMEBoy I got (from the MAMEBoy site) successfully
moves the PocketPC taskbar to the bottom of the screen
and shows the menu at the top. The MAMEBoy I built from
the sources I downloaded from the same site does neither.
That's what I'm confused / wondering about. There's a
command bar create, command bar show, etc. but nothing
happens (and I tried clicking around for invisible menus
too!). I adjusted the client rect up and down but got
no love.

> What you need to do is to move game display down (it's
> now centered as if the taskbar is down) To do that, look
> at the GDIDisplay.c
>
> Look for the code that looks like this:
> [...]

Thanks, I'll check this out. I already did some messing
around with the windows client rect and stuff but didn't
get very far.

> I'm dying to know how did you make it use gapi instead of
> gamex!

Sorry to disappoint you...but I didn't. At first, I thought
I would need to (because of the GAMEX linker errors), but
I couldn't get it to work.

What I was doing was using the CGAMEX.CPP file from the
iMAME source distribution. It's basically the same
interface as MAMEBoy's CGAMEX.CPP but modified so that
internally the functions use GAPI (GX).

> Is there any speed increase comparing to
> a standard mameboy for E-125 that you can get from my
> site? Can you please send me your source with some brief
> explanation what you changed in it to make it use
> gapi?

Well, when I was trying this, I did get it to compile, but
when I ran it it would give me a "no DSA" error. So I
looked around and it seemed the GXOpenDisplay (or whatever
it's called) wasn't getting passed an HWND, so I figured
that was the reason it was failing. Then I tried to
figure out which HWND to give it and figured the
"MAME32_CreateWindow" or whatever function's local hWnd
was the one to use, since that was the display window
(sorry, I don't have my source in front of me and I've
had a long day). So I moved the GAMEX open/close calls
around a bit, but no success. I think I did finally get the
thing to run but starting a game would just hang it.

I honestly haven't ever sat down and really looked at
the source properly, I just wanted to recompile it so
I could add in the Tempest driver. But I am interested
in playing around with it some more, since MAMECE (although
very good) is too slow on my E-125, and MAMEBoy so nice
and fast.

Cliff