VGA demystified – the definitive guide to OzVGA, SE_VGA and everything VGA-related - Page 3

Menneisyys · 10-10-05, 10:54 AM

Originally Posted by rilot

Nope, because it doesn't work.

BTW, I've been reading contradicting information on whether WM5 VGA devices can be used in real VGA. Does anyone know whether they can be?

10-10-05, 02:39 PM

Originally Posted by Menneisyys

BTW, I've been reading contradicting information on whether WM5 VGA devices can be used in real VGA. Does anyone know whether they can be?

The main problem is that there is not any free QVGA ROM upgrade available from where you could extract the needed files.

In another hand I can tell you that the double pixeling can be disable using the usual MUI technique.

rilot · 10-10-05, 02:40 PM

I have the 96dpi DLL files from a QVGA installation of WM5. I can force the screen in to 96dpi mode but it has the effect of removing all the icons, much as it would on WM2003SE without the correct DLLs installed.

No matter where I put the 96dpi DLLs or what I set in my "path" variable, I cannot get the OS to call them at boot time.

All the registry settings are the same as WM2003SE but it would seem that the OS doesn't choose which dpi of DLLs to load based on the value "LogicalPixelsX" and "LogicalPixelsY" any more. There must be another setting somewhere.

10-10-05, 02:46 PM

Originally Posted by rilot

I have the 96dpi DLL files from a QVGA installation of WM5. I can force the screen in to 96dpi mode but it has the effect of removing all the icons, much as it would on WM2003SE without the correct DLLs installed.

No matter where I put the 96dpi DLLs or what I set in my "path" variable, I cannot get the OS to call them at boot time.

All the registry settings are the same as WM2003SE but it would seem that the OS doesn't choose which dpi of DLLs to load based on the value "LogicalPixelsX" and "LogicalPixelsY" any more. There must be another setting somewhere.

If you want I can give you the contact information in Private of the SE_VGA author. I'm sure that he will be glad to prepare a new version for WM5 using those files.

10-10-05, 02:48 PM

Originally Posted by rilot

I have the 96dpi DLL files from a QVGA installation of WM5. I can force the screen in to 96dpi mode but it has the effect of removing all the icons, much as it would on WM2003SE without the correct DLLs installed.

No matter where I put the 96dpi DLLs or what I set in my "path" variable, I cannot get the OS to call them at boot time.

All the registry settings are the same as WM2003SE but it would seem that the OS doesn't choose which dpi of DLLs to load based on the value "LogicalPixelsX" and "LogicalPixelsY" any more. There must be another setting somewhere.

What machine are you using in your tests?

rilot · 10-10-05, 02:51 PM

i-Mate JASJAR (HTC Universal) which is a WM5 VGA device. The DLLs are from an HTC BlueAngel WM5 installation.

10-10-05, 02:52 PM

Originally Posted by rilot

i-Mate JASJAR (HTC Universal) which is a WM5 VGA device. The DLLs are from an HTC BlueAngel WM5 installation.

Well those dlls are buggy.
I wont try to do anything with them.

rilot · 10-10-05, 02:54 PM

Are they? How do you know?

10-10-05, 03:01 PM

Originally Posted by rilot

Are they? How do you know?

I have many customers with teh HTC Blue Angel and they have not been able to use my programs while the rest of WM5 owners can use them.

rilot · 10-10-05, 03:03 PM

OK. Probably because the BA and Hima installations were cobbled together from various pre-release editions of WM5.

I have asked someone with a HTC Wizard WM5 genuine device to rip and mail me the DLLs. We shall see where we get with them.

10-10-05, 03:03 PM

In another hand. I does not seem to me a good idea to prepare an application with dlls from a beta version OS. I, at least, have enough with the Official version bugs to add more bugs with Beta DLLs. ;)

10-10-05, 03:05 PM

Originally Posted by rilot

OK. Probably because the BA and Hima installations were cobbled together from various pre-release editions of WM5.

I have asked someone with a HTC Wizard WM5 genuine device to rip and mail me the DLLs. We shall see where we get with them.

That sounds much better.

10-10-05, 03:19 PM

Originally Posted by Menneisyys

BTW, I've been reading contradicting information on whether WM5 VGA devices can be used in real VGA. Does anyone know whether they can be?

I did get my Today screen into true VGA after making the registry changes, but the unit pretty much was dead in the water after installing ozVGA. I wasn't very scientific about the whole thing, but I'll try to be next time.

Menneisyys · 10-10-05, 03:24 PM

Originally Posted by ctitanic

In another hand. I does not seem to me a good idea to prepare an application with dlls from a beta version OS. I, at least, have enough with the Official version bugs to add more bugs with Beta DLLs. ;)

Well, the affected DLL's are resource DLL's only - that is, there's no executable code in there. That is, even beta ones will do.

10-10-05, 05:32 PM

This is a hell of a time and a hell of a thing to be testing with Sprite Backup not working with WM5. I don't have the stamina to keep screwing up my Axim and then having to reinstall apps and such without a good backup program that works with the new OS. It is going to be a long few months until all this crap is straightened out. I'm sure I'll look back and laugh, but not right now. OK... maybe a little.