@Rogue
> I don't get this. What is so hard about entering
>
> fdcboot; bootm
>
> or
>
> diskboot 50000 1:0; bootm
Given the (IMHO) "crude" state of AmigaOne hardware and that this is the first widespread OS4 release, there's absolutely nothing wrong with it. But as a previous poster suggested, when seen from the POV of a current AmigaOS 3.x user, there is something distinctly "alien" about it. In order to move forward to modern hardware, it is unfortunate that we must simultaneously move backward to these kinds of interfaces. Over the long-term, I hope Hyperion and Eyetech will work to address issues like this.
Here are a few replacement procedures off the top of my head. As I don't currently own an AmigaOne and am not familiar with the subtleties of loading new firmware, take these for what they're worth:
1) User presses a key combination during the boot sequence, which makes the AmigaOne respond with a "Load new firmware?" prompt. User presses "Y", which causes the AmigaOne to scan all connected devices (a bit like checking RDB's) for recognizable firmware files. The AmigaOne presents a list of such files, and the user can choose to install one or cancel.
2) Same as above, except "Load new firmware" is an option on an early-boot screen (ie. hold both mouse buttons during boot).
3) Assuming the firmware is loaded (or can be loaded?) into RAM during bootup, like current Kickstarts, the user flashes the firmware using an OS4 Reaction GUI utility, just like flashing a modem or CD/DVD drive, and reboots to use the update. Obviously, this assumes OS4 is already installed or easily loaded off CD.
Todd
