"Could not activate this XO" error

[Bert Freudenberg]

The auto update boot script supports both nand1234.img and  
os123456.img naming schemes, both fit into 8.3 FAT.

Maybe we should use one for dev builds and the other for stable builds.

>     Renaming the installation file does not change the version  
> number that
>     is actually stored in the NAND FLASH as a result of the  
> installation.

I thought that was obvious - sorry for not mentioning it, and thanks  
for spelling it out.

- Bert -

On Jul 23, 2007, at 5:57 , Mitch Bradley wrote:

> Kim Quirk wrote:
>> Thanks Mitch! I didn't know that.
>>
>> Do you think that is the best way to do the downgrade? I already  
>> changed the Autoreinstallation page to the notes I above. The  
>> possible problem at the end of the downgrade didn't sound good;  
>> and we are going to start using stable release numbers >1000, so  
>> if you do change it back, please keep that in mind.
> I think the rename method is good.  It is simple, effective, and safe.
>
> As Dan points out, you have to both rename the file to e.g.  
> nand6000.img and change the corresponding number in olpc.fth .
>
> Be sure to respect the 8.3 limitation on the filename - nand60000  
> will fail on a FAT filesystem.
>
>
>>
>> Thanks,
>> Kim
>>
>> On 7/22/07, *Mitch Bradley* <wmb at laptop.org  
>> <mailto:wmb at laptop.org>> wrote:
>>
>>     Kim Quirk wrote:
>>     > I don't recommend that your rename your nand to a higher build
>>     number
>>     > than it actually is just to avoid a downgrade. You may never  
>> be able
>>     > to catch up (or catch back down to the proper version).
>>     >
>>
>>     Renaming the installation file does not change the version  
>> number that
>>     is actually stored in the NAND FLASH as a result of the  
>> installation.
>>
>>
>