You can also use the dd command to copy the backup saved by LILO to the boot sector. Refer to the LILO documentation if you wish to do this. FDISK /MBR MBR stands for Master Boot Record. This command replaces the boot sector with a clean DOS one, without affecting the partition table. Some purists disagree with this, but even the author of LILO, Werner Almesberger, suggests it. It is easy, and it works.

A few people have reported this problem. It appears to be related to some CD drives that have DMA issues. If this solution works for you, would you mind sending us mail (linux-project@pcquest.com) telling us what CDROM drive and motherboard you use? Thanks! The file zlib-1.1.3-22.i386.rpm on the CD seems to be corrupted, and I am getting errors mentioning libz.so.1 The distribution supports this setup under certain circumstances, but you must follow a slightly complicated method.

The lilo program (not the complete LILO package), uses the command line option -u to uninstall the LILO boot loader. You have to supply the device name of the device you installed LILO on, for example: This rewrites the original, pre-LILO master boot record back to the first hard drive, from the boot record saved in /boot/boot.0300. If you installed LILO to a partition as a secondary boot loader, for example, /dev/hda1, lilo re-installs the original boot sector from the save file /boot/boot.

Add this entry to /etc/lilo.conf, then rerun lilo. other = /dev/hda1 table = /dev/hda label = Windows The other points to the partition containing Windows and table points to the partition table of the disk.

Add something like this to your /etc/lilo.conf file under linux and rerun /sbin/lilo. Note that Solaris *MUST* be the active partition, on either the primary or another another hard drive. To use LILO with Solaris on the primary partition, install LILO in the MBR and mark the solaris partition as active. In this example Solaris is on your second hard drive (hence the "loader" line): other = /dev/hdb1 loader = /boot/chain.

If you have FreeBSD and Linux on the same disk, just follow LILO's installation instructions for booting a non-Linux operating system. Very briefly, these are: Boot Linux, and add the following lines to /etc/lilo.conf: other=/dev/hda2 table=/dev/hda label=FreeBSD the above assumes that your FreeBSD slice is known to Linux as /dev/hda2; tailor to suit your setup). Then, run lilo as root and you should be done. If FreeBSD resides on another disk, you need to add loader=/boot/chain.

From kernel versions 1.1.80 on, the compressed kernel image, which is what LILO needs to find, is in arch/i386/boot/zImage, or arch/i386/boot/bzImage when it is built, and is normally stored in the /boot/ directory. The /etc/lilo.conf file should refer to the vmlinuz symbolic link, not the actual kernel image. This was changed to make it easier to build kernel versions for several different processors from one source tree.

Sure, you can. Create a primary partiton BEFORE your Windows partition (e.g. with PartitionMagic) and get a boot manager (I use the german tool 'Bootmanager', you can get a free trial version at http://www.bootmanager-pro.de).

Follow the instructions for the previous question substituting /dev/hdc as directed. An alternate, much-more-difficult method follows that doesn't involve the "switch drives with /boot/chain.b" trick. These are basically the steps I 'discovered' through countless failed attempts to get Solaris to boot from the secondary master. I got LILO to boot Solaris/x86 2.5.1 from the master disk of the secondary IDE. Solaris was initially installed in the primary-master disk, i.e.

Basically, the Linux LILO boot loader is used to fool solaris into thinking the slave is the master and vice versa (with the chain.b line) Add this in your Linux /etc/lilo.conf: use /dev/hdc instead of /dev/hdb if your second drive is the secondary IDE master instead of the primary IDE slave drive) Solaris had a bit of trouble because for some reason it had the default boot device as the primary HD and couldn't mount the root filesystem off of it (because it wasn't there).

Therefore booting from a USB device is not possible, neither to restore data from CD via DOS-based programs.

Add this entry to /etc/lilo.conf, then rerun lilo. other = /dev/hda1 table = /dev/hda label = WindowsThe "other" points to the partition containing Windows and <q>table</q> points to the partition table of the disk.

No. Windows Me doesn't include Real Mode DOS, so it's impossible to boot the system into DOS mode or reboot the system into DOS mode. You can, however, use a Windows Me boot disk to boot into a command prompt.

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. So it is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

DOS is a Disk Operating System, that means it's an OS that uses a disk. Operating systems for IBM PCs since the early 1980s were called DOS. DOS consists of the command prompt, mostly command.com and two kernelfiles. That's a basic DOS system. DOS was a mainstream OS until Windows 95 (which also uses DOS, btw) threw it off the market.

You just need to copy a himem.sys from a Windows 9x/ME system to your DOS system and load it before your emm386 (e.g.: add DEVICE=C:\DRDOS\HIMEM.SYS

You have to change the country-settings in config.sys (add 21000 to the country code): COUNTRY=21049,437,c:\drdos\country.sys This will switch the currency from "DM" to "EUR" and the format of the date from "dd.mm.yyyy" to the new format defined in DIN EN 28601 (ISO 8601) "yyyy-mm-dd". This will also work for the other countries in the European Union which take part in the currency union and which are supported by DR-DOS: Simply add 21000 to the country code in config.

If LILO doesn't work, and if the machine has MS-DOS or Microsoft Windows, you may be left with a computer that won't boot. This can also happen on an upgrade to your Linux distribution. Re-installing LILO is the last thing that the installation does. So it is vitally important when installing or upgrading Linux on a dual boot machine, to have a MS-DOS or Windows rescue disk nearby so you can FDISK -MBR. Then you can go about using LOADLIN.EXE instead of LILO.

Refer to the section "Making Installation Diskettes" from the RedHat Linux Installation manual at http://www.redhat.com/support/manuals/RHL-7.1-Manual/install-guide/

If you press the F8 key during the message "MS-DOS is started..." is displayed, you are switched in the step-by-step boot process and are able to suppress the Windows start. Program Manager has a limitation on the number of groups that you can create. You are also limited to 40 Program Items per group. Remove a group/item, and try again. The install should work successfully. Look in the [windows] section of your 'win.ini' file.

Use the command map, to exchange BIOS drives virtually, like this: grub> root (hd1,0) grub> chainloader +1 grub> map (hd0) (hd1) grub> map (hd1) (hd0) I have a separate boot partition on GNU/Linux (or another UNIX-like system), and GRUB seems not to handle this situation correctly. Because GRUB is a boot loader and it normally runs under no operating system, it doesn't know where a partition is mounted under your operating systems.

This is a known problem. Windows refuses to boot when it isn't installed on the first hard drive and shows a black/blank screen. To handle this, you will have to "fool" Windows into believing that it is installed on the first hard drive with a little tweak in your boot loader configuration. Please note that in the below example, Gentoo is installed on hda (first disk) and Windows on hdb (second one). Adjust your config as needed.

Usually the Win9x will be the C: drive, which also contains the files needed for booting. So, you cannot simply reformat this partition to remove Win9x. Instead, the following procedure should work: Delete the C:\Windows and C:\Program Files folders, along with any other folders on the C: drive that you do not need anymore. Some reports also say you can format the C: drive and boot from the Win XP CD, which will allow you to repair the boot files.

A: Use the "System Configuration Editor" included with Windows 98/ME. Click on Start, Run. Type in "msconfig" and click OK. To view the list of programs that load during boot up click the Startup tag. Uncheck the programs that you wish to eliminate. Note: Making changes in the other tabs of the System Configuration Editor can negatively affect your system or could cause your computer to stop booting to Windows.

Western language HTML documents use the ISO 8859-1 Latin-1 character set. Microsoft products use their own "extension" to Latin-1 using a variety of characters which do not appear in Latin-1 nor in Unicode. To correct such incompatibities, use a Perl script called demoroniser. It is installed in Abel. Use it as follows: demoroniser sickfile.txt curedfile.txt

Never - a small instrument vacuums the cloudy lens protein from the eye. It can be powered by ultrasonic energy, though laser energy is being used on a limited basis. But all " vacuums" require a small incision to permit access to the lens.