19 eclipsing of binary and data files in the ROM is strictly controlled. That |
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 |
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 |
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 |
22 in ROM. </p> <p>The following are important considerations for eclipsing |
23 ROM files: </p> <ul> |
23 ROM files: </p> <ul> |
24 <li id="GUID-B854DA2E-A125-5E42-8B97-7DD9E5D30FFE"><p>In Symbian platform, |
24 <li id="GUID-B854DA2E-A125-5E42-8B97-7DD9E5D30FFE"><p>Drives are |
25 drives are are scanned in the order <filepath>Y</filepath> to <filepath>A</filepath> and |
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 |
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> |
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 |
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 |
29 must have the same package UID and non-localized vendor name as the package |
30 that installed the original file. </p> </li> |
30 that installed the original file. </p> </li> |