Discussion Locked

boot.ini and dual boot in xp

0 helpful
25 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
i want to have two completely independant (bootable) xp systems running on different IDE drives on my computer. as i?ve understood (?) from reading about and experementing on the subject, if you intsall different operating systems the boot sequence still needs to access the boot.ini file on the first drive (c; ide0) in order to boot from the second drive (D; ide1). so i?m guessing i need to add a mbr and a bunch of boot files to my d drive in order for it to work... is this possible and if so what do i do? my reason for all of this is that i want to have one encrypted drive (with preboot authentication) for work and one clean for personal stuff. thanks!

25 replies

by scp

Wouldn't it be easier to just use a boot manager? Most boot managers do al the changes automatically. You just have to install all the OS on different partitions.

by bodirt

but even if i use an mbr boot manager on c, i cant?boot fron the d drive since its obviously missing some necessary boot sequence files... i?m guessing this has something to do with the windows installer. that it leaves out som boot files on the second drives because it recognizes a complete system on the master drive... are there any programs to fix this?

by hal 9000

If you install XP on a D,E,F,G,H,I,J,K,L,M,N,O,P or whatever drive it will just boot from that drive without any worries. It is only the older versions of Windows that have to boot from the C drive XP isn't limited by that part of Windows.

Col

by stress junkie

scp is right. The way to go is to use a boot manager. The one problem with this is that if the boot drive goes bad then the second disk doesn't have the code in the MBR to boot.

You can also select the boot drive in the BIOS. Select the first drive that the motherboard sees as the boot drive. Install XP. Then select the second drive that the motherboard sees as the boot drive. Install XP. You can stop there and select which disk you boot by using the motherboard boot sequence.

Or you can then add a boot manager to both disks' MBR. This would then be the ultimate solution. You use the boot manager as scp suggested. If the first hard disk goes bad then you can select tell the motherboard to boot from the second disk. It will have the boot manager code and will boot without the presence of the first hard disk.

I just had my first/boot hard disk go bad last week. I have M$ on the first hard disk and Linux on the second hard disk. When the first hard disk went bad I couldn't easily boot either system. So I decided that I should be able to boot the second hard disk even if the first hard disk were removed. I installed a boot manager on the MBR of the second hard disk and told the motherboard to boot from the second hard disk. It worked great. When I get around to replacing the first hard disk and installing M$ on that I will put a boot manager on that disk's MBR. Then having the ability to boot from the second hard disk will just be a recovery feature.

Since it happened to me just last week I would recommend that you consider the possibility of your boot drive going bad and what you would do in that case. Putting a boot manager on the MBR of the second hard disk means that you will still have access to the system on the second hard disk and that you can take your time to replace the first hard disk. You can continue to use the system on the second hard disk so replacing the first hard disk can be done at your leisure.

by bodirt

>>You can also select the boot drive in the BIOS. Select the first drive that the motherboard sees as the boot drive. Install XP. Then select the second drive that the motherboard sees as the boot drive. Install XP. You can stop there and select which disk you boot by using the motherboard boot sequence.<<

will this resolve the problems i?m having with missing boot files on the d drive? i mean does it trick the windows installer in some way to make the installations independant?

by stress junkie

I haven't put XP on the second hard disk but I believe that it will work if the second hard disk is the boot disk. I can confidently say that it might work. I'm sorry that I don't have the real answer, but try it and find out. Then you can let me know how it worked out. :-)

I did this with M$ on the first hard disk and Linux on the second hard disk. My motherboard is currently set to boot from the second hard disk. When I get around to replacing the first hard disk I can install M$ there and then use a boot manager to select which disk to boot from.

by bodirt

what i did in the end was to have only one hard drive at a time connected during installation. this intsalls two independant systems that can be booted directly from the the bios startup manager. thanks for your input!

by hal 9000

On the install of XP it will move that drive to the end of the chain and just boot from there. It will be the only HDD that you can not change the drive letter of but it works great that way.

Col

by vasanthraj

Yes. Having just one harddisk connected during installation did the trick for me, when i had the same issue several months ago. I started using BIOS to choose the harddisk to boot from. Later,i tweaked the BOOT.INI file on first disk and added entries pointing to XP and 2000 installation on second disk, and bingo..i had a BOOT screen from which i can choose the different OS installations on two different drives. Strangely, the same tweak on the BOOT.INI of second drive didn't work for the Windows ME (which was in C: of first drive). Eventhough i didn't bother much in that time...Any thoughts on why that didn't work??

