AmigaOS4 pre-release guide

[amigamad]

It's better than the updater built in to the BIOS of ASUS boards.

No its not the built in asus one is the best i have used,you dont need no messing around creating bootdisks and its easy .   :-?

[DegeRandolf]

The guide talks about using Linux or an Amiga to make the floppy update disk.  I wonder if it can be done under Windoze?

[Waccoon]

I have clear recollection of the responses to my article, where I wrote down, that the MorphOS CD starts with

boot /pci/cd boot.img

in the OpenFirmware prompt, that it's alien, and not Amiga at all. (On a side note I fear there will be no real Amigas anymore.)

The OS4 pre-release install guide seems fair enough to me, and I'm glad that the overall acceptance is better than my article's a year or more ago.

It's not hard, just fussy.  Instead of writing a tiny utility in the CDs bootblock (like early startup options) to do a variety of things, you have to do it all yourself.  Even I could hack up something in no time at all.

But then, this might all change by the time OS4 final is ready, so all this arguing is useless, anyway.

DegeRandolf:  The guide talks about using Linux or an Amiga to make the floppy update disk. I wonder if it can be done under Windoze?

RAWrite is available for Windoze.  BeOS uses it with its installer, actually.  You can get almost anything Linux without a GUI for Windows... it just might not work very well or at all.  :-)

[Argo]

@JJ

My A7N8X didn't have the flash from windows option. I'll look forward to it on my next board.

[ksk]

Last time I did a firmware update, it was for CS060MK2, a few weeks ago.

I think A1 firmware update looks easier.

[DegeRandolf]

Actually the A7N8X does have a flash from windows using the AsusUpdate software.  It can update your bios from the internet and allows you to flash it all from windows.  It also allows you to flash a bios file you already have, again right from windows.  I know this because that is the mb I have and I've done it twice.  Quick and simple.

[Rogue]

It's not hard, just fussy. Instead of writing a tiny utility in the CDs bootblock (like early startup options) to do a variety of things, you have to do it all yourself. Even I could hack up something in no time at all.

I don't get this. What is so hard about entering

fdcboot; bootm

or

diskboot 50000 1:0; bootm

or

setenv serverip a.b.c.d
tftpboot

?? Any of these lines will boot from a media, either floppy, CD-ROM or network. What "tiny utilitiy" do you want to put in what CD's "bootblock" (we're talking about an El-Torito boot image here anyway, no "bootblock")?

[theTAO]

@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

[Rogue]

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

I don't really see the difference. Last time I updated my CyberstormPPC flashrom, things looked very similar, I had to boot into initial CLI and enter a command from there. I don't think that the exact characters that you type matter very much.

This makes the firmware update on an AmigaOne (or a pegasos, for the matter) very similar to a classic Amiga in my opinion. Given the fact that the install guide is very detailed on what you have to do and type, I don't see it as a complete problem.

Finally, if you never had a blizzard or cyberstorm on your classic, the concept of "updating the firmware" is completely alien to you anyway because previously you had to either open your case and put in another ROM chip, or send it off to a dealer and have it replaced.

Over the long-term, I hope Hyperion and Eyetech will work to address issues like this.

Ideally this can be updated via Workbench, but that requires an installed OS 4 system. Problem is that the older firmware cannot boot the OS 4 CD. Unfortunately U-Boot does not support multiple El-Torito boot images.

But if you ask around for AmigaOne owners that actually did an update before, they will most likely confirm that the update is painless.

Here are a few replacement procedures off the top of my head

1) is potentially dangerous IMO, since it requires users to actually read on-screen text. The current updater will require you to type 'o' and 'k' to overwrite your flashrom only to force people to actually read it. I think that a flashrom update shouldn't be too comfortable because it is mostly a rare condition and should not be able to happen accidentially.

2) would be an option, but updating your firmware is essentially a hardware-dependent thing that isn't going to be integrated into the OS itself. The early boot menu on e.g. the CyberStorm would not have this option.

3) will probably be the way it will be in future updates and/or the final release CD. However, it requires that the firmware is able to use the AmigaOS install CD, and that is only true for later versions of the firmware, so for the time being it is a chicken and egg situation that can only be resolved in this way.

