Hello Anant Hardikar,
....
>Question;
>From here, how to restore w2K's MBR and thereafter restore boot magic to take over multibooting
>w98, w2000, and Linux. I do not like to start from fresh, as I have done it previously
>successfully. The w2K boot disks are available.
The problem is in lacking of the following three files on the C: drive:
boot.ini -multiloading menu file,
ntdetect.com
ntldr } - specific files for Win2k loading.
These files can be restored by manually from another mashine.
However, they should be copied in the due course (one after another,
I foget who is first).
Note that yours io.sys file is already modernized and requires above
files!
Second, thes files can be restored by automatically when you make
reinstallation procedure for win2k.
Note that you should to stop reinstallation after first PC
reloading.
>Alternatively, how to get LILO to MBR and re configure it to see the three OSs without needing
>to reinstall w2K.
My advice is : don't go to MBR with Linux LILO. Use floppy for
booting, and when you learn Linux(minimum 0.5 year) then you can try.
>How to solve the flashing screen problem in Linux, and to start the xwindow GUI?
You should first used to Linux about one month or so in the text mode!
Midnight Commander can be on yours service there. But without any BOOK
(about ~500 pages) I don't go with Linux.
Since yours hardware is new, therefore there no Linux drivers for it.
Therefore Linux first probe should be taken on an old PC (300-400
MHz). X-Window config is a very delicate problem for novice. Better
one time to see somewere (with guru), or get a good Book and read
MANPAGES.
Several Linux (Slackware, Red Hat, Mandrake) have XF86Setup utility.
Try it every day to learn more, and one beatifull morning you get
X-Window. This utility has the following pages:
Mouse config, Keyboard config, Video Card config, Monitor config &
Other config. At the end try xvidtune, which automatically find out
the optimal video config for you.
The last advice is don't load X-Window by "startx" command.
First try it by "X -probeonly > /tmp/x.val 2>&1" command.
In the tmp/x.val file you can see what is going with yours drivers.
--
Best regards,
Yakymakha
Curious about the people moderating your
messages? Visit our staff web site:
http://freepctech.com/staff.shtml
|