by apotheon

Keep in mind that when I refer to "partitions" here, they may be partitions on one drive, for on more than one drive. To the OSes you're using, it doesn't much matter whether things are on one drive or many.

To dual-boot Windows XP with Windows XP, you should be able to set it up pretty easily, actually. First, you install (or have a preinstalled) XP system on one partition. Then, install XP again on another partition. Pay close attention to what you're doing while installing: the XP installer (depending on which version of the XP installer you use) should give you an option to set it up as a multiboot system.

Even if it doesn't, you should just be able to tell it to which partition you want it to install. Then, after installation is finished, edit the boot.ini script(s) to adjust to suit your needs.

To be really safe about it, you can check your motherboard's CMOS capabilities. If it allows you to specify which physical hard drive is the first boot device, you can simply install on one drive, then pull that drive out and install on the other, then make sure you've got both drives in. Then, if you are booting one and want to boot the other, you restart the computer and enter BIOS/CMOS settings to switch which disk is bootable this time. It's a little more of a pain in the butt, though it will be the most "safe" method available and easiest to recover.

Here's what I'd do: Have three partitions between whatever number of drives you're using (plus whatever addition partitions you need for your arrangement of data and so on: I always have at least a bootable partition and a separate data partition so that if I need to nuke and pave the OS I can do so without having to restore all data from backup). The extra partition should only need to be about one GB (actually, far less, but with each GB being so cheap these days, you might as well err on the side of caution and flexibility). Install XP on one partition. Install XP on another partition. Do a very minimal install of Linux on the third, 1GB partition.

With this Linux install, I'll recommend using GRUB as your bootloader since that's what I know best, though there's no real reason you can't use Lilo. While installing, it should make the system multi-boot (or give you options for doing so) automatically, because modern Linux installers are quite good at recognizing the presence of multiple OSes. After the install, edit the GRUB configuration file to put the booting options in the order you like. The first option will be the default, generally. You can set the amount of time before the menu times out during bootup and goes automatically to the default OS here, as well.

The GRUB configuration file will be located at /boot/grub/menu.lst in most Linux systems, though a couple of them (like Red Hat Linux) use /boot/grub/grub.conf instead. The configuration file should contain information about how to configure it; it does in every Linux distribution in which I've edited menu.lst or grub.conf, at least.

This gives you the added advantage of a third, bootable, console-based, system-recovery OS, in addition to providing what is probably the easiest method to ensure you get exactly what you want for booting options. It's far less likely to hose up your system than using XP's automated multiboot options, and easy to fix if you have to reinstall XP and screw up the multiboot, too (since an XP install almost always over-writes the MBR).

Good luck.

by jbm

Hello. Excuse me, I don't write english, I try.You have just to create 2 primary partitions. Yous instal your first XP Os on one partition. When you finish, you instal your second XP OS on second primary partition. You'll have 2 distinct OS on 1 PC. Good luck.
Don't use the extension partition. You can use Boot magic program to manage 2 primary partition

BATISTE

by hectorjleslie

You may want to give Virtual PC or VMWare a try, you don't need to mess with the partitions and you can delete or create the virtual drives as many time as you like without compromising the integrity of your system. This is great for testing. Hope this helps...

by laser3

I had what I thought was a good thing going for me, but then one parathion got messed up.

What I have now is tow disks, each with one bootable Windows 98 partition and one Windows XP partition. Booting form the first (physical) disk I can boot into Windows 98 on that disk or Windows XP on either disk.

Since the primary partition on the second (physical) disk got formatted, I cannot boot into the Windows XP partition on that disk. I have tried copying the boot.ini file from the first disk, and also trying to change various numbers and letters in it, but to no avail. There is also the problem that the "users" on the second disk XP partition are not the same when I boot from the first physical disk as when I boot from the second one.

What I want (which may not be obtainable) is to be able to boot form each disk into the same XP partition on the second disk, with the same users.

Can it be done on the basis of what I have now? How?

by bagmaster50

Get Boot Magic from Power Qwest to use as a boot manager. It will allow you to boot to any amount of OS's while hiding them from each other. Bott Magic also comes with Partition Magic, so if you have a Partition Magic cd you can install Boot magic from it. Take note: Boot Magic has to be run fron a fat or fat32 partition. The manual for Partition Magic gives complete instructions on how and where to install it. It can even be installed onto it's own fat partition. It requires at least a 32 meg partition to install to.

by laser3

