|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-F8A26275-883A-5299-9C37-9DDCC2F62108" xml:lang="en"><title>Eclipsing</title><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
13 <p>Eclipsing is a mechanism to upgrade files existing on the ROM drive, by |
|
14 installing a new version of the same on the RAM drive. The file name and path |
|
15 of the existing file and the new version must be the same. </p> |
|
16 <p>For example, the file, <filepath>a.exe</filepath> located on <filepath>z:\...\</filepath>, |
|
17 can be eclipsed by placing a latest version of <filepath>a.exe</filepath> on <filepath>C:\...\</filepath>. </p> |
|
18 <section id="GUID-DBF1C87D-7360-54B7-8658-B6659BF77F06-GENID-1-8-1-4-1-1-4-1-6-1-4-1-5-1-2-3"><title>Eclipsing rules</title> <p>The |
|
19 eclipsing of binary and data files in the ROM is strictly controlled. That |
|
20 is, device creators can eclipse only the files that are listed in the Stub |
|
21 SIS file. The eclipsing fails if there is no associated Stub SIS file present |
|
22 in ROM. </p> <p>The following are important considerations for eclipsing |
|
23 ROM files: </p> <ul> |
|
24 <li id="GUID-B854DA2E-A125-5E42-8B97-7DD9E5D30FFE"><p>Drives are |
|
25 scanned in the order <filepath>Y</filepath> to <filepath>A</filepath> and |
|
26 lastly the <filepath>Z</filepath> drive. Therefore a file in <filepath>Z</filepath> drive |
|
27 can be eclipsed by the newer version of the file placed on any drive between <filepath>Y</filepath> to <filepath>A</filepath>. </p> </li> |
|
28 <li id="GUID-4ECA6004-CE36-5EC7-A523-03EC3B9FC171"><p>The upgrading package |
|
29 must have the same package UID and non-localized vendor name as the package |
|
30 that installed the original file. </p> </li> |
|
31 <li id="GUID-60050205-50D1-5331-93ED-26E39D0D9678"><p>The file in ROM can |
|
32 be eclipsed only once. </p> </li> |
|
33 <li id="GUID-DA8251A1-D148-580A-A28F-B0A7388C4870"><p>The installation is |
|
34 blocked if a data file with the same name as the file to be eclipsed exists |
|
35 in the file system. The device creators can configure the installation policy |
|
36 to enable the Symbian device user to remove the obstructing files and continue |
|
37 with the installation. </p> </li> |
|
38 <li id="GUID-40325AC4-85B8-5EF3-9E70-21AF6DF35A52"><p>Eclipsing of <filepath>EXEs</filepath>, <filepath>DLLs</filepath> and |
|
39 data files either by installation or by inserting the media card into the |
|
40 Symbian device returns an error. This aborts the installation or renders the |
|
41 media card application unusable until the conflict is resolved. This restriction |
|
42 is not applicable if the file being eclipsed is an orphaned file.</p> </li> |
|
43 </ul> </section> |
|
44 </conbody><related-links> |
|
45 <link href="GUID-9DCD2076-0F73-5BB7-85BF-580567E0AB53.dita"><linktext>Package Upgrades</linktext> |
|
46 </link> |
|
47 <link href="GUID-7FD72D9F-D65E-5248-A296-F2196F1DF5CF.dita"><linktext>Upgrade Types</linktext> |
|
48 </link> |
|
49 |
|
50 </related-links></concept> |