thank you Arun,
 i managet to get it this time byt my problems are not
yet over.
i again formatted the disk and loaded linux(genome
workstation). then created a partition for windows in
/mnt( i was under the impression that i will be able
to mount windows later. after that i uninstalled lilo
by using lili -u.

now the problems are
1. i still am using a boot disk to load linux( this
problem is minor)
2. when booting i always got to boot in the
interactive mode to stop the GPM and netconfig daemon
which were the causes of the problems. i want to know
how to make sure that these services dont start when i
boot.
3.i am unable to configure xwindows using
xconfigurator because every time i rin this my
keyboard and mouse hang and i have to press
ctrl+alt+F2 to login as root again and kill the
process(xconfigurator).

please help me on how to go about this.
thank you
Ashok


--- Arun Sharma <[EMAIL PROTECTED]> wrote:
> On Fri, Dec 17, 1999 at 04:15:32PM -0800, Dogpile
> ping wrote:
> > Problems 
> > 1. as soon as i set the boot disk in the CD- rom
> the
> > installation started but the keyboard and mouse
> are
> > not working( i have the Keyboard with all the new
> > features like sound control and shortcut keys to
> > internet on the keyboard).
> 
> The keyboard is not the problem usually. Try to run
> without *any* services and then start each one
> manually
> to see what's hurting you. Try reading up about 
> run levels to see how to disable services (in your
> case GPM)
> at startup.
> 
> > problem 2.
> > when i switch the P.C on the Lilo prompt does not
> come
> > up it only displays "LI" and nothing happens when
> i
> > hit tab. i have to get the system up and running
> with
> > a boot disk every time.
> 
> LILO docs say:
> 
>  (<nothing>)  No part of LILO has been loaded. LILO
> either isn't installed
>     or the partition on which its boot sector is
> located isn't active.
>    L <error> ...   The first stage boot loader has
> been loaded and started,
>     but it can't load the second stage boot loader.
> The two-digit error
>     codes indicate the type of problem. (See also
> section "Disk error
>     codes".) This condition usually indicates a
> media failure or a geometry
>     mismatch (e.g. bad disk parameters, see section
> "Disk geometry").
>    LI   The first stage boot loader was able to load
> the second stage boot
>     loader, but has failed to execute it. This can
> either be caused by a
>     geometry mismatch or by moving /boot/boot.b
> without running the map
>     installer.
>    LIL   The second stage boot loader has been
> started, but it can't load
>     the descriptor table from the map file. This is
> typically caused by a
>     media failure or by a geometry mismatch.
>    LIL?   The second stage boot loader has been
> loaded at an incorrect
>     address. This is typically caused by a subtle
> geometry mismatch or by
>     moving /boot/boot.b without running the map
> installer.
>    LIL-   The descriptor table is corrupt. This can
> either be caused by a
>     geometry mismatch or by moving /boot/map without
> running the map
>     installer.
>    LILO   All parts of LILO have been successfully
> loaded. 
> 
>       -Arun
> 
>
--------------------------------------------------------------------
> The Linux India Mailing List Archives are now
> available.  Please search
> the archive at http://lists.linux-india.org/ before
> posting your question
> to avoid repetition and save bandwidth.
> 


=====
Ashok Kumar

__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
--------------------------------------------------------------------
The Linux India Mailing List Archives are now available.  Please search
the archive at http://lists.linux-india.org/ before posting your question
to avoid repetition and save bandwidth.

Reply via email to