Mitch a écrit:
> I think you are trying to do it the same way BIOS works.
> Under Mac OS, you allow the regular OS to load (or protected mode/safe
> mode) and then use user-friendly solutions (System prefs, third-party
> tools like Tech Tool, Onyx, or Mac Pilot.
> At the worst, you can use Terminal and Unix commands to change things.
>
> You aren't ever expected to get down into the system before it loads
> the OS; that's for the extremely hard-core programmer types, not for
> regular users.
I'm mostly a Mac user (I do programming but not on low level like the
Firmware). But when I saw the first Windows machine in a school (in
addition to say "Ouch, that's bad!"), I tried the BIOS (well, not the
first day).
In the BIOS, I saw some useful options as for instance the ability to
start up the system by clicking on the mouse (or by typing some letters
on the keyboard, like a password). So, if you set a password to
"aeiouy", you can type, while the computer is turned off, "aeiouy" and
the computer wakes up. But this behaviour relies on the hardware of this
specific machine.
This is the reason that made me thinking there could be useful options
in the Firmware (setting more extended options than the Mac OS interface
provides). After all, there's nothing that states "the Firmware does not
set options" in the docs.
|
