Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My situation is different from yours. I post this a lot and people always do something different or never say what the results were, so I have no idea whether this is a fluke or not but it works for me. Because I swapped drives and didn't bother changing anything, both hda1 and hdb1 are marked 'bootable' and I have this
other = /dev/hdb1
label = NT
table = /dev/hdb
as my NT stanza. Master-boot (as I understand it) basically means LILO will tell ny 'other' that they are booting from 0x80 regardless. I only really run Slack but all five systems *can* boot.
I have no followups. I always get confused when I say something like this and people suddenly tell me they've switched to GRUB or that they were *really* trying to dual-boot OS/2 and ask for more help. But if you boot with LILO between Linux and an NT system on hdb1 with it flagged bootable, it oughtta work.
thank you guys... however yesterday I made a really bad mistake.....I crashed both boot loaders.......
how can I restore the windows one *without* having a bootable WinXP CD or a Rescue Floppy?? any ideas?? Or is there a way to do this through Linux?
I'm not sure what 'crashed both boot loaders' means, but simply reboot with a Linux floppy or CD, edit your lilo.conf, rerun /sbin/lilo, and reboot. As long as the XP *system* is intact and properly configured, LILO will boot it. But you ought to have boot floppies (or several) for every system you've got.
Weirdly enough, you can do this with Mandrake 9.2 CD1-- one of their rescue options is "Restore Windows Bootloader". But of course you're not using Mandrake, and I'm not sure if the Slack rescue options include this (not going to reboot to find out, sorry ).
Dare I wonder how you have installed XP without a bootable CD?
Do you perhaps have a Win98 or ME boot floppy? You could use that to boot and try the fdisk /mbr command. It might work.
But I must ask you again-- I know you said that it was a real PITA to reinstall all of the Windows Updates and all.... but is it still? Because at this point, it's pretty much as simple to reinstall both OSes correctly as it is to fix this mistake.
well, I have boot floppies for both, but those for Win won't work properly.
At the last disk I got a blue screen I LOVE THOSE
And I don't know why, but when I booted from the slackware cd, mounted my linux drive, reconfigured lilo.conf, and tried to run /sbin/lilo it wouldn't work....
Are you sure that this master-boot thing works?
But mayber I will just reinstall. But then wouldn't it be better to install windows first on master, and then Linux on slave?
Where should I place the boot loader?
The correct order of installation for a dual-boot system is:
1. Windows first, on the first primary partition of the first hard drive. If installing more than one version of Windows, install the oldest version first, then the newer (i.e., Win 98 then Win XP). The Windows bootloader will always install to the MBR, so no choice there.
2. Install Linux to any partition (primary or extended-- extended is preferred to prevent Windows from trying to give Linux partitions drive letters when Windows is loaded) on any drive.
3. Install LiLO to the MBR. This will overwrite the Windows bootloader, but LiLO will see that there is a Windows partition and will make an entry for it, enabling you to boot either Linux or Windows from the menu. If you had more than one version of Windows installed, choosing the Windows entry in the LiLO menu will take you to the Windows boot menu, which will enable you to choose which version of Windows you want to boot.
Bootloaders (all bootloaders) come in two stages. The first stage is on the MBR, and tells the booting system (which at this point in the boot process knows pretty much nothing but that there is an MBR) where to find the specific information as to what operating systems exist, where they are located, and how to boot them.
Thus, LiLO's first stage, on the MBR, points to /etc/lilo.conf on the Linux partition, which has the information as to what the menu should look like (graphic, text, what color), what OSes should be listed, and where the boot files for each listed OS reside.
The Windows bootloader (I think that's NTLDR for XP and 2000), points to boot.ini, which lists the items on the boot menu and how to boot them. However, since Windows expects to be the sole OS on the system, the boot.ini menu is by default not displayed unless you have more than one version of Windows installed, in which case boot.ini shows both Win 98 and Win 2000, for example.
However, if you have only one version of Windows installed, no Windows boot menu will be displayed, since it is unnecessary, but "not displayed" is not the same as "non-existant".
thanks, you all saved me from insanity...... I got Windows to work again.
i used the winme boot floppy, fdisk /mbr and it went just fine.
Now I even have win on primary, as i switched the drives in the meantime.
@motub: Thanks, you were great help to me
I hadn't read your post first, but now it came handy!
Well, I *always* install WinXP by first installing WinMe and then updating...
Do you know why my PC doesn't boot from win CDs but does for Linux ones? My old one even booted exactly those win cds....strange...
However. NOW I'll reinstall Linux.. and then it will work or I'll.....
Oh, I see... you have a WinXP Upgrade CD, then (non-bootable)? What a pain that is... mostly because it means you have to install WinMe, which is.... not the highlight of Microsoft's career, shall we say.
Anyway, you always do upgrades, but I was considering in the case that you might have been doing a side-by-side Windows install, like the way I once had Windows 98 installed only to try Wine with a native Windows, but Windows 2000 to actually use should I need to use Windows, plus (several) Linux.
Anyway, glad the floppies worked, looking forward to good news (oh dear, I think I've been playing too much Faxanadu on TuxNES... now I'm quoting it... )
no. I HAVE A "REAL" WINXP CD. IT DID BOOT UNDER MY OLD PC.....JUST NOW, NO WAY
M$ thank you so much for being so kind to me, and for the invalueable time i've spend with fixing probs you were generous enough to give to me
oh, *yes*, that was ironical.....
what is Faxandu on TuxNES ??? emulation or something?
Yep. TuxNES is an N(intendo)E(ntertainment)S(ystem) emulator. Much simpler to use that than fighting with my boyfriend to disconnect his C64 from the TV when we're both having a fit of "old-school gaming"....
Anyway, very weird about the CD not booting. I don't suppose you're like me and missing the (very annoying) "Press any key to boot from CD" command that Windows seems to require these days (for pete's sake, I put in a bootable CD, and set my BIOS to boot from CD first, so JUST BOOT THE D*MN CD, WOULDJA??? But noooooo... and yes, that was ironical, too )
But fine, we're not going to discuss the difficulties of that other OS on this forum, so let's just get this dual up and running with the ease and simplicity it was designed for (at least from the Linux end), so you can be a happy person .