Problem with Axim x51v / Windows Mobile 5 (screen resolution)

[schnitz]

Hi!

I got a problem with my x51v.
I tried to switch screen resolution to real VGA.
So I read the tutorial of this forum, and decided to use ozVGA
I follow the instructions (copy files to windows root, copy .exe to a directory), start the program, tip "Apply and Soft reset".
The soft reset happens, but the resolution is the same as before...

OK, I try SE_VGA. SE_VGA installation works fine, no errors. But there are no installed files anywhere...
So I can't even start the interface to try whether it would work...

No problem, there is still the possibility of registry editing.
I changed the two necessary entries to 96, did a soft reset, and nothing happened.
I tried quite often, with axim inside the cradle, outside the cradle, different ways of editing, using some other programs before soft resetting... Finally there appeared the new resolution at logon screen. Eh, not completely. The resolution was changed to real VGA. But the buttons for logon were scaled incorrect. Width seemed to fit, height was to tall... A tip on a button caused axim to crash. So the hard reset was necessary.

After this I tried _really_ a lot of things, but the axim doesn't seem to accept my changes, and the above mentioned programs don't work either.
Finally I got real VGA, but I did _nothing_ different than before, just editing the registry.

So my problems/questions:
Does anybody know, how to use one of the above mentioned programs with WM 5 correctly?
Why do the registry changes work sporadic, and how to solve?
How can I get VGA fitting icons for the system? Now, most of the Today-Screen Icons are missing, because the right size is not available...


Thanks for all hints in advance!!!!

[kiwiruss]

in OzVGA, when in SeVGa mode , the default for wm2003 / wm5 , open the app, and select the "ozVGA button. that should soft reset your device and bring it back up in VGA mode

[schnitz]

I did try this about 10 times, but as I wrote, that doesn't work...

I found something in a blog: the used dll's are not signed, so they can't be loaded during boot process. But you can sign them with a certificate, but this results in a big security issue...

[schnitz]

But, as I can read in your profile, you are using the same pda, aren't you?

Does it really work with yours?