Thanks for th eidea of using Boot Magic and Partition Magic. However, I once downloaded a trial version of these progarms, some yeras ago, and the results were not pleasant. I lost the contents of an entire partiation.

I don't necessarly blame the software; maybe I didn't follow the instructions properly. But I can't take a chance on the same thing happening again.

I think I'll just leave things as they are until I can get a different solution.

by craig herberg

Before making any kind of change to your hard drive's partition, you should always make sure to have a full image backup of your system. With products like Norton Ghost and an inexpensive external hard drive, there is no reason to loose all of your data.

Craig Herberg

by hal 9000

Both of those programs are almost fool proof now and even the older versions where very easy to use. Just how long ago was this?

But I suppose it did reinforce the need for a good DR Plan to be implemented by you so you should be perfectly OK to go ahead now and try it again with no adverse side effects.

Just remember to have your backup's up to date before starting.

Col ]:)

by craig herberg

There is no better way for people to value a solid backup plan. Hopefully, people will learn this valuable lesson early enough to not loose a lifetime of research or a client list ten years in the making.

Craig Herberg

by eingram1

What good does a complete backup do if, when trying to restore a backup from a different hard drive, the system gets almost everything restored, then crashes with the message "restore failed"
This has happened to me twice. Once using NT Backup and once using PartionMagic's Drive Image.

by craig herberg

Hopefully, they loose it before they have years of client information or medical research that is not replicated anywhere.

by hal 9000

I've never had a single problem and even then I always keep a DATA backup separate from the main complete backup.

With XP I always keep the following folders backed up without question The My Documents Folder complete, The Favorites Folder, the E-Mail Folder containing all of the E-Mail and The Address Book Folder. So even in the event of a total reload being required I can always restore the data without a problem. Of course if I have data stored in any different folders these get backed up with out question.

I always perform a Data Backup daily to another HDD on my main workstation and a remote HDD on one of the networked units just in case of a HDD going bad then save these to a Tape and DVD weekly or more often if there is some important data that is saved. The complete accounting package is also saved in this manner as well so even if I have to reload the computer I still have all of my Data intact.

The only reason that you should get corruption of either a Drive Image or a complete Backup is if the Drive you are backing up to is going bad and the SMART is reporting "Imminent Drive Failure" that can cause a HDD to not restore correctly as the data has been corrupted while the backup is being done and there is no verification run to make sure that the complete backup has actually been performed.

You should always verify the integrity of any backup that you perform or it will be next to useless when really needed. I can remember one Government Department who had a Security Officer perform their Tape Backup daily and they spent a great deal of effort to save their tapes but unfortunately when their server fell over they discovered that for the last 6 months the tape had never been written to as while the proper directions had been followed by the Security Officer the Tape Drive had gone bad so it would run for a few minutes but it never actually wrote anything to the tape and because the guy had other duties like the physical security of the building he just pushed the buttons and then proceeded on his rounds so the Tape was never checked to make sure that it had actually saved the data. Once the Security Officer returned and the tape drive was no longer running he would pull out the tape and drop it into a secure bag and place it in the local fire proof safe and the next day it was transfered off site but it was never checked and because it was a low priority the job was allocated to someone not conversant with computers.

When I eventually found a recorded copy of their supposedly saved data they only had 6 months of work to reenter and at the same time changed their data backup system as the Bureaucrats found out just how important a Data Backup actually was.

Col

by hal 9000

Isn't it? I just hate it when they loose the stuff after years of work and I have to send the dead drive/s away for data recovery as a few $ spent up front would have saved them several K to recover their data. ;)

But the best lesson is always in the hip pocket. :D

But if it wasn't me who had to break the news to them it would be so much better. :)

Col ]:)

by rguernsey

(Sheesh! 3 years later - I'm sure will will help someone.)
I have that setup. It's easy.
Edit the boot.ini using the built-in utility.
(What utility? GOOGLE IT! =-p)
Copy this and paste it. You can change the "Windows XP 1" in between the quotes to what ever you like.

[boot loader]
timeout=15
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP 1" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP 2" /noexecute=optin /fastdetect

I installed XP on each IDE drive separately then set them up together in BIOS. Doesn't matter which is master or slave they will both boot. Sometimes you get a blinking (or not) _ up in the left corner and just hangs. If so use the boot list (F10 or F12 etc...) to get you started. Once you are booted you can edit from there. You will also be able to choose which drive will boot first by default.

This discussion is closed to new replies.