The Earlybird systems where specifically aimed at developers, technically inclined people, and former and present Amiga users

[Waccoon]

Ideally this can be updated via Workbench, but that requires an installed OS 4 system. Problem is that the older firmware cannot boot the OS 4 CD. Unfortunately U-Boot does not support multiple El-Torito boot images.

Gee wiz, I wonder how PCs manage to boot at all!  Oh, right.  They use bootloaders...

I don't think BIOS updates within OS4 are a good idea...

The problem is that UBoot doesn't have an update feature, but you are required to update through the firmware (as opposed to just writing data at a hard-coded hardware offset).  That's a "safer" way of doing it, since the flashing utility is essentiall in the BIOS, instead of a seperate program like it is on the PC.  Given that any PC program can hack my BIOS, I think I prefer the UBoot method.  Still, it can't be THAT hard to write a simple Early Startup screen.  After all, they did that over a decade ago on the "real" Amigas!

I don't get this. What is so hard about entering

If you have to type something exacly like in the directions, why type at all?  It's not hard, just unnecessary.

I was playing Gran Tourismo 3 recently, and it just occured to be how badly designed this game is.  Asside from the pathetic phsysics model, the interface is infuriating.  If I want to enter a race and my current car doesn't meet race regulation, what do I do?  Well, what I want to do is switch my car to one that meets regulations.  Instead, I have to...

Get out of the reace menu, get out of competition mode, get out of league select, go home, go to the garage, find a car that is regulation compliant (by memory), select it, "get in", get out of garage, get our of home, then go to race/league/competition/race, and then enter the race again.

WHEW!  Why should I be forced to spend 40 seconds to go to the garage when the game could instead show a list of cars that meet race regulations, and let me switch on the spot?  Why so much interface clutter?  It becomes very obvious after a few hours of navigating interfaces that the designers made sure the game looked very pretty, but is very frustrating to play.  I don't know why this game is so damn popular, and why every racing game is trying to clone the Gran Tourismo "feel".  Viper Racing on the PC is way, way more fun, even though you only have one car you can drive.

Any OS that wants to go up against Windows and MacOS *must* be interface savvy.  That's why I have so many nagging doubts about Linux, OS4, and just about everyone else who gets "squashed" by Microsoft.  Most operating systems are made by strict engineers and are very painful to use.  Even BeOS drove me nuts with its ambiguous error messages, badly designed windows, and crummy Start Menu clone.  The more I learn about Interface design, the more I realize that most people who are trying to compete against Windows are pretty much killing themselves.

is potentially dangerous IMO, since it requires users to actually read on-screen text. The current updater will require you to type 'o' and 'k' to overwrite your flashrom only to force people to actually read it

Interface designers know damn well that forcing people to read text doesn't work.  People never read long texts no matter what.  They just skim and see "o" and "k".  It's no more effective than having, "If you don't agree that this website is harmful and will give you lepracy, click 'No, I don't agree' to enter this website".  How many people are fooled by that every day?  My weblogs can tell you.  :-)

Unless you're my father.  He's so careful about everything it takes him 2-3 hourse to re-install Windows, 30 minutes to run FDisk, and about 2 minutes alone to realize that "large disk support" means FAT32.  On the other hand, when I'm helping my uncle on the phone, he will push buttons before I can even ask him, "What does the screen say, now?"  :-)

[Hooligan_DCS]

Sure looks easier than fixing a broken Pegasos 2 bios just because you did what the manual says.

[Rogue]

Gee wiz, I wonder how PCs manage to boot at all! Oh, right. They use bootloaders...

PCs use El-Torito boot images. "They use bootloaders" seems to be a bit of an understatement, since there needs to be a definition of what file to actually boot. And CD don't have boot blocks.

The problem is that UBoot doesn't have an update feature, but you are required to update through the firmware (as opposed to just writing data at a hard-coded hardware offset). That's a "safer" way of doing it, since the flashing utility is essentiall in the BIOS, instead of a seperate program like it is on the PC. Given that any PC program can hack my BIOS, I think I prefer the UBoot method. Still, it can't be THAT hard to write a simple Early Startup screen. After all, they did that over a decade ago on the "real" Amigas!

