I’ve dedicated several articles (for example, THIS) to tracking Registry changes. In addition to the WinDiff-based method I’ve explained, there are also other solutions doing the same; most importantly, SKTracker and the pretty new, free, highly recommended CeRegEditor (see the Registry Editor Bible for more info on the latter).
Now, however, an, in some cases, MUCH better, dynamic tool, RegLogger has been released for both current Windows Mobile platforms: Pocket PC (Windows Mobile Classic / Pro) and Smartphone (Windows Mobile Standard – man, I DO hate these name changes and the subsequent need for ever entering both names...).
It allows for dynamically tracking what changes there have been in the Registry dynamically (in runtime). Just an example of creating a subkey called “menneisyys da king” (see the, in the first screenshot, highlighted “Create” action) and, later, setting a String value “yeah” (see ID 144 in the same screenshot):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(WM6 VGA Pocket PC screenshot. Note that the value I’ve given to the new string can’t be seen; neither can be seen the full registry tree I’ve attached the new subkey to. These problems might be fixed in the subsequent versions.)
(WM6 QVGA Smartphone screenshot)
(WM2003 PPC screenshot)
(WM5 VGA PPC screenshot showing Resco Registry Editor’s reading out all the Registry values)
Availability, compatibility
Get the PPC / SP version HERE. It’s compatible with all PPC and Smartphone platforms starting with WM2003. Just unZIP the file, transfer its contents to your handheld and run REGLOGGER.exe. To start logging, enable Log / Capture. Note that, on some Smartphones (NOT on my CID / app unlocked WM6 HTC Vox / s710!) you might also need to import TestCert_Privileged.cer, should you encounter authentication problems.
Tips
Because of the HUGE amount of Registry access going on all the time, there are two text input fields and some checkboxes in Log / Settings you will need to make extensive use of.
First, if you’re absolutely sure the app you’re running and would like to track its Registry changes doesn’t have any active code in \Windows, which would result in the Registry change you’d like to find out, you can just enter \Windows (feel free to just leave out the leading backslash) to filter out most of the, in this case, unnecessary traffic in the “Exclude processes with this sub-str” as can be seen in the following:
Note that several programs put an executable file under \Windows; for example, Pocket Controller 6’s (the best Windows Mobile device controller app with a brand new remote Registry editor) PCCommLoader.exe under \Windows\StartUp. In these cases, you won’t want to filter out \Windows but, instead, enter PCCommLoader (or a substring of it) to the other text input field, “Include only from processes with sub-str”, as can be seen in the following screenshot:
You can also set which operation you’d like to track; by default, everything is logged, even reading (querying). You’ll most probably want to limit the number of the enabled checkboxes at the bottom.
Finally, you may also save the tracking results to a file using File / Save As. Note that, currently (as of version 1.0), it doesn’t contain the missing for example full Registry tree information either.
That's a really cool program I will use, will enable me to track all those nasty demo version registry entries I have.
BTW do you know of an application to edit .rgu or .hv files, so the kitchen-registry files. Of course you can use the editor but I haven't found any app that shows it in hive-view.
Is there any application for us track our Phone
for family, so we know where the kids are
its for a friend of mine
If someone knows if we can do it on PPC phone
would like to know
Will SmartPhone Tracker do the job
But i think thats just when our phone gets stolen
might jam the phone
Thxs
Related
SKTools is, in my opinion, by far the best all-in-one system tool for the Pocket PC. You will definitely want to give it a try - it's an indispensable tool.
I’ve often posted on earlier versions of SKTools; see for example this – make sure you follow the links in the post to earlier reviews!
The new, 3.1.1 version boasts the following new capabilities (excerpt from the blurb):
"Registry Explorer" (registry viewer/editor/new/export/import/backup) option added.
"Buttons" section of TuneUP! option improved. Added standard macros.
Added some new devices to benchmark database
Improved "Notification queue" option work for WM5 devices
added Dutch language UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As can be seen, it’s the registry editor feature that is the most important new feature. Therefore, I’ve given it a very thorough test. Please also read my Registry Editor Bible for a more thorough elaboration on the meanings of the test results below; in here, I won’t explain what they stand for.
The registry editor is NOT using the usual tree control other (except for Total Commander 2.0/2.5’s file system-like user interface) registry editors utilize and, therefore, it’s requires a bit more effort to go up/down a registry tree. For example, when you want to step into a subkey, you need to highlight it, bring up either the context and / or the Action menu and select Open. Going back to the parent key is doing the same on the .. symbol. You can also use the six predefined keys in the Goto menu to quickly switch to the six most important positions in the registry tree. Finally, you can double-click a subkey for faster navigation - then, you won't need to bring up the menu and select Open.
Importing RegEd 5-format files works (Unicode only – as with Resco Registry Editor, the best registry editor, it doesn’t import non-Unicode files and doesn’t display an error message either).
Exporting also works; it exports to (Unicode) RegEd 5 files. Exporting is considerably faster than with Resco – this may be advantageous when you frequently export the entire registry.
It also has registry searching capabilities. The search GUI has fine-tuning capabilities: you can ask for case-sensitive, data-only etc. searching) in Registry Search / Tools / Settings as can be seen in here and here. The results are, by default, found in both key / value names and data. Unfortunately, it doesn’t search Unicode binary data (for example, mail server names in [HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Inbox\LdapInfo]) – in this respect, Resco is definitely superior. However, the S-K folks have told me they’ll implement the latter.
As far as editing capabilities are concerned, it’s able to correctly (as opposed to, for example, PHM, Total Commander and Merlin) edit multiline strings. Upon editing DWORD values, you can only use decimal numbers (no hex/ binary / octal input possible). The binary editor isn’t very sophisticated either, compared to Resco, Vidya or Merlin – but at least works.
All in all, as far as strictly the new registry editor / export / import / backup / restore functionality of SKTools is concerned, it’s certainly welcome, usable, reliable (!) and makes the entire suite more than a must for all serious Pocket PC users. However, don’t throw your Resco Registry Editor away – for some tasks, it’s still unrivalled and is (still) considerably better than the regededitor functionality of SKTools.
However, don't think SKTools is bad - it is definitely the Number One all-in-one system tool around. It's just that its registry editor (and backup / restore module - please see the Backup Bible) isn't so strong as those of some other commercial applications. However, don't forget there are a lot of other, top-notch modules in the entire suite, which do make SKTools, price/performnce-wise, the best all-in-one utility suite.
Many older computer users know what adventure games the excellent folks Magnetic Scrolls have produced some really good adventure games. (See THIS (if the link doesn’t work, THIS) for more info). If you want to play these really excellent games on your Windows Mobile (WM for short) device, I have some very good news for you: yes, they’re all playable – and not only under CPU-hungry and not-the-best-suited-for-the-Windows-Mobile-UI emulators, but also real interpreters.
You may have already heard of “Magnetic”, THE Magnetic Scrolls games interpreter. It, fortunately, also has a Windows Mobile port.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(another VGA shot; a QVGA one)
There are three main revisions of Magnetic: 1, 2 and 2.2. Of course, the higher, the better (see the three charts comparing them HERE for more info on the version differences if interested). For WM, fortunately, a port of the latest, 2.2 version is available; as with the desktop Windows. Note that there is another version called for WindowsCE-based Handheld Pro and 2000 devices: chiark’s MagnetiCE; you will NOT want to use it on your WM device because it uses H/PC menus even under Windows Mobile.
Installing the interpreter
Download it from here (linked from this IF-Archive page) (alternative, direct download here). Unzip MagneticWinCE.exe and transfer it anywhere on your handheld.
Note that the interpreter is only compatible with WM2003SE and newer operating systems. It doesn't seem to run under WM2003 (tested on my iPAQ 2210), let alone PPC2k2. I had no problems running it on my (several) WM2003SE+ devices; worked flawlessly even under WM6. It makes use of built-in keyboards and landscape modes without problems. It also supports command history (up/down cursor keys), which is very useful particularly if you want to, say, repeat “wait” many times.
Getting and installing the games
Fortunately, all compatible games are available online and you don’t need to do any conversion. Go HERE and go to the bottom, to the bottom-most Game Files chart. Download the “Story files” of all the games you’d like to enjoy. Unzip it to anywhere on your storage card. Make sure you only put it in a direct descendant (subdirectory) of the root of the card and not the second, third etc. one; this, unfortunately, also applies to the \My Documents directory on your card) or in the main storage, under a directory in \My Documents.
If you don't like this restriction because of the standard file selection dialog, you can fix the problem by getting Mad Programmer’s File Dialog Changer , the current WM5/WM6-compliant version of which is 1.66. Get it HERE. You'll also need GSGetfile.
I’ve often elaborated on the installation / usage of this really useful utility (see for example THIS). Just a quick recap (with WM6 screenshots): after transferring ARM\filedlgchg.cpl from filedlgchg.zip and ARMRel\gsgetfile.dll from gsgetfile-i.zip to \Windows on your mobile device, go to the new Settings / System / File Dialog Changer applet and just check in “Exchange Standard File Dialog”. This will make it possible to peek in anywhere in the file system as can be seen in here.
In addition to the (text-only) story, you may also want to download the image repository (see the “Graphics file” column for all the games you’d like to run). Title graphics and title music files are also downloadable (if present); you will need to separately watch / listen to them from a multimedia player and an image viewer. Hint files, on the other hand, are also handled by the interpreter engine; therefore, you will want to download them too if you do need hints.
Then, just start MagneticWinCE.exe, select File / Open and select the game to play.
The menu of the interpreter is pretty straightforward; in addition to the standard Open / Exit functionality, in Edit / Verb, you can select five predefined verbs to speed up input words. In Display, you can set the size of the images displayed (and whether they’re displayed at all).
The Palm OS Kronos emulator
If you have a Palm OS device, you may have heard of Kronos, an emulator for Magnetic Scrolls, Infocom-style ZMachine, and Scott Adams style adventure games. It’s very advanced: as opposed to the original Windows (and Windows Mobile) version, it supports automaps and popwords.
Unfortunately, it (as of the latest, 1.4.7 version) crashes the current version (1.0.025) of StyleTap, the Palm OS emulator for WM, in the 66% screen mode and, as can be seen in here, in 100% mode, on VGA devices, it uses a low-resolution display. However, if you can live with this (because don’t want to enjoy the images), running Kronos under StyleTap may be a good alternative.
Note that as far as QVGA (low-resolution) Windows Mobile devices are concerned, images are almost invisible on them; example screenshots here and here. However, if you don’t need images at all or can play in 66% mode on QVGA devices, the images are, then, correctly displayed (1 2).
Note that Kronos offers autoload/save features. This is missing from the WM version. The latter, however, supports saving and loading the game state (via the save/load commands) any time.
If you have a QVGA Smartphone like the HTC Vox / s710, you know well enough that most existing games and other graphics-based Smartphone apps (Windows Mobile 6 Standard) out there only use a postage-stamp sized screen area. An example of this is PDAMill’s Flux Challenge, which, being designed for the traditional low-res (176*220) Smartphone resolution, only uses part of the available QVGA screen estate:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There were no widely known solutions for the problem. Some developers announced support for QVGA devices (for example, that of Cell Doom – see announcement HERE), but the most (including PDAMill) didn’t.
Fortunately, an excellent White Russian coder has come up with a generic solution, which not only makes it possible to run MANY (but not all!) games at full screen, but, in cases, also lets for using real (!) QVGA resolution with some titles (for example, emulators).
Downloading, installing
Go to this MoDaCo thread and download the ZIP file attached to the first post. You’ll need to register as a forum user if you aren’t able to access it. If you don’t want to bother with it, I’ve also uploaded the file to my database back-end; it’s HERE.
After this, just unZIP it and start GxQvga Patcher.exe. Should you encounter an error message complaining about the lack of the .NET Framework 2, you will need to download it HERE (note that some stated it only requires 1.1. I haven’t checked whether they’re right. The latter is accessible HERE.)
Using
This patcher app runs on the desktop, NOT on the Smartphone. This means you must transfer the main EXE file of the game / emulator / app you’d like to make use of the QVGA screen to your desktop computer first. To do this, use for example Total Commander with the CE file system patch (see THIS for an explanation of installing it) or, if you don’t want to bother, just the “Explore” button of ActiveSync.
Transfer the main EXE files (but nothing else) of the apps / games you’d like to patch to the directory of where the above-mentioned, just decompressed GxQvga Patcher.exe resides.
Now, start GxQvga Patcher.exe. It will present you a dialog:
In there, click “Select exe file to patch...". Now, select the EXE file you’d like to patch:
After letting it go on, you’ll be presented a message telling you the patching was successful:
Now, all you need to do is:
Copy the patched EXE file back to your MS Smartphone, making sure you overwrite the original EXE file
Go to the QVGA subdirectory on your desktop (just under the directory where GxQvga Patcher.exe resides), and copy XG.dll to the same directory on your smartphone
Start the game / app to see whether it worked; answer Yes to the message.
If the game / app still only uses 176*220 (and not the full screen), exit it and go to the SCALE (NOT the previous QVGA!) subdirectory on your desktop, and copy XG.dll to the same directory on your smartphone and copy XG.dll to the smartphone, making sure you overwrite the previously copied QVGA XG.dll. Now, start the game on your Smartphone. Hope it’ll use the full screen. If it still doesn’t do this, then, nothing can help, I’m afraid.
Examples of the before-after cases
PocketHobbitSP2003 (as of the current, Alpha 11 version) doesn’t support QVGA devices. As can be seen in the following screenshot, without patching, it only uses a stamp-size screen area in Portrait mode on QVGA devices:
http://www.winmobiletech.com/062007C64Emus/c64EmuDefaultStamp.bmp.png
After the patch and using the QVGA DLL, it becomes much bigger and, what is even more important, makes use of the full horizontal screen reoslution – that is, 240 pixels, resulting in MUCH more readable text:
http://www.winmobiletech.com/062007C64Emus/PatchedSEQVGAP.bmp.png
Incidentally, with the SCALE DLL, it also fills in the entire screen horizontally, BUT only upscaling the original, 176*132 rendition resulting in a MUCH inferiour real resolution & readability:
http://www.winmobiletech.com/062007C64Emus/PatchedSPVersionScaleDLLQVGAPortrait.bmp.png
This is why I’ve emphasized you MUST give a try to the QVGA DLL first and only give a try to the SCALE one when the former doesn’t deliver any results.
Recommended link
This MoDaCo thread discusses the converter at length. A MUST!
It's a cooool tool, I will try it.
yes, I have been using it for half a year ago, cool thing Worms, Flux Challenge... this tool doesn't know any limitations!!
If you have a QVGA Smartphone like the HTC Vox / s710, you know well enough that most existing games and other graphics-based Smartphone apps (Windows Mobile 6 Standard) out there only use a postage-stamp sized screen area. An example of this is PDAMill’s Flux Challenge, which, being designed for the traditional low-res (176*220) Smartphone resolution, only uses part of the available QVGA screen estate:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There were no widely known solutions for the problem. Some developers announced support for QVGA devices (for example, that of Cell Doom – see announcement HERE), but the most (including PDAMill) didn’t.
Fortunately, an excellent White Russian coder has come up with a generic solution, which not only makes it possible to run MANY (but not all!) games at full screen, but, in cases, also lets for using real (!) QVGA resolution with some titles (for example, emulators).
Downloading, installing
Go to this MoDaCo thread and download the ZIP file attached to the first post. You’ll need to register as a forum user if you aren’t able to access it. If you don’t want to bother with it, I’ve also uploaded the file to my database back-end; it’s HERE.
After this, just unZIP it and start GxQvga Patcher.exe. Should you encounter an error message complaining about the lack of the .NET Framework 2, you will need to download it HERE (note that some stated it only requires 1.1. I haven’t checked whether they’re right. The latter is accessible HERE.)
Using
This patcher app runs on the desktop, NOT on the Smartphone. This means you must transfer the main EXE file of the game / emulator / app you’d like to make use of the QVGA screen to your desktop computer first. To do this, use for example Total Commander with the CE file system patch (see THIS for an explanation of installing it) or, if you don’t want to bother, just the “Explore” button of ActiveSync.
Transfer the main EXE files (but nothing else) of the apps / games you’d like to patch to the directory of where the above-mentioned, just decompressed GxQvga Patcher.exe resides.
Now, start GxQvga Patcher.exe. It will present you a dialog:
In there, click “Select exe file to patch...". Now, select the EXE file you’d like to patch:
After letting it go on, you’ll be presented a message telling you the patching was successful:
Now, all you need to do is:
Copy the patched EXE file back to your MS Smartphone, making sure you overwrite the original EXE file
Go to the QVGA subdirectory on your desktop (just under the directory where GxQvga Patcher.exe resides), and copy XG.dll to the same directory on your smartphone
Start the game / app to see whether it worked; answer Yes to the message.
If the game / app still only uses 176*220 (and not the full screen), exit it and go to the SCALE (NOT the previous QVGA!) subdirectory on your desktop, and copy XG.dll to the same directory on your smartphone and copy XG.dll to the smartphone, making sure you overwrite the previously copied QVGA XG.dll. Now, start the game on your Smartphone. Hope it’ll use the full screen. If it still doesn’t do this, then, nothing can help, I’m afraid.
Examples of the before-after cases
PocketHobbitSP2003 (as of the current, Alpha 11 version) doesn’t support QVGA devices. As can be seen in the following screenshot, without patching, it only uses a stamp-size screen area in Portrait mode on QVGA devices:
http://www.winmobiletech.com/062007C64Emus/c64EmuDefaultStamp.bmp.png
After the patch and using the QVGA DLL, it becomes much bigger and, what is even more important, makes use of the full horizontal screen reoslution – that is, 240 pixels, resulting in MUCH more readable text:
http://www.winmobiletech.com/062007C64Emus/PatchedSEQVGAP.bmp.png
Incidentally, with the SCALE DLL, it also fills in the entire screen horizontally, BUT only upscaling the original, 176*132 rendition resulting in a MUCH inferiour real resolution & readability:
http://www.winmobiletech.com/062007C64Emus/PatchedSPVersionScaleDLLQVGAPortrait.bmp.png
This is why I’ve emphasized you MUST give a try to the QVGA DLL first and only give a try to the SCALE one when the former doesn’t deliver any results.
Recommended link
This MoDaCo thread discusses the converter at length. A MUST!
If you have a QVGA Smartphone like the HTC Vox / s710, you know well enough that most existing games and other graphics-based Smartphone apps (Windows Mobile 6 Standard) out there only use a postage-stamp sized screen area. An example of this is PDAMill’s Flux Challenge, which, being designed for the traditional low-res (176*220) Smartphone resolution, only uses part of the available QVGA screen estate:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There were no widely known solutions for the problem. Some developers announced support for QVGA devices (for example, that of Cell Doom – see announcement HERE), but the most (including PDAMill) didn’t.
Fortunately, an excellent White Russian coder has come up with a generic solution, which not only makes it possible to run MANY (but not all!) games at full screen, but, in cases, also lets for using real (!) QVGA resolution with some titles (for example, emulators).
Downloading, installing
Go to this MoDaCo thread and download the ZIP file attached to the first post. You’ll need to register as a forum user if you aren’t able to access it. If you don’t want to bother with it, I’ve also uploaded the file to my database back-end; it’s HERE.
After this, just unZIP it and start GxQvga Patcher.exe. Should you encounter an error message complaining about the lack of the .NET Framework 2, you will need to download it HERE (note that some stated it only requires 1.1. I haven’t checked whether they’re right. The latter is accessible HERE.)
Using
This patcher app runs on the desktop, NOT on the Smartphone. This means you must transfer the main EXE file of the game / emulator / app you’d like to make use of the QVGA screen to your desktop computer first. To do this, use for example Total Commander with the CE file system patch (see THIS for an explanation of installing it) or, if you don’t want to bother, just the “Explore” button of ActiveSync.
Transfer the main EXE files (but nothing else) of the apps / games you’d like to patch to the directory of where the above-mentioned, just decompressed GxQvga Patcher.exe resides.
Now, start GxQvga Patcher.exe. It will present you a dialog:
In there, click “Select exe file to patch...". Now, select the EXE file you’d like to patch:
After letting it go on, you’ll be presented a message telling you the patching was successful:
Now, all you need to do is:
Copy the patched EXE file back to your MS Smartphone, making sure you overwrite the original EXE file
Go to the QVGA subdirectory on your desktop (just under the directory where GxQvga Patcher.exe resides), and copy XG.dll to the same directory on your smartphone
Start the game / app to see whether it worked; answer Yes to the message.
If the game / app still only uses 176*220 (and not the full screen), exit it and go to the SCALE (NOT the previous QVGA!) subdirectory on your desktop, and copy XG.dll to the same directory on your smartphone and copy XG.dll to the smartphone, making sure you overwrite the previously copied QVGA XG.dll. Now, start the game on your Smartphone. Hope it’ll use the full screen. If it still doesn’t do this, then, nothing can help, I’m afraid.
Examples of the before-after cases
PocketHobbitSP2003 (as of the current, Alpha 11 version) doesn’t support QVGA devices. As can be seen in the following screenshot, without patching, it only uses a stamp-size screen area in Portrait mode on QVGA devices:
After the patch and using the QVGA DLL, it becomes much bigger and, what is even more important, makes use of the full horizontal screen reoslution – that is, 240 pixels, resulting in MUCH more readable text:
Incidentally, with the SCALE DLL, it also fills in the entire screen horizontally, BUT only upscaling the original, 176*132 rendition resulting in a MUCH inferiour real resolution & readability:
This is why I’ve emphasized you MUST give a try to the QVGA DLL first and only give a try to the SCALE one when the former doesn’t deliver any results.
Recommended link
This MoDaCo thread discusses the converter at length. A MUST!