diff -r 51a74ef9ed63 -r ae94777fff8f Symbian3/SDK/Source/GUID-F8A26275-883A-5299-9C37-9DDCC2F62108.dita --- a/Symbian3/SDK/Source/GUID-F8A26275-883A-5299-9C37-9DDCC2F62108.dita Wed Mar 31 11:11:55 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-F8A26275-883A-5299-9C37-9DDCC2F62108.dita Fri Jun 11 12:39:03 2010 +0100 @@ -1,50 +1,50 @@ - - - - - -Eclipsing -

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.

-

For example, the file, a.exe located on z:\...\, -can be eclipsed by placing a latest version of a.exe on C:\...\.

-
Eclipsing rules

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.

The following are important considerations for eclipsing -ROM files:

    -

  • Drives are -scanned in the order Y to A and -lastly the Z drive. Therefore a file in Z drive -can be eclipsed by the newer version of the file placed on any drive between Y to A.

    • -

  • The upgrading package -must have the same package UID and non-localized vendor name as the package -that installed the original file.

    • -

  • The file in ROM can -be eclipsed only once.

    • -

  • 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.

    • -

  • Eclipsing of EXEs, DLLs 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.

    • -
- -Package Upgrades - -Upgrade Types - - + + + + + +Eclipsing +

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.

+

For example, the file, a.exe located on z:\...\, +can be eclipsed by placing a latest version of a.exe on C:\...\.

+
Eclipsing rules

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.

The following are important considerations for eclipsing +ROM files:

    +

  • Drives are +scanned in the order Y to A and +lastly the Z drive. Therefore a file in Z drive +can be eclipsed by the newer version of the file placed on any drive between Y to A.

    • +

  • The upgrading package +must have the same package UID and non-localized vendor name as the package +that installed the original file.

    • +

  • The file in ROM can +be eclipsed only once.

    • +

  • 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.

    • +

  • Eclipsing of EXEs, DLLs 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.

    • +
+ +Package Upgrades + +Upgrade Types + + \ No newline at end of file