On Tue, 1 Sep 1998, Kenneth Stephen wrote:

> Gevaerts Frank wrote:
> 
> > On Mon, 31 Aug 1998, Norbert Bottlaender-Prier wrote:
> >
> > > Kenneth Stephen a écrit:
> > > >
> > > > 2.4 I use Win95. Can I use LILO?
> > > > I. See the Linux+Win95 HOWTO.
> > > > II. Some people claim that the HOWTO is incorrect, and that Win95 reinstalls
> > > > itself on the MBR unpredictably. Many other people think this not true.
> > >
> > > It IS true. Not a question of opinion. And it's predictable : No means
> > > to escape this "feature" of Lose95...
> >
> > As far as I know, Win95 does this every time you run it's setup.
> > I use lilo and keep a boot disk just in case.
> >
> 
> Well, folks, I am puzzled a bit. What exactly is this Win95 'setup' that is
> referred to above? I have had Lilo on my system for over a year now (with Linux as
> the default kernel) and have rebooted a few times into Win95, but have never come
> to grief.
> 
It's something in the control panel, it's not normally run. (Add/Remove
programs -tab: Windows setup or something)
> > > >...
> > > >
> > > > 2.6 How do I get Linux to recognize memory above 64mb.
> > > > In your /etc/lilo.conf, put a line like:
> > > > append="mem=##M", where ## is the size of your RAM in megabytes or
> > > > append="mem=##k", where ## is the size of your RAM in killobytes.
> > >
> > > Add a warning : NEVER indicate MORE ram than you really have.
> >
> > And even a bit less, to account for the memory that the BIOS reserves. (ie
> > if you have 128M, tell the system it's 127M). The bios usually needs a few
> > 100 K's.
> 
> I have never heard of this before. I would imagine that the kernel is aware of the
> amount of memory reserved for BIOS and would subtract this out to get the correct
> value. Is your statement documented somewhere, oris it speculation on your part?
> 
Don't know if it is documented in some proper place, but there was talk
about this in linux-kernel

Frank

> Kenneth
> 
> --
> There is no such thing as luck. 'Luck' is nothing but an absence of bad luck.
> 
> 
> 
> 

Reply via email to