Anyone with half a brain can reprogram a flashrom. There is nothing magic about it. The firmware updater is an external program. If we had relied on U-Boot's build in capabilities, you would need to

- unlock the flashrom manually
- load the flashrom update into memory somwhere
(manually)
- copy the update into the flashrom (you guessed it, manually)
- lock the flashrom

I prefer an external program, and I'd prefer a program that makes a few sanity checks first.

Any OS that wants to go up against Windows and MacOS *must* be interface savvy. That's why I have so many nagging doubts about Linux, OS4, and just about everyone else who gets "squashed" by Microsoft

No one can go up against Windows and MacOS. Not at this stage. Neither is AmigaOS trying to do that, and I don't think that MorphOS is trying, either.

They just skim and see "o" and "k".

You must have read the text to see that you need to press those two letters. If there would have been a prominent "Press SPACE to continue" *then* people may complain, but as it is now, you need to read the text to find out that you actually need to press those keys. If you chose to skip the rest, you're beyond my help :-)

[Waccoon]

PCs use El-Torito boot images. "They use bootloaders" seems to be a bit of an understatement, since there needs to be a definition of what file to actually boot. And CD don't have boot blocks.

Only for CDs, I believe.  PCs are designed to boot CDs by emulating a floppy drive.  What difference does it make if a computer doesn't support multiple boot images?  The only image you HAVE to load is the bootloader.

Do memory cards and ZIP drives work differently than CDs?  I would presume they work more like hard drives.

It's just complicated since nobody thought the CD would be good for anything but storage, so nobody put effort into making a good all-purpose interface for booting, burning...  CD-ROMs are the work of the devil.  You'd think the people who make firmware for non-PC platforms would put their foot down and fix some of this mess.  If the AmigaOne can't boot directly off a CD, well, that's a big usability issue.

Anyone with half a brain can reprogram a flashrom. There is nothing magic about it.

There is if you've never heard of a BIOS or firmware before.  Most of my customers haven't, which is why they always have trouble using the products I am forced to sell them.

This is the 21st century.  Haven't we gone beyond typing at command prompts, yet?  Linux offers all sorts of TUI interfaces.  Programmers just don't know how to use them, or really just don't care -- no matter how much their customers might.

This is why I also tend to lean towards commercial software over free, open-source apps.  Nobody overlooks the importance of user interfaces more than non-commercial developers.  But, that's a different topic...

I prefer an external program, and I'd prefer a program that makes a few sanity checks first.

How do you load that external program without a bootloader?  Why not make the bootloader that external program?  Why not build a booloader into the firmware (assuming the hardware people aren't cheap.  There's a reason why most PC BIOSes are programmed in assembly).

No one can go up against Windows and MacOS. Not at this stage.

If not "this stage", then WHEN?!  People have been {bleep}ing that Microsoft has been a monopoly for a decade!  When will the market be ready for a serious competitor?  Five years from now?  Five years ago?  People can do something now or they can wait forever and never do anything.  I don't think anybody really understands why Amiga, BeOS, Atari, and everyone else went under.  Microsoft used to be a small fry, too, at one stage.

You must have read the text to see that you need to press those two letters.

You'd be surprised how much you can see without reading.  If a single frame of a movie flashes before your eyes for 1/30th of a second, you can probably recognize more than you realize, such as a character's shirt color, or whether there was a car or a boat in the background.

The longer the text, the less people will read, because unlike geeks, normal people can't bother spending a few hours figuring out every little engineering glitch and oversight.  Concise, well-designed products tend to be the most sucessful in the marketplace, if branding isn't a huge influence (IBM vs HomeGrownComputers, Inc).  How many people actually skim a 50-page UELA, let alone read it?  People don't have time for that stuff, and will rather just take their chances with evil disclaimers than waste time reading labyrinthine legal crap.

The real point, though, is that making people type "OK" isn't going to make them understand the instructions any better.  All developers should make an effort to describe what's going to happen, and just use safer methods.  Concepts like "safe saving" are rare in the industry, and others like "complete on reset" seem to be exclusive only to Windows.  It amazes me how many Operating Systems still have a "maintenance" mode, and are incapable of changing properties of files that are currently open.  That's what queues are for!