Archived:Adding files to the startup list from embedded SIS packages not possible (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition (initial release) and FP1

---

Article

Created: User:Technical writer 1 (21 May 2007)

Last edited: hamishwillee (15 Jun 2012)

Description

Adding an executable to the startup list is described in the document "Startup List Management API Technical Specification" in the S60 3rd Edition SDK API Reference Guide.

In order to add applications to the startup list, the SIS package must meet (among others) the following requirements:

• The installation package containing the application must be trusted, that is, it must be signed with a valid certificate.
• The installation package must install the application executable to be added into the startup list.
• In case of an embedded package, the control file must be included in the parent package.

See the above document for a full list of requirements.

However, adding an executable to the startup list is possible only when the file is included directly in the parent SIS. Therefore, even if the parent SIS includes the control file, it cannot add executables from embedded SIS packages to the startup list.

Solution

The executable to be added to the startup list must be included directly in the parent SIS package. If this is not possible (for example, because of different capability requirements for embedded and parent packages), the startup component should be delivered as a separate SIS file.