Qu� tal, me gustar�a hacer un apunte a mi mensaje anterior:
Antes ten�a en la misma m�quina un arranque dual Red Hat + Potato y todo
funcionaba perfectamente. La Potato estaba donde est� ahora, en el disco
grande, la Red Hat donde ahora est� g�indos. Al instalar g�indos decid�
dedicarle la partici�n primaria del disco peque�o, para contentar al nene tuve
que cambiar los discos de orden (antes ten�a el de 2.4 Gb como "secondary
master" y lo pas� "primary master") por que seg�n tengo entendido necesita estar
instalado en la partici�n primaria del primer disco. Pues eso, que con los
discos intercambiados (y sin el virus este con forma de SO) el LILO me funcion�
siempre a la perfecci�n.
Saludos,
Quique
Enrique Marcote Pe�a wrote:
> Hola:
>
> No soy capaz de poner a funcionar el LILO con windows 98. Tengo dos
> discos duros hdc de 10 Gb con Potato y el hda de 2.4Gb, donde contra mi
> voluntad he tenido que instalar el windows ese. Instalo el LILO y no
> logra arrancar, me da el error 40, osea
>
> L 40 40 40 40 ...
>
> He mirado en la documentaci�n del LILO y para este error en concreto no
> dice gran cosa ("Seek failure". This might be a media problem. Try
> booting again) lo intento y nada. Tambi�n he probado a especificar la
> geometr�a del disco...m�s de lo mismo.
>
> �D�nde puedo encontrar m�s informaci�n al respecto?�Alguien ha tenido
> alg�n problema similar?
>
> Muchas gracias,
>
> Quique
>
> Mi lilo.conf es el siguiente:
>
> # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
> # --------------- `install-mbr(8)', `/usr/share/doc/lilo/',
> # and `/usr/share/doc/mbr/'.
>
> # +---------------------------------------------------------------+
> # | !! Reminder !! |
> # | |
> # | Don't forget to run `lilo' after you make changes to this |
> # | conffile, `/boot/bootmess.txt', or install a new kernel. The |
> # | computer will most likely fail to boot if a kernel-image |
> # | post-install script or you don't remember to run `lilo'. |
> # | |
> # +---------------------------------------------------------------+
>
> # Disk geometry.
> #
> #disk = /dev/hda
> # bios = 0x80
> # sectors = 63
> # heads = 64
> # cylinders = 1023
>
> # Support LBA for large hard disks.
> #
> lba32
>
> # Specifies the boot device. This is where Lilo installs its boot
> # block. It can be either a partition, or the raw device, in which
> # case it installs in the MBR, and will overwrite the current MBR.
> #
> boot=/dev/hda
>
> # Specifies the number of deciseconds (0.1 seconds) LILO should
> # wait before booting the first image.
> #
> prompt
> timeout=50
>
> # Enable map compaction:
> # Tries to merge read requests for adjacent sectors into a single
> # read request. This drastically reduces load time and keeps the
> # map smaller. Using `compact' is especially recommended when
> # booting from a floppy disk. It is disabled here by default
> # because it doesn't always work.
> #
> #compact
>
> #linear
>
> # Specifies the VGA text mode at boot time. (normal, extended, ask,
> <mode>)
> #
> # vga=ask
> # vga=9
> #
> vga=normal
>
> # Specifies the device that should be mounted as root. (`/')
> #
> root=/dev/hdc1
>
> # Installs the specified file as the new boot sector
> #
> install=/boot/boot.b
>
> # Specifies the location of the map file
> #
> map=/boot/map
>
> # You can set a password here, and uncomment the `restricted' lines
> # in the image definitions below to make it so that a password must
> # be typed to boot anything but a default configuration. If a
> # command line is given, other than one specified by an `append'
> # statement in `lilo.conf', the password will be required, but a
> # standard default boot will not require one.
> #
> # This will, for instance, prevent anyone with access to the
> # console from booting with something like `Linux init=/bin/sh',
> # and thus becoming `root' without proper authorization.
> #
> # Note that if you really need this type of security, you will
> # likely also want to use `install-mbr' to reconfigure the MBR
> # program, as well as set up your BIOS to disallow booting from
> # removable disk or CD-ROM, then put a password on getting into the
> # BIOS configuration as well. Please RTFM `install-mbr(8)'.
> #
> # password=tatercounter2000
>
> # You can put a customized boot message up if you like. If you use
> # `prompt', and this computer may need to reboot unattended, you
> # must specify a `timeout', or it will sit there forever waiting
> # for a keypress. `single-key' goes with the `alias' lines in the
> # `image' configurations below. eg: You can press `1' to boot
> # `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
> #
> # message=/boot/bootmess.txt
> # prompt
> # single-key
> # delay=100
> # timeout=100
>
> # Kernel command line options that apply to all installed images go
> # here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
> # the Linux kernel `Documentation' directory.
> #
> # append=""
>
> # Boot up Linux by default.
> #
> default=DebianPotato
>
> image=/vmlinuz
> label=DebianPotato
> read-only
> # restricted
> alias=1
> #image=/mnt/hdc2/boot/vmlinuz-2.0.35-2
> # label=RedHat5.1
> # root=/dev/hdc2
> # read-only
> # alias=2
> #image=/boot/vmlinuz-2.0.35-2
> # label=DebianOld
> # read-only
> # alias=2
> #image=/vmlinuz.old
> # label=LinuxOLD
> # read-only
> # optional
> # restricted
> # alias=3
> # If you have another OS on this machine to boot, you can uncomment the
> # following lines, changing the device name on the `other' line to
> # where your other OS' partition is.
> #
> other=/dev/hda1
> label=Windows
> # restricted
> alias=2
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
