On Fri, 2 Aug 1996, John Tran wrote:
> > > 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.
On Sat, 3 Aug 1996, James D. Freels wrote:
> >"More sense on a PC" ? Duh ! Maybe for a "Win95" user.
> >Anyhow, the problems with "I've installed Micro$oft Windoze 95 on my
> >computer and can't boot Linux anymore" is just due to the fact that
> >M$ just assumes that anyone use their piece of cr
"James D. Freels" <[EMAIL PROTECTED]> writes:
> If it were that bad, why are there so many people using it?
I'm not commenting on anything but this line. IMO this may be a
reason why you have to put up with something, but it is never a good
argument for the merits of an item.
--
Rob
>"More sense on a PC" ? Duh ! Maybe for a "Win95" user.
>Anyhow, the problems with "I've installed Micro$oft Windoze 95 on my
>computer and can't boot Linux anymore" is just due to the fact that
>M$ just assumes that anyone use their piece of crap and just baldly
>recreates the MBR.
I know all
> In my case, I started out (several years back) using LILO to dual-boot
> DOS or Linux. But, I actually have found now that the Loadlin option
> not only is more convenient for Win-95, but actually makes more sense
> on a PC. The only problem is that Loadlin has some memory
> limitations. But,
Hi,
> The DOS+LOADLIN solution is in my opinion a very practical and safe one.
Yes, that is true. And I would suggest everyone who starts with Linux to use
this combination, if:
- he has a Dos system
- she doesnt need the additional boot password security
- has a minute more time
> I read
> "mu
> > 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 en
Hi,
> other = /dev/hda1
> label = win95
> loader = /boot/any_d.b
AFAIK any_d.b is used to swap C: and d: drive. If you OS is on the first drive
you need to run chain.b instead.
Greetings
Bernd
--
(OO) -- [EMAIL PROTECTED] --
( .. ) [EMAIL PROTECTED],ka.sub.org} http://home.pages.d
or of size=4096 bytes!)
__ Reply Separator _
Subject: Re: LILO and W95
Author: debian-user@lists.debian.org at cclink
Date:02.08.96 07:26
On Thu, 1 Aug 1996, nathan work wrote:
> ok, i just loaded linux after w95 for the first
>What I have done is similar to what Susan suggest in using LOADLIN, but I
>have setup a menuitem in config.sys to handle it. The line I use in the
>config.sys file is:
>
>shell=c:\loadlin.exe c:\vmlinuz root=/dev/hda6 ro
>
>This assumes my root file system is on hda6. This way when I boot I have
Dear Nathan:
I currently run Win95 and DEBIAN GNU/Linux 1.1 using the following
lilo.conf:
prompt
boot=/dev/hda
delay=5
image=/vmlinuz
label=linux
root=/dev/hda2
vga=ask
other=/dev/hda1
label=win95
table=/dev/hda
The DOS partition is on hda1 , Linux on hda2 , swa
Dear Nathan:
I currently run Win95 and DEBIAN GNU/Linux 1.1 using the following
lilo.conf:
prompt
boot=/dev/hda
delay=5
image=/vmlinuz
label=linux
root=/dev/hda2
vga=ask
other=/dev/hda1
label=win95
table=/dev/hda
The DOS partition is on hda1 , Linux on hda2 , swap is hda3.
After
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
On Thu, 1 Aug 1996, nathan work wrote:
> 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
Hi Nathan --
You said:
> - 95 will not 'recognize' LILO, and boots right into 95.
If you installed win95 *after* you installed lilo) you have win95's mbr.
To boot Linux now you can either install LILO as the boot manager,
with advice from Randy Jones, or you can retain win95 as the boot
manag
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
On Thu, 1 Aug 1996, nathan work wrote:
> 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
17 matches
Mail list logo
