nathan work writes: > ok, i just loaded linux after w95 for the first time. i know very > little about linux or unix for that matter and i'm having a real problem > - 95 will not 'recognize' LILO, and boots right into 95. i didn't have > this problem with 3.1. what i need is for someone to be gracious enough > to take me by the hand and show me how to overcome this (to keep w95 > from controling what's booted). please email me if you'd like:
There is a mini HOWTO about this problem: Linux+Win95. As a short explanation. Boot your machine under Linux (I hope you have a bootdisk) and edit /etc/lilo.conf accordingly. Then run lilo. Et voila. Here's my lilo.conf # Start LILO global section boot = /dev/hda compact # faster, but won't work on all systems. delay = 50 vga=extended ramdisk = 0 # paranoia setting # End LILO global section # Linux bootable partition config begins image = /vmlinuz root = /dev/hda2 label = linux # Linux bootable partition config ends # WIN95 bootable partition config begins other = /dev/hda1 label = win95 loader = /boot/any_d.b # WIN95 bootable partition config ends Michael -- Michael Meskes | _____ ________ __ ____ [EMAIL PROTECTED] | / ___// ____/ // / / __ \___ __________ [EMAIL PROTECTED] | \__ \/ /_ / // /_/ /_/ / _ \/ ___/ ___/ [EMAIL PROTECTED] | ___/ / __/ /__ __/\__, / __/ / (__ ) Use Debian Linux! | /____/_/ /_/ /____/\___/_/ /____/
