Boot-it ng and installing windows

I got BootItNg, and have a few problems, maybe someone has come across the same problems.

1. I get "Multi-os partition xxx on hd0 could not be checked for changes.  Unable to mount the filesystem".
What does this mean?

2. I install WinXp 32-bit version ok.  On the 64-bit version, after installing, the boot gives
<WindowsRoot>\System32\ntoskrnl.exe missing
Does anyone know why it says this?  How to fix it?
amp834Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

NaturaTekCommented:
From the booting documentation (http://neosmart.net/forums/showthread.php?t=3118)

1. Ntoskrnl.exe is missing or corrupt

"Windows could not start because the following file is missing or corrupt:

<Windows root>\system32\ntoskrnl.exe.

Please re-install a copy of the above file"

This means the ARC paths in the [operating systems] section or the default entry in BOOT.INI is incorrect. Double-check that multi() and disk() are both set to 0, and verify that rdisk(x)partition(y) points to the correct partition where Windows XP is installed. Instructions on the correct configuration of boot.ini can be found here.
2. Hal.dll is missing or corrupt

Windows\System32\Hal.dll missing or corrupt:

Please re-install a copy of the above file.

This means the ARC paths in the [operating systems] section or the default entry in BOOT.INI is incorrect. Double-check that multi() and disk() are both set to 0, and verify that rdisk(x)partition(y) points to the correct partition where Windows XP is installed. Instructions on the correct configuration of boot.ini can be found here.
http://neosmart.net/wiki/display/EBCD/Rebuilding+Boot.ini
(Actually, in my case this error was due to a corrupt ntldr file in XP, though I was trying to boot from BootIT NG, which depends on the boot files in XP, instead of from the Vista bootloader entry created by EasyBCD, which depends on the boot files in Vista, copied over from XP)
0
NaturaTekCommented:
skip section (2) above, pasted too much.
In a nutshell edit your boot.ini tell it what drive/partition is xp
0
Become a Certified Penetration Testing Engineer

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

amp834Author Commented:
None of these seem to do it.
0
NaturaTekCommented:
did you edit the boot.ini? copy the contents of your boot.ini and place it here
0
Gary CaseRetiredCommented:
Did you create a dedicated primary partition for XP x64; then create a boot item for it; and then remove the XP x32 partition from the MBR for that boot item?

If you do that (so the ONLY partition visible in the partition table when you install XP x64 is the partition you created for it), and then boot to that partition (it will fail) -- and THEN boot to the XP x64 installation CD and install it, it will work perfectly.

Any deviation from that can cause problems.   It sounds like you tried to install XP x64 to the same partition you installed the x32 version (as a dual-boot within that partition).
0
amp834Author Commented:
Hi Gary.  I was hoping you would see this post eventually!

I made a partition just for xp64, plus a data partition.  All other partitions are hidden.

When installing xp64, it saw
unpartitioned space (8mb)
C: (the one for xp64),
D: (the data partition),
free space

And I installed onto C:.  It installed ok, I think reboot was fine, but when I put BootItNg back, it would give the ntldr missing error when booting xp64.  Should I have told BootItNg to save the mbr before putting BootItNg back?

I can clear c: and try again, but I think I've done it twice already.

0
Gary CaseRetiredCommented:
The setup above is right ... after XP x64 finishes installing and reboots, it most likely will have "wiped out" Boot-It (i.e. the system will boot directly to XP x64) -- is that what happened?    That's normal ... you then just boot to the Boot-It CD and select "Reactivate Boot-It".    Once that's done, you should be able to boot, choose the XPx64 boot item from the boot menu, and the system should boot fine.

Where in this process is it working differently for you??
0
amp834Author Commented:
I did exactly that--Install xp64, reboot, goes to xp64 ok, then reboot on boot-it and tell it to reactivate boot-it.  When I choose the xp64 from boot-it, I get the ntldr error.

Just as a sanity check, I'm wiping the partition and installing it again, to double-check if this is what happens.  If there's something I should try while doing this, please let me know.

0
amp834Author Commented:
When I'm installing xp64, I get

unpartitioned space, 2003 MB
D: Partition 2, ntfs 199997 MB
C: Partition 1 [Unknown]
unpartitioned space, 236943 MB

I will install on C: Partition 1.
0
Gary CaseRetiredCommented:
What are the "real" partitions on the drive?   i.e. what does Partition Work show?

... and what exactly do you have "visible" in the MBR for the boot item for XPx64?

i.e. what does the right side of this screen show for your XPx64 boot item?


Boot-Edit.jpg
0
amp834Author Commented:
I can't take a screenshot, but the right side has HD0:  xp64, xpdata.  Everything else is empty.
0
Gary CaseRetiredCommented:
Okay, that's what it should show.   And you DID try to boot to that item (which will fail) first; and THEN boot to the XP x64 CD, right?

If you've done that, this should be a very simple process as long as you absolutely choose the correct partition to install to.    I presume the two partitions you "see" from the XPx64 installation match what you're expecting -- i.e. the "D: Partition 2, ntfs 199997 MB" partition is the right size for your "xpdata" partition.

... as long as that's right, then installing to the C: partition should work just fine --- although I'm not sure why it's showing as "unknown" ... did you create it in Boot-It with NTFS formatting?
0
Gary CaseRetiredCommented:
... by the way, does your system by any chance have a floppy drive?
0
amp834Author Commented:
Yes, booting on new partition xp64, bootitng says it can't, to put CD and press cntrl-alt-del.  

I'm not sure where that 1st 2003MB free-space partition is coming from!  I do have a few 20gig partitions, but they should be hidden.

Unfortunately no floppy drive.  I usually get one, but didn't on this machine!

It's installing now, I will be able to tell about bootitng in a few minute.
0
Gary CaseRetiredCommented:
After you finish installing x64 (and it boots okay), try this:

=>  Boot to Boot-It, but do not "re-activate" -- instead go to Partition Work (I forget the exact set of options at that point -- you may have to choose "Maintenance Mode" & then Partition Work) and select View MBR.    See if the partition for XPx64 is active (Do NOT change anything at this point -- just want to know if it's flagged as active okay).

=>  Now reboot from the Boot-It CD and choose re-activate Boot-It.

=>  Remove the CD and boot again -- go to Maintenance Mode; Partition Work; and View MBR again and see if the XPx64 partition is active.   If not, highlight it and make it active.   Apply that change; reboot; and see if you can boot to XPx64 okay now.
0
amp834Author Commented:
Viewing MBR, xp64 was still active.

Reboot gave same problems.

I changed boot.ini and added Multi...Partition(1)    (and 0 and 2), it turned out to work on on Partition(1).

My guess, it saw the empty space as Partition(0), and so the C: drive was Partition(1).  

Or, more likely, since the Ntdata partition was 1st, it was Partition(0), and c: was partition(1).  So there is some inconsistency between the winxp64 installer and subsequent running?


But it works ok now.

Any insights
0
Gary CaseRetiredCommented:
This is an issue of the correlation between the partitions in the MBR and the settings in BOOT.INI in XP.

You could change the BOOT.INI file and then rearrange the entries in the MBR in Boot-It's boot item ... but there's no real reason to swap things around, since it's working fine now.
0
amp834Author Commented:
It's not clear to me what BootItNg is doing vs. what WinXp64 is doing, with the

0 free space
1. ntdata
2. XpOs
3. free space

The nt installer saw #2 and assigned it C: (because it was a primary?, that's why it didn't assign C: to #1?), which is what I wanted, then D: to ntdata.  That was the #0 and #1 partitions in BootitNg.

But after installing, it probably wrote something to the XpOs, and subsequently saw it as partition 1 instead of partition 0.

I still don't get it, but that's ok.  It is running.  I may run into problems if I copy the Xp64 partition and try to boot from the copy.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Gary CaseRetiredCommented:
If what you just detailed is how the MBR "looks" in the boot item for XP, then it's clear what's happening.

You normally want the booting OS to be in the first slot in the MBR -- you've apparently got it in the 3rd.   I'd have made item 0 the XPOs (assuming that's your XPx64 partition), then item 1 the ntdata, and left the other two entries blank.   That's most likely what happened.

Note you can set the MBR to "look" like whatever you want -- the MoveUp, MoveDN, and Clear buttons let you do that.

I suspect that if the XP partition was in entry 0, it would work exactly as you were expecting -- you will, of course, have to change the BOOT.INI to reflect the correct entry.
0
amp834Author Commented:
In the BootIt-ng screen, I had only 2 partitions for booting Xp64:  xp64 in slot 0, ntdata in slot 1.  is there some other screen in BootIt-ng I should also have configured?
0
NaturaTekCommented:
This is a bit off, but is there a reason you are using bootitng other than just for xp and xp64? You can achieve the same result
http://www.pcstats.com/articleview.cfm?articleID=1910 /(one of the many tutorials out there)

If you planning on adding more os's like linux/vista/etc, bootit more plausible.
Clear instructions are at http://www.terabyteunlimited.com/downloads/bootitng.pdf

If you are wanting bootit, someone will help solve for you, if you just want xp and xp64 there are number of other ways including with no 3rd party software.
0
Gary CaseRetiredCommented:
You've got it configured just fine - and clearly all's working well.   Not sure why the BOOT.INI wasn't set correctly initially, but it's fine now, so you can easily image/restore/copy the XPx64 system to other partitions, etc.

NaturaTek -- the flexibility Boot-It provides is much better than using NTLDR to manage the boots => complete isolation of the different OS's;  C: drive installs for all; etc.
0
NaturaTekCommented:
garycase
I know what bootitng is and used it. Since the user is struggling to get it working I'm asking what are his needs, 2 os's relating to xp, there are simpler ways, if thats all he wants. Maybe he googled how to dual boot and came up with bootitng..and trying to make it work. Maybe he specifically wants is, I don't know. Adding multiple os's outside of xp, bootitng is plausible. Either way, hopefully he's all good!
0
Gary CaseRetiredCommented:
Clearly it's working fine now ... so there's no reason to change.

I also looked at the question history for the author, so I knew he had earlier done this in other, less flexible ways (most recently with Grub).

... Once you get used to Boot-It, it's unlikely you'll ever use anything else.   My main system can boot 11 different OS's;  an older system can boot 16; and all of my systems have at least 2 or 3 options.
0
amp834Author Commented:
Hi NaturaTek.  I needed to have the OSes be on c:, with OS1 not seeing OS2 at all, etc.  This was a followup post after I actually started using BootIt-NG.

I also tried using Ubuntu, with Grub and partition tools, I had the same "ntldr" problem there!, so I suppose I could try that again, but I got everything working well enough already, so I'll go with this configuration for now.

Gary, I think I'm ok now, and will close this question early next week (leaving it open just in case there are any residual comments).  Thanks for your help.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
System Utilities

From novice to tech pro — start learning today.