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

Should I bother with this before getting WM5?

Why not? It only takes about ten minutes to set it up... I had held off until reading this thread, using ForceHiRes instead. But this convinced me to give Oz a try... Well worth the minimal effort...

[makuu]

That's really a great Post Menneisyys. As you mentionned I did try to demystify True Vga in the past but your post really is THE definitive guide.

I wanted to ask you what kind of switcher you are using to switch different VGA mode. Are you using OzVga or did you write your own scripting switch using nScriptM ( I saw that you already wrote different kind of Script with nScriptM ).

I don't use OzVga especially because I want to handle 2 differents dll for PI and using OzVGA would mean to store 3 different dll in RAM, that is one of the reason I am using scripts instead.

So if you are also using scripts I will be very interested on it.

Also do you think your guide will be valid for WM5?

Great article. I just picked up the Netfront browser since it was on sale for 20 bucks. Works great in SE_VGA mode. Can view some shockwave sites that pocket IE wouldn't even show. Also the Goamo keyboard works great in the OzVGA/SE_VGA mode.

[magnolia]

Is there nothing to be done about the system dialogs and general system font? I tried bumping the font sizes way way up in oz just to see if that made a difference, but it didn't. They're just too tiny. Nearly everything else, I can adjust to my liking, but the system stuff is killing me. Well, those and the PI problems I've been experiencing.

[prusling]

Is there nothing to be done about the system dialogs and general system font?

As a long-term Oz'er, I find the font size in the main title bar including Start and the Time frustratingly small, or perhaps I haven't read carefully enough through the excellent tutorial yet to find out how to fix this?

[Menneisyys]

That's really a great Post Menneisyys. As you mentionned I did try to demystify True Vga in the past but your post really is THE definitive guide.

I wanted to ask you what kind of switcher you are using to switch different VGA mode. Are you using OzVga or did you write your own scripting switch using nScriptM ( I saw that you already wrote different kind of Script with nScriptM ).

I don't use OzVga especially because I want to handle 2 differents dll for PI and using OzVGA would mean to store 3 different dll in RAM, that is one of the reason I am using scripts instead.

So if you are also using scripts I will be very interested on it.

Also do you think your guide will be valid for WM5?

(Sorry for answering this late; it's only now that I've noticed my article has been reposted in this forum.)

Much as, as it offers full access to both the Registry and the file system, you can do the same with nScriptm than with OzVGA I use OzVGA to switch between the two modes because it's easier to configure (you don't need to edit nScriptm files).

Your problem with PI can very easily be fixed if you relocate the PI DLL's to the File Store. Then, OzVGA won't use RAM to store the non-active DLL's.

[Menneisyys]

Is there nothing to be done about the system dialogs and general system font? ... I tried bumping the font sizes way way up in oz just to see if that made a difference, but it didn't. They're just too tiny. Nearly everything else, I can adjust to my liking, but the system stuff is killing me.

By dialogs, do you mean system popups/ tooltips (like the battery warning, the Connectivity popup), or self-standing (also, user-creatable) dialog windows? The font size of the latter can be made bigger; the former not.

Unfortunately, there're a lot of fonts that just can't be made bigger - Start Menu fonts, file dialog fonts (the fonts used by the system in the Programs/Settings dialogs to display program names), MSN Messenger etc.

Unfortunately, this all also seem to apply to WM5 too (see my WM5 font usage comments in the thread).

[Menneisyys]

Please note that I've also posted Spb Pocket Plus 3.0, iLauncher and and cLaunch settings storage-related information in my review of Today plug-in launcher/meter utilities at, for example, http://www.aximsite.com/boards/showthread.php?p=837330 , http://www.pocketpcthoughts.com/foru...c.php?p=366634 , http://www.ipaqhq.com/forums/showthread.php?p=113155 , http://discussion.brighthand.com/sho...hreadid=120439 or http://www.firstloox.org//forums/showthread.php?p=40624 .

It's really worth checking out, especially for Spb Pocket Plus 3.0 users, because OzVGA's built-in support for Spb Pocket Plus 3.0 is outdated and not working with version 3.0. The discussion is also worth checking out for people that don't actually use these plug-ins but want to have more information on how/where other applications store the settings that should be kept separate in native and standard/SE VGA modes.

[makuu]

(Sorry for answering this late; it's only now that I've noticed my article has been reposted in this forum.)

Much as, as it offers full access to both the Registry and the file system, you can do the same with nScriptm than with OzVGA I use OzVGA to switch between the two modes because it's easier to configure (you don't need to edit nScriptm files).

Your problem with PI can very easily be fixed if you relocate the PI DLL's to the File Store. Then, OzVGA won't use RAM to store the non-active DLL's.

I was just wondering if you were using ozVGA or not. The problem of having dll in BIS and use ozVGA to handle it is: that ozVGA keeps saving before every switch and then will keeps writing in BIS. I don't like this as I don't want to stress my BIS with the writing limitation. My scripts are not writing in BIS but only reading in BIS and writing in RAM. Also my scripts are using a .cfg file so I don't need to re-edit the scripts every time that I want to handle a new application (I only add a new line to my .cfg file).

Otherwise I am also handling SPB + 3 as explained
here

[phasetrip]

thanx a lot!!! ozVGA is the best!!!

Is anyone using this with Windows Mobile 5.0?

[rilot]

Is anyone using this with Windows Mobile 5.0?

Nope, because it doesn't work.

[Menneisyys]

Nope, because it doesn't work.

Did anyone come up with a real VGA solution for WM5 so far?

(Based on the article, it can't be that complicated. That is, if, for example, only the affected DLL names have been changed, they can be extracted very easily from, say, the x51v WM5 ROM upgrade and just renamed.)

[c00lk1d]

Renaming won't do, you need to update the resource files themselfs

[Menneisyys]

Renaming won't do, you need to update the resource files themselfs

That is, you must resize icons/other resources, or, do we have to do something more? (I wish I had a WM5 device so that I could try...)