Welcome to Emulationworld

Forum Index | FAQ | New User | Login | Search

Make a New PostPrevious ThreadView All ThreadsNext Thread*Show in Threaded Mode


SubjectCan I change the screen res, to use a CE device with a larger screen? (MameboyX) Reply to this message
Posted byAnonymous (208.63.202.194)
Posted on06/12/01 09:09 AM



Both mameboyx and mamece seem to run on my Z50, except for the fact that the screen is screwed up. My guess is that it is assuming a much smaller screen, and wrapping-around. Can I change the screen res to 640x480? (Then I just need to redo the key mappings and I might be there... :-) )

I posted about this a few days ago, but I have tried some things since then. First of all, I tried mameboyx, and it seems to work the same as mamece (same screen problem), but I was surprised that it worked that well, considering its not running on a Casio!

Anyway, I tried these things with Mameboyx: creating a mame.ini file with "resolution 640x480", but that didn't help. I've also tried the command-line options that work on the Windows version. Are these mamece versions hard-coded to the small screen?

Thanks for any help,
G.





SubjectRe: Can I change the screen res, to use a CE device with a larger screen? (MameboyX) new Reply to this message
Posted byMarconelly!
Posted on06/13/01 09:52 AM



Yes, resolution is hardcoded in MAMEBoy (and probably in MAMECE3 too...) I know Datrren was making a special versions for some hi-res devices but don't know where you can download them since his site is down :(




SubjectResolution.. new Reply to this message
Posted byAnonymous (208.63.202.20)
Posted on06/13/01 11:56 PM



> Yes, resolution is hardcoded in MAMEBoy (and probably in
>MAMECE3 too...) I know
> Datrren was making a special versions for some hi-res
>devices but don't know
> where you can download them since his site is down :(

Yeah, I tried to get there, but found out that the links to his site didn't work. I have done various web searches, but have not found the stuff mirrored. :-(

I take it that "hardcoded" in this case means that it's more complicated than changing a "#define MAX_XDIM 240" to "#define MAX_XDIM 640" or some such? :-)

I can appreciate that it would be a real pain to even try to make (another) special version, particularly not having a machine there to test it on. I'd try compiling something myself, if I could use the free MS compiler; however, when I compile, it seems to only produce stuff for WinCE 3.0, and my unit has a 2.11 core. Ugh. Does that sound right (that I can't use that compiler, but have to use VC++6)? I would have hoped there'd be a bit more backwards-compatibility; any chance I'm just missing an option? I took a look at the code, and I'm not sure that I really want to get into it, but hey, how hard could it be? ;-)

So close and yet so far... ;-)

G.





SubjectRe: Resolution.. new Reply to this message
Posted byAnonymous (65.34.179.88)
Posted on06/14/01 00:58 AM



> Yeah, I tried to get there, but found out that the links to his site didn't
> work. I have done various web searches, but have not found the stuff mirrored.
> :-(

The version in question was for a device called an "epod". Search around for "+epod +mame" and you may find a mirror of the file. The epods had a resolution of 640x480 iirc.

> I take it that "hardcoded" in this case means that it's more complicated than
> changing a "#define MAX_XDIM 240" to "#define MAX_XDIM 640" or some such? :-)

Not too much more complicated than that.

> compiling something myself, if I could use the free MS compiler; however, when I
> compile, it seems to only produce stuff for WinCE 3.0, and my unit has a 2.11
> core. Ugh. Does that sound right (that I can't use that compiler, but have to
> use VC++6)? I would have hoped there'd be a bit more backwards-compatibility;

I use VC++6. I don't know what it'll take to make it work with the free dev tools, but it must be possible. I'm fairly sure the Embedded Toolkit can compile for CE2.11 targets, although I don't use it myself.

Darren





SubjectRe: Resolution.. new Reply to this message
Posted byTekhmaster
Posted on06/14/01 05:24 PM




