Anna
Advanced Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору
Нашла в чем проблема
Взято отсюда: http://www.redhat.com/support/resources/faqs/rhl_general_faq/s1-bootloader.html
Цитата: Question:
I have installed Linux to dual boot with Windows. My first drive, /dev/hda is Linux, and my second drive is my Windows drive. Windows worked fine until after I installed Linux. Now, when I select "dos" from the LILO: prompt to boot to Windows, all I get is "Starting...." and then my machine locks, up. My entry for Windows in my /etc/lilo.conf file looks like this:
other=/dev/hdb1
label=dos
table=/dev/hdb
Why is this happening and how can I work around it?
Answer:
Windows is expecting to be the first disk in your computer and does not know what to do when you try to boot it as the second drive. In order to work around this, you must modify your /etc/lilo.conf file so that the entry for Windows looks like this:
other=/dev/hdb1
label=dos
table=/dev/hdb
map-drive = 0x80
to = 0x81
map-drive = 0x81
to = 0x80
Once you have done this, you must re-run LILO so that your changes take effect. To do this, type /sbin/lilo -v -v.
What this does is fool DOS/Windows into believing that it is the first drive in your system. |
В последних версиях Лило (начиная с 22.5) также имеется опция "master-boot", которая фактически делает тоже самое
Цитата: "master-boot"
This flag (LILO version 22.5) indicates a DOS/Windows/OS2 or other
system which will only boot from BIOS device 0x80, the "C:" drive, or BIOS
device 0, the A: drive. When this
flag is specified, if this drive is not assigned device code 0x80 or 0 by the
BIOS, then the chain loader will dynamically swap the device code actually
assigned with device code 0x80 or 0 to make this drive appear
to be the first hard or floppy drive, "C:" or "A:".
This flag is easier to use than "map-drive=", and is preferred,
if simple forcing of device code 0x80 is all that is required. It is also
more general, in that the necessity to swap BIOS device codes is determined
dynamically at boot-time, not at boot install-time, as with "map-drive=".
It is slightly more powerful than "boot-as=", in that the device code which
is assigned, 0 or 0x80, is determined dynamically. |
|
