unable to boot into xp

[Guest]

XP was running a little slow for me for the past couple months ever since i
copied and replaced my boot drive. I thought it might have been because some
system files were not copied properly so I decided to run the XP setup cd
from windows and perform the upgrade option in order to reinstall any files
that may have become corrupt in the drive copy process. During the upgrade,
setup gave me a warning about one of my drivers not passing windows logo
testing and advised against installing it. Since all drivers had been
working fine before i told it to install them anyway but when it was done
installing XP it would no longer boot. It now only gets past the bios
display and right before the windows xp logo would normally come up, a BSoD
flashes (too fast for me to read the stop error) and then the computer
restarts. I know that the XP cd should give me the option to automatically
repair a copy of windows installed on the system when i boot to the cd and
get past the EULA but it doesnt. I have another drive on this computer
running Vista RC1 so i am able to edit files on the drive that contains the
corrupt XP installation. I really dont want to have to reformat the drive
because it is a major hassle. Does anyone know if there is a way to fix this
problem by editing or deleting files from corrupt windows installation? Will
the auto repair option come up when i boot to the XP cd if i delete some
important windows files (maybe the setup will recognize that it is damaged
then)?

 

[Brian A]

Will XP boot to Safe Mode?
Since both XP and Vista were installed and you then ran an XP upgrade, you may want
to have a look at the boot.ini to make sure the OS's are configured properly for
boot.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Guest]

No, XP will not boot to safe mode either. I have already looked at boot.ini
and it is fine. Visa and XP are not on the same drive. I used the repair
console from the boot cd to fixboot and fixmbr. I also ran chkdsk and found
no errors.

 

[John John]

From the Vista installation you can change the reboot on crash
behaviour so that the computer will stop with a BSOD or bugcheck error
message instead of going into a reboot, you might then be able to get
useful information to help you resolve the problem. You will have to
edit the Windows XP registry from the Vista installation, the
instructions here are culled from the article below, but we will use
Regedit (instead of Regedt32). Windows versions prior to XP cannot load
registry hives with Regedit, that is why the article instructs you to
use Regedt32. Only do the steps below, the other steps in the article
are not necessary.

1. Run Regedit.exe from the Vista installation, and then go to the
HKEY_LOCAL_MACHINE key.

2. On the Registry menu, click Load Hive, and then open the System file
in the original Windows XP installation location. By default, this
installation is located at %SystemRoot%\System32\Config\System.

3. Enter an arbitrary name when you receive a prompt for a key name in
the Load Hive window. This loads the original HKEY_LOCAL_MACHINE hive as
a subkey of the current key.

4. Change the value data in the AutoReboot value to 0 (zero), instead of
1, in the following key:

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl

5. Collapse the HKEY_LOCAL_MACHINE subkey and unload the hive.

This disables the Automatically Reboot option in the original Windows
installation. After you follow these steps, you may be able to gather
information from the STOP error message and resolve the problem that
prevents the computer from starting.

Windows Restarts Continuously with Blue Screen
http://support.microsoft.com/kb/174630/EN-US/

This will help you better understand the instructions:
http://www.rwin.ch/xp-live/regedit.htm

John

 

[Guest]

Ok I followed those instructions and I was able to write down the error.
Stop: 0x0000007B (0xF79F6524, 0xC0000034, 0x00000000, 0x00000000)

 

[Brian A]

I'm sure this was a mistype on your part.
<quote>
Windows versions prior to XP cannot load registry hives with Regedit, that is why
the article instructs you to use Regedt32.
</quote>

Prior versions did use regedit.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[John John]

What's the rest of the error message? We need all of it. The error
almost invariably means that Window can't talk (communicate) with the
boot drive or boot drive controller. But we need the full text of the
bug check message to confirm that. Is the drive SATA or is it on a RAID
controller by any chance?

John

 

[John John]

Windows NT and Windows 2000 cannot load remote hives using Regedit, with
these earlier NT versions you have to use Regedt32 to perform the
operation. Also, in these earlier versions Regedit cannot do registry
security and permissions and it cannot do certain types of values like
REG_MULTI_SZ REG_EXPAND_Z, these have to be done with Regedt32. Of
course Regedit can load the local hives and it can connect to a network
registry, but it can't do what is shown in the article in question. On
these earlier Windows versions Regedt32 is the real registry editor,
Regedit was thrown in mostly for its search capabilities and value
renaming abilities that Regedt32 doesn't have. With Windows XP onward
the capabilities of Regedt32 were all rolled up and included in the new
Regedit version.

