...what methods have you used to successfuly resurrect an XP system that just won't boot at all? with the autoexec and config files no longer there in general, it seems the choices are much more limited.
You can't boot into Safe Mode? That normally doesn't run either of those files, but loads an emergency libary. You can even boot into Safe Mode with networking.
1. Restart the computer. Some computers have a progress bar that refers to the word BIOS. Others may not let you know what is happening. 2. As soon as the BIOS loads, begin tapping the F8 key on your keyboard. Do so until the Windows Advanced Options menu appears. If you begin tapping the F8 key too soon, some computers display a "keyboard error" message. If this happens, restart the computer and try again. 3. Using the arrow keys on the keyboard, select Safe mode (or Safe Mode with Networking) and then press Enter.
thanks critter... went thru alla them standards awreddy though... *peep* the F8 method just cycles back and forth, requesting the drive be repaired by typing "r", and cycles this way endlessly. will not boot off CD. rescue disk would not fix it. F12 test would not fix it.
i'm pretty much just curious if i did everything possible at all. :/
incidentally, an install-over (in a separate directory) was able to get it going again and save all files, but the apps which require user-specific rights won't work of course. *fluffs feathers*
What about signing on as global administrator and changing the rights of those files directly? It's very time consuming, I know, but it would allow those files to be saved. Same with the apps that require the user-specific rights. Change their rights as admin, and they'll probably run again. (I had to do this once).
I've been using SpinRite since v1.0 was released a decade and a half ago.
My standard Oh Sh-one-t! Windows Repair Kit contains:
SpinRite 6.0 (If this can't recover data of a corrupted hard disk, then it's time for the big dollar professionals)
MemTest86 3.1a (You never know, it might be faulty memory that manages to pass the BIOS boot tests)
Ghost 2003 (If the disk is readable but not bootable, Ghost will let me capture all the data to another HDD, or a series of CDRs or DVDRs. Once I have a snapshot of the problem disk, I know that I can attack the original disk with gusto and if I really screw things up, I can reloaad the Ghost image. Plus I can use GhostExplorer on another Windows computer to extract all the files and data from the ghost image files.)
Offline password editors (These are bootable CDs that contain software to allow me to edit lost Windows Admin or User passwords. Have a look here for information.)
indeedy good sir..thanks! *chyrp* ..... funny you should mention that... in fact their other computer was indeed hung up with a hardware anomaly.... he changed the cpu fan and made too much of a mess with the contact grease, causing some intermittent shorting... so after I cleaned that up, it cured that ailment.. :>
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2005-05-25 12:23 pm (UTC)1. Restart the computer. Some computers have a progress bar that refers to the word BIOS. Others may not let you know what is happening.
2. As soon as the BIOS loads, begin tapping the F8 key on your keyboard. Do so until the Windows Advanced Options menu appears. If you begin tapping the F8 key too soon, some computers display a "keyboard error" message. If this happens, restart the computer and try again.
3. Using the arrow keys on the keyboard, select Safe mode (or Safe Mode with Networking) and then press Enter.
no subject
Date: 2005-05-25 01:34 pm (UTC)the F8 method just cycles back and forth, requesting the drive be repaired by typing "r", and cycles this way endlessly.
will not boot off CD.
rescue disk would not fix it.
F12 test would not fix it.
i'm pretty much just curious if i did everything possible at all. :/
incidentally, an install-over (in a separate directory) was able to get it going again and save all files, but the apps which require user-specific rights won't work of course.
*fluffs feathers*
no subject
Date: 2005-05-25 01:45 pm (UTC)wow... sounds very intriguing... *wags tail*
Date: 2005-05-26 08:47 am (UTC)If you recall a basic step-by-step for this, I'd love ta peek... ^v^
Re: wow... sounds very intriguing... *wags tail*
Date: 2005-05-26 07:08 pm (UTC)no subject
Date: 2005-05-25 01:15 pm (UTC)*clamps his beak shut with his hand*
Pax,
Hali
--
http://www.avians.net/hali
http://www.matthewebel.com
no subject
Date: 2005-05-25 01:35 pm (UTC)no subject
Date: 2005-05-25 01:35 pm (UTC)no subject
Date: 2005-05-25 01:42 pm (UTC)Oh good, I didn't need to proselytize yet again. My work here is done...
Pax,
Hali
--
http://www.avians.net/hali
http://www.matthewebel.com
Rubber Chicken and SpinRite 6
Date: 2005-05-25 05:12 pm (UTC)Re: Rubber Chicken and SpinRite 6
Date: 2005-05-26 08:49 am (UTC)I've heard of this thing... mebbe it's time to add it to my resource kit...
*wags* ... thanks woof!
Re: Rubber Chicken and SpinRite 6
Date: 2005-05-26 10:15 am (UTC)My standard Oh Sh-one-t! Windows Repair Kit contains:
SpinRite 6.0 (If this can't recover data of a corrupted hard disk, then it's time for the big dollar professionals)
MemTest86 3.1a (You never know, it might be faulty memory that manages to pass the BIOS boot tests)
Ghost 2003 (If the disk is readable but not bootable, Ghost will let me capture all the data to another HDD, or a series of CDRs or DVDRs. Once I have a snapshot of the problem disk, I know that I can attack the original disk with gusto and if I really screw things up, I can reloaad the Ghost image. Plus I can use GhostExplorer on another Windows computer to extract all the files and data from the ghost image files.)
Offline password editors (These are bootable CDs that contain software to allow me to edit lost Windows Admin or User passwords. Have a look here for information.)
no subject
Date: 2005-05-26 08:52 am (UTC)funny you should mention that... in fact their other computer was indeed hung up with a hardware anomaly.... he changed the cpu fan and made too much of a mess with the contact grease, causing some intermittent shorting... so after I cleaned that up, it cured that ailment.. :>