UPDATE (06/12/2008):
1. the new version has turned out to be supporting MS Smartphone (SP for short). As of now, the EXE installer isn’t guaranteed to deploy the right version on the phone, though. As the developer explained, “The installer works correctly depending on the version of Activesync and the number of devices. Since we are supporting all models from PPC through WM6 in one setup program, this can lead to issues with different versions of Activesync. Each CAB is versioned for the correct system and Activesync is supposed to select based on this data. This is a known issue with Activesync and has been open for a while, which is why we provide and prefer customers to use the cab files if they know how. I’ve been fighting with MS for months on this problem.” As the Smartphone CAB file isn’t available for separate download, you’ll need to get the
PCommodore64Vic20Setup2.exe file, execute it and, then, go to
\Documents and Settings\windows username\Local Settings\Temp\RarSFX0\ to localize
WMSPCab.cab. Use this one. Hopefully the developers will release the CAB file as a separate download – as they’ve done with the PPC versions.
2. Using the SP version is pretty much the same as the PPC version. However, upon each start, you’ll need to supply a button to invoke the menu - that is, highlight the user interface elements in turn, using the up/left and down/right D-pad arrows; note that, when starting from the default upper left corner, you can go back to the lower right by pressing up/left. That is, you don’t need to scroll through all the buttons and icons, which would be pretty time-consuming:
I recommend using the Back hardware button for this feature because if you assign for example the camera button, the Camera app will always be invoked, along with the menu. The reason for the latter misfunction is that button disabling is limited to those supported under GAPI for each hardware device. If the manufacturer did not allow this button to be blocked during GAPI use, it is left active. You can’t assign a numeric button either, as they’re used for alphanumeric input (that is, you don’t need to use the on-screen, very slow-to-scroll keyboard for character input).
Incidentally, the two screenshots above show the interface on a 176*220 traditional MS Smartphone. As can be seen, no text is readable. It’s a bit better in Landscape, though. No such problems with QVGA Smartphones (and Pocket PC’s). Example screenshots:
(Portrait)
(Landscape)
Another screenshot without the GUI in Landscape. This is the maximum resolution you can get on a 176*220:
It’s just sufficient to run games:
While the same in Portrait:
3. legal owners of the 2.xx version are entitled to a massive, 72% (!) rebate by using the form
HERE. This is quite a bargain, taking into account the vastly improved emulation core, the multiplayer support and the heavily reduced CPU load (meaning vastly improved battery life on most CPU platforms). Incidentally, on a 195 MHz 176*220 HTC s310 Smartphone, the CPU usage is about 65% when idling.
Note that if you purchase a license, you'll also be able to use it on the desktop version of the emulator. Yes, the EXE installer also installs a desktop version (available under Start / Programs / ClickGamer Technologies / WinCommodore64)
4. The developers plan to port the emulator to both Symbian S60 and the iPhone.