Well, don't be so hasty. Knowing the .upgrade file format might still prove somewhat useful. Depending on what it will/won't do. If you can choose to do just a flash write in an upgrade file, then it would be a cool way of distributing logos and custom kernels. I know that it's possible to do just a partition replacement (because Mike once made the accident of distributing an upgrade that way), but I don't know if it works the other way around.

If one could know the bare minimum of what bytes are necessary to surround a piece of flash data and stuff into an upgrade file, then I would begin work on a logo editor. I'm kind of keen on this idea. It would allow you to both import images as well as pixel edit them right on the screen. Its output would be a .upgrade file that wrote the logo to memory location A000 in the flash. It would even launch the upgrade file for you if you wanted.

It'd only be for Windows, though, since that's all I know how to code for...

Honestly, I could do it right now and I probably will anyway, using the download.c source, but it'd be so cool to have the output be a .upgrade file if that's possible. (I'd still output a raw binary file so linux folks could copy it over and use download.c to send it.)

___________
Tony Fabris