mike said:
I have been getting the Windows could not start because the
following file is missing or corrupt:
Windows/System32/CONFIG/SYSTEM message. I tried the recovery consol
solution- didnt work. Tried the md temp thing- I get a message that
says access denied. I do not get the password question when the
recovery console opens either it just starts. I am using raid 0 on
my machine. I need to get the pics of my daughter off this nutty
computer or else my wife said I am DEAD! Someone please help!!
Bruce said:
How to Recover from a Corrupted Registry that Prevents Windows XP
from Starting
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545
Once you've recovered, you might want to look here, as well:
How to Troubleshoot Registry Corruption Issues
http://support.microsoft.com/default.aspx?scid=kb;en-us;822705
Thanks for giving it a try Bruce but I cant get past the md temp
thing. Windows says access denied.
Between the time you log into the Recovery Console and the time you
try md, type: set AllowAllPaths = true
Hi Blades....The recovery console does not ask me for a
password...it asks for R for recovery... F3 for escape....and Enter
to continue installing windows. I hit R and it goes right to the
C:\ prompt. Then I do the md thing like windows asks and it says
denied. I did what you said and i got The set command is currently
disabled. The SET command is an optional recovery console that can
only be enabled by using the security configuration and analysis
snap-in. Huh??? HELP!
Well, then you're not going to get much use out of the Recovery
Console.
Well, I have two options for you:
1) Install the hard drive from that PC into another PC (say the one
you're using now) as a slave. Then you can fix the install, or just
copy the pictures over and be done with it.
2) Download/Install/Use either a Linux CD-bootable distro with NTFS
support, or BartPE. I prefer BartPE, myself. Both are kind of a
pain to set up, though.
JC_101 said:
For the record, I agree- taking it to another computer is the
easiest thing you can do. install it as a slave (make sure jumpers
are all good) and pull the info (Pics) off of it.
Good luck.
The linux CD's would be of great help as well... and may have to be
your coarse if you don't have another machine. but then.... how
would you be posting here? lol.
John said:
Bad idea, that is a RAID 0 setup you are talking about.
RAID 0 can mean if one drive of the array fails all data gets lost.
Depends on the level of failure, skill of the end-user, etc...
But if it is severe enough - poof goes the data.
Is this a Hardware RAID?
If so - was Windows XP actually installed on the RAID drives?!
(Bad bad things - RAID 0 - just not work risking everything.)
If it wasn't part of the RAID or you can install another drive and install
Windows XP SP2 and the correct drivers - MAYBE you can access the drives -
depending on what has gone wrong.
I suppose 'zero backups' doesn't start to explain it and 'will be buying an
external drive soon and making a backup schedule' is the future...
If it is a hardware RAID - and the hardware configuration shows no issues
with the RAID itself - and you can get a BARTPE with the right drivers for
the card doing the RAID(maybe whether or not you can) - then you may be able
to boot with BartPE and see the data. Might have to take ownership to copy
it to an external drive/network location - but... Better than nothing.
You could also try making an image of the disk (if hardware RAID) with
something like Ghost and using Ghost Viewer to get to the backed up files.
A lot of that depends on questions not asked...
- Hardware RAID 0?
- What does the hardware configuration utility say about the drives?
- No backup system in place *and* were using RAID 0 for system/data storage?
- Does the OP think they can make a BartPE CD?
- Does the OP have access to somehting to back the system up to?
- Does the OP have access to drive imaging software?