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