Easy? The jury is still out.....er missing.

#1
I'm seeking to fix my boot files that apparently were corrupted while attempting a repair/install. I've been booting the past three weeks using an NTLDR floppy boot disk I downloaded, that apparently circumvents my boot files.

This EasyBCD app, error'd upon install (shown below) and while it appeared to finish installing, I can't find the directions for use. The downloadable online tutorials appear written for Vista users, or those who want dual operating systems..

I just want my lone install of XP to boot correctly.

Would highly appreciate any help, direction, a copy of the readme?

 

mqudsi

Mostly Harmless
Staff member
#2
EasyBCD is only for dual-booting with Windows Vista or Windows 7 - it isn't meant to be used for individual installs of Windows XP.

But we can still help :smile:

Open C:\Program Files\NeoSmart Technologies\EasyBCD\Profiles

Copy both NTLDR and NTDETECT from there to C:

Open a command prompt, and type in:
Code:
cd "C:\Program Files\NeoSmart Technologies\EasyBCD\bin"
BootGrabber.exe /bootcfg
bootsect.exe /nt52 all /force
bootsect.exe /nt52 /mbr all /force
 
#3
Thanks for the reply Comp Guru!

Theres an "ntdetect.com" file, an "easyldr" file , and one labeled "grldr"

but see no NTLDR file.

I have mine in C:?
 

mqudsi

Mostly Harmless
Staff member
#4
If yours are already in C, you can skip that step.
 
#5
I'm not sure if those were downloaded to replace mine, or if mine were overwritten, but they're jacked up in any case.

Thanks for the thought anyway.

Guess I missed the part about the dual boot specific, entirely.
 

mqudsi

Mostly Harmless
Staff member
#6
No, go ahead and continue with the other steps.
 
#7
Hey Comp Guru!

Granted ,It was a bit unusual, but I assumed you meant "skip the idea entirely".

Glad I checked back!:happy:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Master Blaster>cd C:\Program Files\NeoSmart Technologi
es\EasyBCD\bin
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>BootGrabber.exe /bootcfg
BootGrabber utility.
Copyright NeoSmart Technologies 2009-2010 <http://neosmart.net/>
Unable to get volume information for \\?\Volume{bd5a6f37-e5bd-11de-90b2-806d6172
696f}\
Located active partition on drive 0: \ArcName\multi(0)disk(0)rdisk(0)partition(
1)
Drive 0, Partition 1: Valid Windows 2k/XP/2k3 (Added).
Drive 0, Partition 2: No Windows installation found.
Drive 1, Partition 1: No Windows installation found.
Drive 1, Partition 2: No Windows installation found.
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bootsect.exe /nt52 all /force
Target volumes will be updated with NTLDR compatible bootcode.
C: (\\?\Volume{bd5a6f39-e5bd-11de-90b2-806d6172696f})
Updated NTFS filesystem bootcode. The update may be unreliable since the
volume could not be dismounted during the update:
Access is denied.
E: (\\?\Volume{c51e5944-e6e9-11de-98bb-806d6172696f})
Successfully updated NTFS filesystem bootcode.
F: (\\?\Volume{c51e5945-e6e9-11de-98bb-806d6172696f})
Successfully updated NTFS filesystem bootcode.
G: (\\?\Volume{60538061-f67c-11de-97da-001e90e94f32})
Successfully updated NTFS filesystem bootcode.
Bootcode was successfully updated on all targeted volumes.
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bootsect.exe /nt52 /mbr all /
force
bootsect {/help|/nt60|/nt52} {SYS|ALL|<DriveLetter>:} [/force] [/mbr]
Boot sector restoration tool
Bootsect.exe updates the master boot code for hard disk partitions in order to
switch between BOOTMGR and NTLDR. You can use this tool to restore the boot
sector on your computer.
Run "bootsect /help" for detailed usage instructions.
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>

Not sure what it all means, nor if I'm supposed to close the window yet, but its still open for now.
 

mqudsi

Mostly Harmless
Staff member
#8
oops! That last one was supposed to be

bootsect.exe /nt52 all /mbr /force
 
