HELP! Reboot Loop in XP During Normal Boot and Function Selections

[GNM]

I have a system that during boot goes directly to the menu screen that
appears to be the same as if you were to select the F8/F5 during boot. No
matter what selection is chosen the system will automatically reboot and
return to the same menu screen. I have allowed the ticker to count down and
reboot on its own and still the same outcome of being returned to the menu
screen. When I select Safe Mode, Last Known..., etc... the OS just continues
to reboot in the same manner. So basically no matter what function in the
menu has been opt, the system consistantly Loop-Boots back to the same menu
screen. I am seeking a fix for this that does not involve wiping the HDD and
re-installing the OS?

Thank You

 

[Pegasus \(MVP\)]

I have a system that during boot goes directly to the menu screen that
appears to be the same as if you were to select the F8/F5 during boot. No
matter what selection is chosen the system will automatically reboot and
return to the same menu screen. I have allowed the ticker to count down
and
reboot on its own and still the same outcome of being returned to the menu
screen. When I select Safe Mode, Last Known..., etc... the OS just
continues
to reboot in the same manner. So basically no matter what function in the
menu has been opt, the system consistantly Loop-Boots back to the same
menu
screen. I am seeking a fix for this that does not involve wiping the HDD
and
re-installing the OS?

Thank You

Normally you would use System Restore in such cases in order to
undo the damage that something did to your machine. Since you
cannot get into Windows, you cannot use System Restore directly.
However, you can use it through the Recovery Console - see here:
http://support.microsoft.com/kb/307545. Note that this is a complex
process. If you're inexperienced in such matters then you should
ask a more experienced friend to assist you.

 

[db ´¯`·.. >]

you might try to
log into the file
system via the
recovery console
with your win cd:

http://support.microsoft.com/kb/314058


then at the prompt>
you can run:

bootcfg /rebuild

fixboot

fixmbr

and a while you are there, a:

chkdsk

http://support.microsoft.com/kb/314058


--

<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>

..

 

[Pegasus \(MVP\)]

you might try to
log into the file
system via the
recovery console
with your win cd:

http://support.microsoft.com/kb/314058


then at the prompt>
you can run:

bootcfg /rebuild

fixboot

fixmbr

and a while you are there, a:

chkdsk

To use chkdsk without first backing up all important
files is a dangerous thing: It can cause massive data loss.

 

[db ´¯`·.. >]

allot of things
can cause massive
data loss but chkdsk
was not designed by microsoft
to corrupt information.

if it were, microsoft would
be out of business.

what/where is the foundation
of this concern with chkdsk?


--

<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>

..

 

[Pegasus \(MVP\)]

allot of things
can cause massive
data loss but chkdsk
was not designed by microsoft
to corrupt information.

if it were, microsoft would
be out of business.

what/where is the foundation
of this concern with chkdsk?

I think it is generally accepted that chkdsk is a dangerous
program to run. It will certainly eliminate errors in the filing
system but in doing so it may convert partly or wholly readable
files/folders into unuseable blocks of 65 kBytes of date. The
general rule, which holds for other repair programs too, is:

1. Salvage what you can salvage.
2. Repair what you can repair.

Note the order!
And just because Microsoft designed it does not necessarily
mean that it's the best thing since sliced bread!

 

[db ´¯`·.. >]

i can understand
your premise, however it
is not one that i share or
support.

my position is that i will
rely upon microsoft as
the primary source of
information for its
operating system.

all else is second hand
information and food
for thought.

however, if by chance a user
incurred a massive loss of information
then it was likely due to a physical
problem with the hard drive.

reasonably check disk would be
used in an attempt to corect the
incoherent disk activities, but futile
on a failing harddrive.

so in these cases chdsk would
become the scapegoat.

--

<)))º>·´¯`·.¸. , . .·´¯`·.. ><)))º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><)))º>

..

 

[GNM]

I thank you both for your in depth analysis in regaurds to my issue as I have
taken both options and put them into play in resolving the issues I faced and
came out with a system that I was able to gain what it was I set to
accomplish and that wasnot having to redo the HDD simply because I knew there
was a problem with the registry and the fix although intense was party to the
repairs as was the chkdsk format in which I use quit often and has proven to
accomodate me w/repairs more than none.

The only draw back of the 307545 was that it did not enable me to gain
access as it states of the actual recovery date I needed as I believe this to
be due to the astronomical amout of unallocated files placed within the HDD's
OS.

Again I thank you both for your input in helping me resolve this matter as
it was very helpful.

Thank you and Happy Holidays!