XP reboots continuously & won't allow me to repair it.

I already got that article for removing XP Service Pack 2....I thought about trying it, but I didn't want to waste my time if I wasn't sure it was installed in the first place.

I also found the first article but do not think it applies as I can access the XP installation through RC.  I will see what happens.

sounds like there's a part of your registry that is missing or hosed

I think the repair function relies on certain registry files and if the setup environment can't find or read part of the registry, it can fail in weird ways.

if you can have a back up of the registry files,  boot from the cd and go into the RC   and rename the originals, and replace them with copies of the backups.

if the links above are accurate, you don't have much to lose,..


Tanelorn  

SheharyaarSaahil, you're killing me.  Parallel installs take forever.  :)  I thought about that one too, and am still considering it.

I did make an observation in the recovery console though.  When I list the directories, I can see that there is an:

$ntuninstallKB825119

directory listed and that it installed that patch on 9/30.  Now, she said she shut down at the end of the day yesterday and boot up this morning and that the reboot cycle was what was occuring.

But looking up the KB article for that patch shows a buffer overrun problem...seems fairly routine.  The article is http://support.microsoft.com/default.aspx?scid=kb;en-us;825119.  I can't imagine why such a mundane update can cause these types of problems so I am unsure if it is related.

I guess I can check and see if there is an uninstall option for that KB fix in that directory....

Interesting idea FE.  I tried to run it from the Recovery Console, but that of course didn't work.  I might try that idea.  I've never run System Restore from a NTFSDOS reader disk.

Hey FE.  That NTFSDOS Reader, won't let me execute the file.  I can open it and lok at the contents, but there is no option to execute.  Am I missing something?

I can copy it too...but copy it to where, I don't know.  It's too large for the A drive....

the free one is a reader only,

no writing.   :)

I wasn't writing....I was tryng to execute.  And I did get t he option of copying, but the file was too large for a floppy disk.

Yea...  you must purchase the full version to be able to execute..  I forgot to mention it, and am sorry.

What you could do, however, is create a bootable CDrom disk with an OS on it.  I highly recommend using BartsPE for this.  Although the instructions look a little tough, it is extremely easy to build and create.  With this, you can access the NTFS partition and fix most anything that you find there.

http://www.nu2.nu/pebuilder/

Fatal_Exception

BartPE rocks!!

I just built a couple of cdroms yesterday,  

if he runs the restore point utility,  will it try to fix the os that's loaded in memory?   or can you point it at a system directory on the hard disk and say   "fix it".  

I have to plead ignorant on this one.  ifyou can point it at the windows directory and fix it,  that would be a tremendous tool !!!

If this is the case, I can see myself scheduling restore points in my environment,  say, weekly.  if a machine gets hosed... boot bart run a bat file compiled in, and viola....  my job gets extremely easy...

very impotous

Tanelorn

Tan...  I would have to test that theory, as it may not work since Barts runs in its own environment.  Unfortunately, I will be out of town this weekend and not be able to ck it out till Monday.  But if you can use the Command Shell in Barts to access the System Restore file (using the above command structure) I see no reason it would not execute and run the Restore.

And, I agree.  Barts is the one utility that any tech worth their weight will carry with them at all times.  What sometimes will take hours, and ultimately a reinstall, only takes minutes if you can access the hard drive (other than taking it out and slaving it to another system...)

FE

Hi,

you can run cmd.exe on top of a real windows xp environment.
 I would liken it to a parallel install...  only its on a cdrom.  

I don't know if that gives you any hints,
Q.  will the command line restore work with a parallel install?
        if you can run it booting from a floppy, like one of the previous posts implies,
        it should...   and I'm excited about what it might mean.

T

Another thing you can do to get to the Command Shell is to replace the AutoScreen Saver (that comes up if at the logon screen after several minutes) with the command shell itself.  Then when you boot to the logon screen and wait a bit, you will have total access to the system using System Rights, which of course are higher than even Admin Rights...  I got this tip from Pete Long (who most of you already know) and have outlined it on  my website.  It was meant as an alternative to LophtCrack for restoring an Admin Password, but I should think it would also work here, as long as you can get to the Logon Screen...

Check it out if you like in the W XP section entitled Lost the Admin Password:

www.doverproductions.com

Also, anyone looking for a neat Network Troubleshooting Flowchart should take a look at the Networking Section and view the Netowrk Connection Troubleshooting flowchart I put up last week.

FE

Well gents....I had limited time to fix the problem and I have a policy for production machines that if I cannot fix it in half a day, it's not worth the trouble....so I re-ghosted it and now it's fine.  In any event...I'll distribute the points.

FE...I use Bart's Corporate modboot religiously, but I've never tried the PE yet.  I might have to make one and play with it.  I'll keep the idea in mind for the future.

Thanks for all the suggestions guys.

Good policy, and one which I also adhere to religiously...  :)

And thanks..

FE