#9
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>bootsect.exe /nt52 all /mbr /
force
Target volumes will be updated with NTLDR compatible bootcode.
C: (\\?\Volume{bd5a6f39-e5bd-11de-90b2-806d6172696f})
Updated NTFS filesystem bootcode. The update may be unreliable since the
volume could not be dismounted during the update:
Access is denied.
E: (\\?\Volume{c51e5944-e6e9-11de-98bb-806d6172696f})
Successfully updated NTFS filesystem bootcode.
F: (\\?\Volume{c51e5945-e6e9-11de-98bb-806d6172696f})
Successfully updated NTFS filesystem bootcode.
G: (\\?\Volume{60538061-f67c-11de-97da-001e90e94f32})
Successfully updated NTFS filesystem bootcode.
\??\PhysicalDrive0
Successfully updated disk bootcode.
\??\PhysicalDrive1
Successfully updated disk bootcode.
Bootcode was successfully updated on all targeted volumes.
C:\Program Files\NeoSmart Technologies\EasyBCD\bin>


look ok?
 

mqudsi

Mostly Harmless
Staff member
#10
Yeah. If NTLDR and NTDETECT are still in place, then you should be good to go.
 
#11
I hope so,
Heres a quick run down on what happened before I try to restart this without the boot disk.

The machine had originally blue screened, and was stuck in a continuous reboot condition, unable to even boot into safe mode.
I eventually decided on a repair install.
I had changed the boot order of my drives in the BIOS, but in doing so, I mistakenly selected the wrong HD as the 1st boot device.

I never actually ran the install repair, as it requested the Admin user password, which I forgot having even set, but made 3 attempts at a guess anyway.

After the 3rd wrong pw attempt, it denied any more, and rebooted itself.
Thats when I got the first boot.ini error, which eventually changed to a missing NTLDR error.

In a big mess at that point, I stumbled upon the NTLDR boot disc download, and made a floppy boot disc with my backup PC. It allowed me to access Windows virtually problem free.

Once there, I double checked my drives, and realized the one that had my OS on it, wasn't even active in the BIOS.
When I activated it, and swapped them around to the original order, I took out the boot floppy, and it returned to the same blue screen conundrum.
I believe at that point, I swapped them back, and hence, my three week partnership with this boot disc.

Not sure how its gonna boot, but I'm convinced this EasyBSD is one cool tool, and having searched around, no seemed to have a clue how to fix the files.

Thanks Computer Guru, a very fitting title.
 

mqudsi

Mostly Harmless
Staff member
#12
OK, you need to have NTDETECT and NTLDR on the active partition of the first disk in the BIOS boot order.
 
#13
Ok, the only thing is, in disc managment, although my C drive (Disk 0) lists as "System",
my E drive (disk 1) currently states "active".

 
Last edited:

mqudsi

Mostly Harmless
Staff member
#14
Windows is stupid. In disk management, system means active.
 

Terry60

Knows where his towel is.
Staff member
#15
Every different HDD and removable drive, can and usually does have an "active"partition. It just tells the MBR which partition on that drive to look in for the boot files, if you put that drive at the top of the boot priority. If you're not booting from that drive it has no relevance.
Unfortunately XP is a bit lax about displaying flags. Whereas Vista and W7 will display "active" "system" and "boot" explicitly, XP implies one with another, and when something is all three together, just says "system" and assumes you will infer the others.
 
#16
Ok, so each physical drive can have one active? I wasn't sure if there could only be one active of the four primary.
Geez, one OS is confusing enough, TWO are for technical masochists, and innate gurus.

Thanks again, I'll try booting this thing tomorrow night. :x
 

Terry60

Knows where his towel is.
Staff member
#17
Only one of the 4 primary partitions on each HDD can be active.
2 HDDs = 8 primaries, 2 active.
 
#18
Hey guys!

Just wanted to drop by and thank you again for helping get my files straightened out.
Everything booted up clean, without a hitch, and the jury has reached a decision..

..Easy as BCD! :joy:
 

mqudsi

Mostly Harmless
Staff member
#19
Hey, thanks for taking the time to report back.

Glad we could help :smile: