Viper_Jatt

I recently completed the task of converting my system running Windows XP to dual-boot Windows and Linux.

I needed to run Windows most of the time, but occasionally needed to boot Linux to run special applications.

The one overriding requirement was to change the existing Windows setup as little as possible.

In this case, that meant adding a second hard drive.

Easy enough, right? Well, not so fast.

The computer in question is a standard white-box PC with Windows XP installed on its one hard drive.

One option was to shrink the exiting Windows partition with and install Linux in the resulting free space.

However, this was too intrusive.

I did not have a backup of the data on the Windows machine, and didn't want to take the time to make one, so I was loath to do anything that could wipe it out.

So I installed and set up a new second drive, then installed Fedora Core 3 in the standard manner.

When the installer asked what drive to use, I chose the second IDE drive, hdb.

The other key step was to make sure the installer did not install a Linux boot loader on the primary hard drive.

While having the installed do this is generally the recommended method of installing a dual-boot Linux/Windows system, I didn't want to do it because of my goal of minimizing changes to the Windows disk.

The Windows bootloader (NTLDR) can be configured to boot Linux partitions, so I decided to use it as the primary bootloader.

The default boot option would remain Windows, so if i took no action on boot, the system would go to Windows as it always had.

However, if i selected Linux in the NTLDR boot menu, it would hand off to the Linux bootloader (GRUB) on the second drive.

The Fedora installer gives you the option of placing GRUB in the master partition of the primary IDE drive (hda) or in the boot partition of the secondary IDE drive (hdb1).

I instructed the installer to take the second option.

Note that without extra configuration later, this setup will not boot to Linux, because whatever bootloader is on the primary drive -- in this case Windows -- will always be run.

Another option I considered was removing the primary Windows drive and placing the Linux drive in the system as the primary drive.

I could then install GRUB on the Linux drive (the primary now) and configure it to also boot Windows on the secondary drive.

One caveat here is you must configure GRUB to .

Otherwise, Windows gets confused.

I elected not do this type of install because it seemed more complicated than installing Linux on the second drive.

Boot sector transplant

The next step in the process is to save a copy of the Linux boot partition.


This can be done either with dd in Linux or with the free utility under Windows.


Either program simply takes the first 512 bytes on the disk and puts them into a file.


The dd command to do this is dd if=/dev/hdb1 of=bootsect.lnx size=512 count=1.


Once you have this file, copy it to a diskette or some other removable media so you can then copy it to the Windows drive for NTLDR.

I happened to use Bootpart because I forgot to use dd before I booted the system back to Windows.


If you use Bootpart you don't have to copy the boot sector to a diskette, as you are already in Windows.


To complete the transplant, place the file you created with dd or Bootpart on the Windows drive as C:\bootsect.lnx.

Now it's time to tell Windows about Linux.


Again, there are two ways to go about this.


If you are doing everything manually, fire up a text editor in Windows and edit the file c:\boot.ini.


Add the line c:\bootsect.lnx="Linux" to the end of the file.

The Bootpart way to do this is simpler: run Bootpart with the command bootpart Linux c:\bootsect.lnx "Linux".


Bootpart will take care of adding the proper entry to boot.ini for you.


Testing and final thoughts

Your system should now be correctly configured.


To test it, reboot the machine.


After the BIOS screen, the first thing you will see is the NTLDR menu asking which OS you wish to boot.


If you do nothing you will go to Windows.


If you choose Linux on this screen, NTLDR will use bootsect.lnx to hand off the boot process to Linux, and start booting from your second hard drive.


The next screen you will see will be your Linux bootloader screen.


From this point on, your system boots the same as any other Linux machine.

And there you have it: a Windows machine that boots Linux as well.


The advantages of this setup are:

• The Windows configuration remains essentially untouched.
• No changes to the Windows hard drive boot sector are necessary.
• Removing Linux from the machine is simple: physically remove the Linux disk and remove the Linux entry from boot.ini under Windows.
• Windows users have a tendency to reinstall the OS from time to time. If that occurs on this system, the Linux disk would be untouched (although you might not be able to boot to it until you copy the boot sector again and fix boot.ini).

While this configuration isn't ideal for everyone, it is a great way to add Linux to an Windows machine with minimal disruption of an existing Windows installation.

    Dhillon

I have Linux as a virtual OS using VMware workstation.

More Info @ http://www.vmware.com/products/desktop/ws_features.html

    Viper_Jatt

I am downloading it right now...to see what difference it would make...

i understand that its install into the current os...and gives a virtual environment of LINUX...

my question to you is: is it as powerful as having a proper LINUX installed like on the seperate HDD? or does it not matter and it will provide me with the same ability as any other LINUX...?

    Viper_Jatt

I have got another problem that I have been trying to work out for sometime now.

I have got a Laptop and it fell out of my hands down 1 full story and it went SMASH...so its all covered with ducktapes and all (it kind of looks real cool though). The amazing thing is the only real damage was done to the HDD and sometimes the computer fails to read the HDD and just does not boot until I POUND IT WITH SOME JOHN CENA ELBOWS...

Well its all under warranty and will be replaced but I had some work to complete on it...and What I am looking for is to be ABLE TO BOOT MY LAPTOP USING MY DESKTOP VIA A NETWORK CABLE...

Dhillon veer could you help me out with this?

i know very little about pxe rom and stuff ...

Please give a step by step instructions...appreciate your help...

    Dhillon

Two operating systems will be running at the same time, sharing the resources so don’t expect the same performance like you may be getting right now.

However Linux doesn’t require much hardware so it should work fine.

    Dhillon

You can boot your laptop via a floppy or a cd drive but even for that HDD drive should be readable.


I think your HDD may just have a loose connection, check it.

    !~TOP_GUNNER~!

aa ki gal ho rhi aa...menu ta kush palle hi nhi pe reya

    Viper_Jatt

i have already tried booting via cdrom...but like you have mentioned...it wont work without hdd detection...

now the thing is i have already checked out the connections for hdd in the laptop...there is only one big connection really...its fine...the inpage kernel error that i am gettin when suddenly the computer reboots is apparently due to a bad hdd...and since i got to use the laptop i need a way to boot it using winxp on the other system in case of failure...is there no way that this is possible?

    Viper_Jatt

ok just to be sure; i carried out the following tasks on my lt.

1. removed the hdd and placed it back in safely and mounted the dvd-rw on as was.

so even if there was/is a loose connection its taken care of.

2. i have replaced the ram with the new same make ram of 1 gb
and there are no problems because its from the vendor

3. cleaned out the fan unit and applied the thermo-paste to the cpu just to make sure that overheating is not the cause...which indeed it is not!

4. started the computer and it worked fine until suddenly it said again...kernel inpage error...and rebooted

now the thing is multi tasking works fine...everything is working fine but when it reboots it wont boot at all...it brings up the PXE screen where its trying to look for instructions over the network that i have established with my desktop...

now if i, as i said before, hit it hard where the hdd is for a few time...it starts working sometimes for a whole day sometimes for 2 mins...

and i getting seriously frustrated and need a way to boot via...network so in that case i can use my network card in the laptop at the university...