Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 24124
  • Last Modified:

What is the proper order to run the Fixboot, Fixmbr, and BOOTCFG/rebuild commands?

Dual boot system has an HP_Recovery first partition followed by the C: partition. Then there is an Extended partition with various logical partitions, none of which need to be bootable, although one of the logical partitions is a copy of the HP_Recovery partition.

The system is hanging on bootup  when the screen says "starting windows". I've been doing a buncha partition shifting with Partition Magic 8. Then I got the dreaded "hal.dll" problem. Cleared that by putting the first two partitions back where they belonged, now I feel like I'm so close to a breakthrough!

Note: There is no "Recovery CD". Tried two XP installation CDs to get into the recovery module, but its demanding a password even though I know for FACT there is none. (Even verified it) So I plan on using a ME boot disk into an A:\ prompt then just use attributes ("C") for the Fixboot, Fixmbr, and BOOTCFG/rebuild commands.
0
CaptainPickard
Asked:
CaptainPickard
  • 3
  • 3
  • 2
  • +3
4 Solutions
 
Jay_Jay70Commented:
Hi CaptainPickard,

as far as i am aware there is no set order, i do them whichever way i feel like on the day! usually fixboot   then fixmbr
0
 
alextoftCommented:
fixmbr writes a new master boot record
fixboot writes a new system partition boot sector
bootcfg just fixes up your boot.ini configuration

It doesn't matter which order you run them in.

I'd recommend getting hold of a PE environment. It's a bootable live Windows CD used by OEM's to mess with images once they're all packaged up and they want to make modifications without booting them. BartPE is a common varient and there's a guide to creating one here: http://www.nu2.nu/pebuilder/

If its asking for a password and there definately isn't one, you could have killed it completely. May be time to use a "repair install". It's a procedure which is often very hastily recommended on EE, but might end up being your only option.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
FriarTukCommented:
by recovery module are you meaning recovery console?
by demanding password do you mean asking for the administrators pswd? if so try blank.

make sure your boot partition C: is the first drive (probably contains the hp recovery partition as well as the logicals)
run
 bootcfg /list    to view boot dev's
 bootcfg /scan  to scan for boot dev's
 bootcfg /rebuild to rebuild the boot.ini
 fixboot c:        to fix the primary drive's system boot files (like ntloader
only run fixmbr if you think a virus has modified it

can you access the recovery partition to reload the o/s?
0
 
mrenosCommented:
Fixboot creates a new boot sector on the hard drive or the partition,
Fixmbr fixes the MBR of the HDD or partition ( MBR:
Short for Master Boot Record, a small program that is executed when a computer boots up. Typically, the MBR resides on the first sector of the hard disk. The program begins the boot process by looking up the partition table to determine which partition to use for booting. It then transfers program control to the boot sector of that partition, which continues the boot process. In DOS and Windows systems, you can create the MBR with the FDISK /MBR command )

Bootcfg add,delete the records in the boot.ini file that exist in the boot partition where ntldr is.

Now from all the above there no emediate connection between those three commands.
Just an logical order will be :
1. Fixmbr
2. Fixboot
3. Bootcfg
But this order, you can change it without creating any problems.

Babs,
hope this helps.
0
 
CaptainPickardAuthor Commented:
None of the Fixboot, Fixmbr, and BOOTCFG/rebuild commands work when you boot up from a ME startup disk. I'm surprised nobody has caught that. My findings seem to point out they only work from a recovery environment; an environment I can't access.

Safe Mode hangs at same spot, with last command line pausing at Mup.sys
I did some research on this "Mup error" the causes associated with it number like the stars in the sky. I'm thinking I'm just gonna have to suck it up and buy an HP recovery CD

Got BartPE up & running in its own environment. Now what?!
0
 
mrenosCommented:
Then you should rephrase your question's title : Can i repair windows xp with a ME boot disk ?

From BartPE you can reset the administrator password of the desirable windows installation in order the Recovery console can login.

Also, in the recovery console do you get 2 options in order to select the desirable windows installation that you wan to logon or you just get 1?
If you get only one and you are sure that there is no password set, just press enter in the password area when needed.

Babs,
Hope this helps...
0
 
FriarTukCommented:
"None of the Fixboot, Fixmbr, and BOOTCFG/rebuild commands work when you boot up from a ME startup disk. I'm surprised nobody has caught that. "

that's why i asked if you referring the xp recovery console which you access by booting from the xp cd
0
 
CaptainPickardAuthor Commented:
How do I create an administrative pwd in BartPE? I'm booted into the BPE environment but see any provisions for accessing User Accounts...
0
 
mrenosCommented:
Download Windows Ultimate Boot CD Version 2.6  from http://www.ubcd4win.com/downloads.htm
Locate the password tools from http://www.ubcd4win.com/contents.htm where you can see the Sala Password Renew Update wich will do what you want.


Babs,
Hope this helps..
0
 
CaptainPickardAuthor Commented:
Thanks to all!
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 3
  • 3
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now