SP Task Manager 1.1b2 available

[Guest The PocketTV Team]

Seems to be one of these installer bugs. The shortcut is configured to point to %InstallDir%. This variable is replaced during installation by the right value. Unfortunately, it seems that it is always replaced by the default destination (ie IPSM). I will post a new version in some minutes and use another to get the installation folder. Thanks for the help.

yes, that's a know bug of the CAB installer on Smartphone :)

[Guest jacoch]

Thanks for the information about the WM_CLOSE message, but it's exactly what I do when you choose the 'Quit application' command. The Kill command is different and kill the process and should only be used when an app doesn't respond anymore. To send the WM_CLOSE message, I'm using PostMessage to avoid hunging Task Manager if an application is not responding. Then, I wait for 500ms before refreshing the application list. This delay is big enough in most cases to let the application quit successfully.

[Guest jacoch]

yes, that's a know bug of the CAB installer on Smartphone :)

Thanks for confirmation. I also have the problem with Smart Explorer, that doesn't register correctly the .zip icon in registry when installed on the SD card. New version will fix this and check that zip icon points to the valid installation folder at startup.

[Guest The PocketTV Team]

Thanks for confirmation. I also have the problem with http://smartphone.modaco.com/viewtopic.php?t=55367>Smart Explorer, that doesn't register correctly the .zip icon in registry when installed on the SD card. New version will fix this and check that zip icon points to the valid installation folder at startup.

This bug affects all registry entries specified in the CAB file that have references to %InstallDir%. Typically it affects file associations installed by the CAB. The bug was confirmed by MS.

We work around the bug by patching the registry entries the first time the application is run after a CAB installation.

There are probably other ways to work around the bug, e.g. with a post-install dll or with some post-install xml in the CAB file.

[Guest jacoch]

I also thought about the post install DLL. But it needs to be signed too. And I don't want to waste a signature for a MS bug. So I will also check registry entries at startup in next release.