|
> Ok, since you prefers seeing things by yourself, upload this > > ftp://ftp2.v3x.net/vx/mame/mamece-mod.zip ( 500 Kb ) > > This is the modified version of mamece 9.4 using the SHFullscreen source. > > You will be surprise than an zero knowledge technical did remove the annoying > task bar, and increased mamece of 3 fps by using the shfullscreen.
I don't believe that you increased the performance of MameCE by using SHFullscreen - that to me would make no sense. You are saying your SHFullscreen call turns the video memory into "special fast" memory? It alters the memory map to allow more speed?
I will reiterate, I have no task bar and no SHFullscreen call. Maybe a PocketPC 2002 thing? (I haven't got that to test on.)
> Try it, the binary is provided source modified, so I don't have anything than > a ipaq 3630, perhaps you should try this version on your prefered PDA, give me > comments on this (provide ARM binary only) > > If you have doubt about my zero technical knowledge, i suggest to look on my > site http://www.realtech-vr.com and http://www.v3x.net and also see how a zero > technical can do since 1995. Ah, I'm now working on this game btw : > http://www.tombraider.com (I've done the Ipaq version - If you want, my email is > stephane@core-design.com
Well if you know what you are talking about why are you saying stuff which isn't true?! "it's probably reading from video memory which is slowing iPaq 38xx": not true - it's the rotation blit. "DLLs are portable across all platforms": not true. "It would be straightforward to put drivers in different DLLs": not true. "SHFullscreen is the only way to get fullscreen": not true. I've got fullscreen without it - I mean this is just basic logic surely?
0/4 seems a bit bad to me. The only way we can combine what both of us are seeing is maybe Pocket PC 2000 doesn't need a SHFullscreen command and Pocket PC 2002 does, but that would just be speculation. Don't jump to conclusions!
> Best > > PS: Since i've got the source now, I'm now much more understanding the problems, > thanks you for your info for the Ipaq 3800 however...
No problem.
|