13 <p>Eclipsing is a mechanism to upgrade files existing on the ROM drive, by |
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 |
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> |
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>, |
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> |
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 |
18 <section id="GUID-DBF1C87D-7360-54B7-8658-B6659BF77F06-GENID-1-10-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 |
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> |