John

 

[Guest]

the only other thing the BSoD said was that "A problem has been detected and
windows has been shut down to prevent damage to your computer." I know that
STOP: 0x0000007B is associated with driver errors and thats what I thought
was causing the problem to begin with. My drive is a 250 GB WDC caviar se 16
SATA. Windows XP worked fine on it before.

 

[John John]

When you did the in-place upgrade quite possibly you needed to press F6
at the very beginning of the setup routine to have Windows load the SATA
or Mass Storage controller drivers. You MUST supply the drivers on
floppy diskette, the setup program will not accept the drivers from any
other media source.

John

 

[Glenn Holliday]

When you did the in-place upgrade quite possibly you needed to press F6
at the very beginning of the setup routine to have Windows load the SATA
or Mass Storage controller drivers. You MUST supply the drivers on
floppy diskette, the setup program will not accept the drivers from any
other media source.

What's the proper procedure for computers that have no floppy drive?

 

[John John]

What's the proper procedure for computers that have no floppy drive?

If the computer can boot to USB devices you might be able to use a USB
floppy drive, if not you will have to fit a floppy diskette drive to the
computer even if only temporarily. That failing you will have to
slipstream/sysprep an image with the controller drivers included in the
deployment.

John

 

[Guest]

Is there a way to make the in place upgrade (automatic recovery) option come
up when i boot onto the xp cd? (destroying critical registry values maybe?)
if there is no way to do that I plan on just waiting until vista RTM comes
out for msdnaa and upgrade XP to that.

 

[John John]

Automated System Recovery (ASR) and In-Place Upgrade are two completely
different things. Did you previously prepare an ASR diskette? To
launch ASR press F2 when prompted during the text mode setup part. Be
warned that ASR does not backup data files and that the restore process
will format the systemdrive partition, if you have any files you want to
keep on that partition salvage them before you do an ASR restoration.

John

 

[Brian A]

Thankyou for the additional information in that it is Remote Hives and not simply
previous versions when using regedit.

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[Guest]

I did not say ASR. A notice to perform that comes up before setup is even
loaded. I was talking about after pressing enter to set up windows xp and
pressing f8 to agree to the EULA if there is a damaged version of windows
found it will ask if you want it to automatically repair the selected
installation. When I boot onto the xp cd though, it doesnt give me this
option. It goes straight to showing me the list of xp installations and
partitions available with no option to automatically repair a damaged
installation. What I want to know is if there is a way to make setup
recognize that my xp installation is damaged so it will give me that option.

 

[Brian A]

See here:
http://www.michaelstevenstech.com/XPrepairinstall.htm

--

Brian A. Sesko { MS MVP_Shell/User }
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375

 

[John John]

I don't quite understand your question. One of your cd's is probably a
Windows XP cd while the other must be an OEM/Recovery cd. You can
select from whichever options are offered with the cd that you boot but
you cannot add to them or change them.

John

 

[Guest]

http://www.techspot.com/vb/topic8356.html
This website shows what I want to be able to do when I boot to my windows xp
cd (by the way, my cd is a .iso file from msdnaa which I then burned to a
cd. It is xp pro with SP2 included). But when I boot to my cd, that option
for setup to repair an installation of windows xp does not show up. After I
hit f8 to agree to the EULA it goes straight to a screen asking me where i
would like to set up windows and lists all available drives. I have used
this upgrade option on the xp cd before but for some reason it will not let
me do it for this installation.
I am trying to figure out if this option only comes up if setup recognizes
that there is a problem with a version of windows installed on the computer
and, if so, is there a way to damage windows just enough to make setup
realize that windows needs repair?

And Brian-
I went through those steps on michealstevenstech.com with no luck. Thanks
anyway for posting it I am willing to try anything except reformatting.

 

[John John]

I think that we are going around in circle. Press F6 at the beginning
of the setup routine and feed it the SATA drivers on a diskette. SP2
should be able to recognize SATA but it doesn't recognize them all. The
SATA drivers should be on your motherboard driver cd or supplied with
your controller card. If that is not the case then then boot to the
recovery console and run these commands on the drive:

chkdsk /r
fixboot

John