You Are Here:

Community: Wiki

This page was last modified on 27 October 2008, at 13:44.

KIS000653 - Adding files to the startup list from embedded SIS packages not possible

From Forum Nokia Wiki



ID KIS000653 Creation date May 21, 2007
Platform S60 3rd Edition
S60 3rd Edition, FP1
Devices
Category Symbian C++ Subcategory Base & System, SW installer


Keywords (APIs, classes, methods, functions):

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.

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwikiE2eforumE2enokiaE2ecomE2findeE78E2ephpE2fKIJ000103E5fE2dE5fS60E5fprofileE5fsettingsE5fandE5fplayingE5fsoundsE5finE5fMIE44letsX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZKnowledgeBaseContentQ qdcZtypeQUqfntypeZKnownIssueQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqfntypeZWikiContentQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZKnowledgeBaseContentQ qfnZtypeQUqfntypeZKnownIssueQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZtypeQUqfntypeZWikiContentQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZKnowledgeBaseContentQ qrdfZtypeQUqfntypeZKnownIssueQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqfntypeZWikiContentQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