ftp://ftp.altlinux.org/pub/distributions/ALTLinux/4.0/Desktop/4.0.3/iso/altlinux-4.0.3-desktop-i586-install_ru-dvd5.iso

Why lilo needs "static-BIOS-codes" in this case -- see
https://bugzilla.altlinux.org/show_bug.cgi?id=15604 .

In automatic mode, the installer installed the ALTLinux system on /dev/hdb. But
the BIOS can't boot from /dev/hdb. Without this option LILO can't be installed
onto /dev/hda, and so the installed system is not bootable.

One way to fix it would be to fix #15604 (make static-BIOS-codes unnecessary; I
don't know whether this possible). Another (quicker) fix is to teach the
installer to use "static-BIOS-codes" option in such setups.


Workaround:
(Now I describe the workaround step by step; perhaps, someone will use it.)

boot the rescue system from the distro DVD, mount your freshly installed system,
e.g.:

mkdir /mnt/disk
mount /dev/hdb2 /mnt/disk

Also, lilo will want to access /boot/, so relocate your real future /boot/:

mount --move /mnt/disk/boot /boot

add "static-BIOS-codes" to /mnt/disk/etc/lilo.conf,
change "boot=/dev/hdb" (left there by the installer) to "boot=/dev/hdb",
and ultimately install LILO:

lilo -C /mnt/disk/etc/lilo.conf

(After this, the system became bootable.)


Actual Results:  
Hacking is needed to make the system bootable after installation in "auto mode".

Expected Results:  
No hacking is needed to make the system bootable after installation in "auto mode".