> > compile, it seems to only produce stuff for WinCE 3.0, and my unit has a 2.11
> > core. Ugh. Does that sound right (that I can't use that compiler, but have
> to
> > use VC++6)? I would have hoped there'd be a bit more backwards-compatibility;
>
> I use VC++6. I don't know what it'll take to make it work with the free dev
> tools, but it must be possible. I'm fairly sure the Embedded Toolkit can
> compile for CE2.11 targets, although I don't use it myself.
>
I think you just have to download the SDK add on for Win Ce2.11 and then install it just like the PocketPC SDK and the HPC SDK.
It will then create an option in the platform box for Palm Sized PC.

I'm speculating here but I think I did this at one time or another.



Cheers,
-Techmaster


SubjectUsing the eMbedded tools new Reply to this message
Posted byAnonymous (208.63.213.128)
Posted on06/15/01 09:15 AM



Thanks guys! I dunno why I had problems before, but I played with the compiler tools some more, and I was able to compile MameCE3 with a lot of errors. I got a lot of them out, but I'm stuck on 5 or 6 linker errors.

(I actually started compiling MameBoy, but gave up on that, and switched to MameCE3.)

I'll play with it some more, but it's having trouble with ordinary library functions such as "isgraph" and "strrchr".

All my other problems I have hacked around. :-) I hope I didn't hack too much. ;-) Maybe 30% of the errors were due to the absense of a library using the "HPC Pro" option instead of the "Palm" compile option. I don't know if this is important or not, but I bet I'll have to come back to that!

I guess the plan now is that if I get this to run, then I'll be asking where to look for the resolution-related parts to change, as I've not seen anything obvious so far.

G.





SubjectRe: Using the eMbedded tools new Reply to this message
Posted byAnonymous (208.63.203.39)
Posted on06/17/01 01:04 PM



An update: I finally managed to get Mameboy compiled. :-) Adjusting the screen was the easy part. I had a lot of trouble trying to get things to compile! Part of it were compiler settings that were off (such as the directory paths). Also, a lot of it was just me getting to understand the organization of the code, but part of it is something odd about how the compiler decides what and when to compile (I would get tons of linker errors, go back and force things to recompile in a certain order, and it would be fixed). (I prefer old-fashioned makefiles where I can explicitly tell it what to do...) Anyway, the important changes were the key mappings and the hardcoded settings in the screen initialization.

If y'all would like, I could put my changes into #ifdef's, and that way it could get into other people's distributions. (Currently, that would be Mameboy.) However, I need to play with MameCE3 more to see if I can get that to work; I don't think WinCE 2.11 likes the "gx.lib". Meanwhile, it's nice to have something running. :-)

Thanks for the help!

G.





SubjectRe: Using the eMbedded tools new Reply to this message
Posted byTekhmaster
Posted on06/18/01 10:38 AM



> An update: I finally managed to get Mameboy compiled. :-) Adjusting the screen
> was the easy part. I had a lot of trouble trying to get things to compile!
> Part of it were compiler settings that were off (such as the directory paths).
> Also, a lot of it was just me getting to understand the organization of the
> code, but part of it is something odd about how the compiler decides what and
> when to compile (I would get tons of linker errors, go back and force things to
> recompile in a certain order, and it would be fixed). (I prefer old-fashioned
> makefiles where I can explicitly tell it what to do...) Anyway, the important
> changes were the key mappings and the hardcoded settings in the screen
> initialization.
>
> If y'all would like, I could put my changes into #ifdef's, and that way it could
> get into other people's distributions. (Currently, that would be Mameboy.)
> However, I need to play with MameCE3 more to see if I can get that to work; I
> don't think WinCE 2.11 likes the "gx.lib". Meanwhile, it's nice to have
> something running. :-)
>
> Thanks for the help!
>
> G.
>

Add your name and the date as a comment above the changes you made and then email me the files you modified. When I get a chance I'll try to merge them into the MameCE3 source.

FYi, the order in which you compile is usually compiling all the projects that create the libraries, then compile the main project for the CE executable so it can use the precompiled libraries ;)


Cheers,
-Techmaster


Previous ThreadView All ThreadsNext Thread*Show in Threaded Mode