Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
08-10-2004, 06:40 AM
|
#1
|
LQ Newbie
Registered: Mar 2004
Distribution: Mandrake 8.2
Posts: 13
Rep:
|
LILO vs Boot.ini... Round One
You guys are gonna love this...
I seem to have...err... 'misplaced' my boot.ini file under win2K pro. I can't use fixmbr from the recovery console as i also have RH9 installed, with LILO being used to choose between the two, and doing so would overwrite LILO, which would just be a pain to put back.
Win2K can still boot after displaying a message for a few seconds stating "missing boot.ini file. Booting from C:\WINNT". It will still load, but its just annoying, ya know.
I know this is more of a windows problem, but it has kind of a Linux twist, and you guys are better at this sort of thing than any windows forum ;-)
|
|
|
08-10-2004, 07:13 AM
|
#2
|
Senior Member
Registered: Jun 2004
Location: Australia
Distribution: Mandriva/Slack - KDE
Posts: 1,672
Rep:
|
Make a lilo floppy or rescue cdrom - if you have mkrescue command and a cd burner then
mkrescue --iso
and burn the iso image to cd. It will allow you to boot back into linux after you fix windows.
you can do the same sort of thing with floppy with
lilo -b /dev/fd0
Test the floppy or cd before fixing windows with fixmbr...
Last edited by amosf; 08-10-2004 at 07:15 AM.
|
|
|
08-10-2004, 07:18 AM
|
#3
|
Senior Member
Registered: Jun 2004
Location: Australia
Distribution: Mandriva/Slack - KDE
Posts: 1,672
Rep:
|
Of course once you fix everything and boot back to linux you run lilo again so you can boot RH as before.
|
|
|
08-10-2004, 07:34 AM
|
#4
|
LQ Newbie
Registered: Mar 2004
Distribution: Mandrake 8.2
Posts: 13
Original Poster
Rep:
|
right, im a newbie at all this, so basically follow your instructions to create a LILO boot disk to get back into linux, test it, then use fixmbr, then boot back into linux. does the LILO boot disk automatically reinstall LILO as the default boot loader?
|
|
|
08-10-2004, 08:41 AM
|
#5
|
Moderator
Registered: Aug 2002
Posts: 26,480
|
|
|
|
08-10-2004, 09:08 AM
|
#6
|
Member
Registered: Feb 2004
Location: Belgium
Distribution: Suse 9.1 Pro / Gentoo
Posts: 114
Rep:
|
the boot.ini file is located in you're C drive and not on the MBR so reinstalling will not fix any problems with that.
If you can boot windows without a problem you just have to locate the boot.ini file and put it in the c:/ folder (your c drive) you will have to display hidden folders and files (its somewere in the explorer options)
If it is not found you can try to make one youself with notepad.
I don't know how it should look but you can look that up on the internet
|
|
|
08-10-2004, 10:27 AM
|
#7
|
Senior Member
Registered: Jul 2004
Location: Skuttunge SWEDEN
Distribution: Debian preferably
Posts: 1,350
Rep:
|
Since boot.ini isn't needed, just create an empty file with that name. It could work?
|
|
|
08-11-2004, 04:12 AM
|
#8
|
LQ Newbie
Registered: Mar 2004
Distribution: Mandrake 8.2
Posts: 13
Original Poster
Rep:
|
I've tried searching for the boot.ini file with hidden system files shown, its gone...but where, who knows?
I've also tried replacing the boot.ini file with one i've seen which looks familiar to the one i used to have (i cant be 100% certain it was the same... can YOU remember every last letter and dash in your boot.ini file?) and it brings up a new message saying that it cant find something called NTOSKNL.exe, or something similar. Hm. I may just leave it as it is. I can't be one hundred percent certain, but I think this has all been caused by a virus. Damn them.
|
|
|
08-11-2004, 04:54 AM
|
#9
|
LQ Guru
Registered: May 2003
Location: INDIA
Distribution: Ubuntu, Solaris,CentOS
Posts: 5,522
Rep:
|
here is mybot.ini
i have windows in hda5,i do not have anything in my C drive except the windows system files,msdos.sys,boot.ini, etc etc
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(4)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(4)\WINNT="Microsoft Windows 2000 Advanced Server" /fastdetect
regards
gaurav
|
|
|
All times are GMT -5. The time now is 06:29 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|