Anatomy of a hang

[tw]

Originally Posted by Undertoad

Now then, when you say "use XCOPY", where should I use it from? I was previuosly aware of XCOPY, having used it since Win 3.1 actually -- but it's not available in the Windows Recovery Console.

XCOPY copies essential information such as registry, your data, and system files. Then make that drive the C: drive; boot from the CD-Rom, and do a disk repair. Many variations may be offered. Generally avoid fixing the registry, no reason to fix system files, but repair the system boot.

This repair will build a boot sector that is unique for the hard drive hardware and NTFS unique parameters. It should correct BOOT.INI, NTLDR file and boot sector so that system can boot when system is repowered - a cold boot.

BTW, before moving that slave (D: ) drive to become a master (C: ) drive, use Disk Management program to confirm that first partition of slave drive is marked active. One of those little overlook problems that sometimes takes hours to discover -been there and don't like to talk about it.

Also before doing that disk change, read the Help information on Recovery Console (one way to get to Recovery Console is to press R when Windows welcome screen appears), 'fixboot' program, 'bootcfg' program, 'chkdsk x: /f' program, and 'diskpart' progam.

I don’t remember if ‘bootvrfy’ is an XP program or was only found in NT.

Executing the 'attrib' command while in the root directory of that newly copied drive (enter 'attrib *.*' or 'attrib /?'), temporarily remove hidden and/or system attributes from boot.ini to edit that file using Notepad or some other text editor. Then use 'attrib boot.ini' to reset those attributes. That is one way to correct the boot.ini file besides using Bootcfg program.

Provided are two ways to setup the boot files for the new disk - one while it is still a D: drive or the other from booting and using the CD-ROM while new drive is a now a master drive. I have not used the 'fixboot' program so I cannot suggest 'surprises'. It sounds like it works on the boot sector like 'SYS x:' did in DOS. Provided is a long list of options for making that new drive bootable.

Using the 'ATTRIB *.*' program or using 'DIR *.* /AS' or 'DIR *.* /AH' in the root directory should confirm new or useful versions of the files Boot.ini, NTLDR, and NTDETECT.COM all in the root directory of the first (and marked active) partition. Summary of what will happen: Bootsector finds NTLDR which in turn loads and executes NTDETECT.COM

Those trying to follow this should remember one fact. If the manufacturer did not provide a CD-Rom for each of any Windows NT (also called 2000 or XP), AND that Windows code number, well, appreciate why his cost controlling would have screwed you when problems happen.

Once you get that system up and running, goto www.windowsupdate.com to finish reconstruction of that new disk.