Skip to Content.
Sympa Menu

baslinux - Re: [BL] LILO and booting problems

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: baslinux AT lists.ibiblio.org
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] LILO and booting problems
  • Date: Sun, 1 Jun 2008 13:21:37 +0000 (UTC)


THe first step is to stop Windows 95 automatically
booting. You want it to give you a DOS prompt.
From there you can execute "win" to start Windows.
Or execute a loadlin command to start Linux.
Or execute any DOS command or bat file (eg menu).

To stop Windows auto-booting, do this:
(1) boot Linux
(2) mount /dev/hda1 /mnt
(3) cd /mnt
(3) edit MSDOS.SYS

You can also do this from a DOS prompt (DOS box, DOS boot disk, booting to command prompt with F8) if you first unhide the file with
attrib -r -s -h msdos.sys
(you can rehide with attrib +r +s +h if you want).

Booting with loadlin sometimes causes problems. Xvesa may not work if you have loaded a mouse driver, for instance, or himem.sys. These are TSR programs that I think use some part of memory needed by Xvesa. If you are not using DOS, you probably don't have an autoexec.bat or config.sys and should be okay.

I have one computer where the keyboard stops working in linux if I use loadlin.

If you don't use DOS and you prefer lilo boot you can probably boot directly to Windows by choosing DOS at the boot prompt (you may want to call it WIN instead in lilo.conf) after typing CTRL during bootup.
(Without editing MSDOS.SYS).

Loadlin is easier to set up but takes longer to boot to linux since first you need to boot to DOS. I use it anyway.

(4) change BootGUI=1 to BootGUI=0
(5) be careful not to add any extra characters
(6) exit, umount /mnt, reboot

Now when you boot Windows, you will get a prompt.

Cheers,
Steven


Sindi




Archive powered by MHonArc 2.6.24.

Top of Page