Theoretically.....

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

A reply to a recent post ["Computer will not start up"- by COOKIE]
about the Error Message: "Windows XP could not start because the following
file is missing or
corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
"Computer will not start up"- by COOKIE (This Forum)
suggested that without an XP CDrom, a repair could not be made.
Although the OP's situation suggests HDD trouble, I would like to know if
the following steps would work.
(If it wasn't for the damaged drive, and license issues aside.)[And in the
case of a desktop computer situation]

I use NTFS, for this example.

1) Using a working Single-boot desktop computer, {(A), for this example,}
enter into BIOS of (A).
2) Enter Standard CMOS Setup.
3)Presuming (A) is using Primary Master for it's drive, set Primary Slave
to Not Installed.
4)Press F10 (or the appropriate function key for that system) to Save
Changes and Exit. Enter. Turn off computer (A).
5)Set jumper on corrupt drive, (B) for this example, to Slave.
6)Presuming (B) has already been removed from it's computer, install (B)
into (A) in the slave position.
7)Start (A), in Safe Mode. Use Explorer to go to root of (B) drive.
8)Right-click System Volume Information Folder. Security Tab, Add, enter
username of (a)'s computer. OK.
9)Open folder. In the folder marked Restore{long-series-of-num-bers} , use
View>Detail to find a recent RP folder and open. Open Snapshot folder.
10)Copy these files to a New Folder

• _REGISTRY_USER_.DEFAULT • _REGISTRY_MACHINE_SECURITY •
_REGISTRY_MACHINE_SOFTWARE • _REGISTRY_MACHINE_SYSTEM • _REGISTRY_MACHINE_SAM
[ Don't worry that they may say "Copy of" for now. Save folder.]
11)Go to (B)'s \WINDOWS\SYSTEM32\CONFIG\
Rename files default,SAM,SECURITY,software, and system to
default.bak,SAM.bak,SECURITY.bak,software.bak, and system.bak.
Move them into Windows\Temp folder
12)Rename the files in New Folder (see 10) to default, SAM, SECURITY,
software, and system.
13)Move them to (B)'s \WINDOWS\SYSTEM32\CONFIG\

14)Move jumper on (B) back to CS or Master. Put (B) back into computer
"B". Reset (A)'s BIOS.
15)Start Windows on "B".

Information I used came from here: http://support.microsoft.com/kb/309531/
and here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545

What Think Ye ?
 
|> A reply to a recent post ["Computer will not start up"- by COOKIE]
|>about the Error Message: "Windows XP could not start because the following
|>file is missing or
|> corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
|>"Computer will not start up"- by COOKIE (This Forum)
|>suggested that without an XP CDrom, a repair could not be made.
|> Although the OP's situation suggests HDD trouble, I would like to know if
|>the following steps would work.

<confusion snipped>

COOKIE should of been using ERUNT
http://www.larshederer.homepage.t-online.de/erunt/

Then COOKIE could download and create a Win98 boot disk
http://bootdisk.com/bootdisk.htm with ntfs4dos installed
http://www.datapol.de/dpe/freeware/ boot up;
Then run ERUNT to repair the registry.
 
|>|> A reply to a recent post ["Computer will not start up"- by COOKIE]
|>|>about the Error Message: "Windows XP could not start because the following
|>|>file is missing or
|>|> corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
|>|>"Computer will not start up"- by COOKIE (This Forum)
|>|>suggested that without an XP CDrom, a repair could not be made.
|>|> Although the OP's situation suggests HDD trouble, I would like to know if
|>|>the following steps would work.
|>
|><confusion snipped>

|>COOKIE should of been using ERUNT
|>http://www.larshederer.homepage.t-online.de/erunt/

Never mind, I just deleted that last message - see if actually happens
:)

ERUNT doesn't run under Win98 ( I just tried it). Blows my plans on
recovery.
 
Trax said:
Trax said:
A reply to a recent post ["Computer will not start up"- by COOKIE]
about the Error Message: "Windows XP could not start because the
following file is missing or
corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
"Computer will not start up"- by COOKIE (This Forum)
suggested that without an XP CDrom, a repair could not be made.
Although the OP's situation suggests HDD trouble, I would like to
know if the following steps would work.

<confusion snipped>
COOKIE should of been using ERUNT
http://www.larshederer.homepage.t-online.de/erunt/
Click to expand...
Click to expand...

Never mind, I just deleted that last message - see if actually happens
:)

ERUNT doesn't run under Win98 ( I just tried it). Blows my plans on
recovery.
Click to expand...

ERUNT doesn't have to run under Win98--the issue would be ERDNT. But
that's beside the point. If ERUNT had been used prior to the mishap, a
restore could be done in the PE environment (e.g. with BartPE), or using
the Windows Recovery Console.

I didn't read the original thread, but going by the error message shown
above, my guess is that, in lieu of a backup, a "last known good"
attempt is in order, and failing that, a repair install is the answer.
 
|> A reply to a recent post ["Computer will not start up"- by COOKIE]
|>about the Error Message: "Windows XP could not start because the following
|>file is missing or
|> corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
|>"Computer will not start up"- by COOKIE (This Forum)
|>suggested that without an XP CDrom, a repair could not be made.
|> Although the OP's situation suggests HDD trouble, I would like to know if
|>the following steps would work.
|> (If it wasn't for the damaged drive, and license issues aside.)[And in the
|>case of a desktop computer situation]
|>
|> I use NTFS, for this example.
|>
|> 1) Using a working Single-boot desktop computer, {(A), for this example,}
|>enter into BIOS of (A).
|> 2) Enter Standard CMOS Setup.
|> 3)Presuming (A) is using Primary Master for it's drive, set Primary Slave
|>to Not Installed.
|> 4)Press F10 (or the appropriate function key for that system) to Save
|>Changes and Exit. Enter. Turn off computer (A).
|> 5)Set jumper on corrupt drive, (B) for this example, to Slave.
|> 6)Presuming (B) has already been removed from it's computer, install (B)
|>into (A) in the slave position.
|> 7)Start (A), in Safe Mode. Use Explorer to go to root of (B) drive.
|> 8)Right-click System Volume Information Folder. Security Tab, Add, enter
|>username of (a)'s computer. OK.
|> 9)Open folder. In the folder marked Restore{long-series-of-num-bers} , use
|>View>Detail to find a recent RP folder and open. Open Snapshot folder.
|> 10)Copy these files to a New Folder
|>
|>• _REGISTRY_USER_.DEFAULT • _REGISTRY_MACHINE_SECURITY •
|>_REGISTRY_MACHINE_SOFTWARE • _REGISTRY_MACHINE_SYSTEM • _REGISTRY_MACHINE_SAM
|> [ Don't worry that they may say "Copy of" for now. Save folder.]
|> 11)Go to (B)'s \WINDOWS\SYSTEM32\CONFIG\
|> Rename files default,SAM,SECURITY,software, and system to
|>default.bak,SAM.bak,SECURITY.bak,software.bak, and system.bak.
|> Move them into Windows\Temp folder
|> 12)Rename the files in New Folder (see 10) to default, SAM, SECURITY,
|>software, and system.
|> 13)Move them to (B)'s \WINDOWS\SYSTEM32\CONFIG\
|>
|> 14)Move jumper on (B) back to CS or Master. Put (B) back into computer
|>"B". Reset (A)'s BIOS.
|> 15)Start Windows on "B".
|>
|>Information I used came from here: http://support.microsoft.com/kb/309531/
|> and here:
|>http://support.microsoft.com/default.aspx?scid=kb;en-us;307545
|>
|> What Think Ye ?
|>

If you manage to access the hard drive it would be easier to copy
WINDOWS\repair to WINDOWS\system32\config

If the registry was back'd up recently to WINDOWS\repair - a function
of the Backup Utility (system state Data), not much would be lost.
 
1st MS article says Repair files are original Setup files.
Couldn't find "Easy way", checking on "Workable" way.

Trax said:
|> A reply to a recent post ["Computer will not start up"- by COOKIE]
|>about the Error Message: "Windows XP could not start because the following
|>file is missing or
|> corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
|>"Computer will not start up"- by COOKIE (This Forum)
|>suggested that without an XP CDrom, a repair could not be made.
|> Although the OP's situation suggests HDD trouble, I would like to know if
|>the following steps would work.
|> (If it wasn't for the damaged drive, and license issues aside.)[And in the
|>case of a desktop computer situation]
|>
|> I use NTFS, for this example.
|>
|> 1) Using a working Single-boot desktop computer, {(A), for this example,}
|>enter into BIOS of (A).
|> 2) Enter Standard CMOS Setup.
|> 3)Presuming (A) is using Primary Master for it's drive, set Primary Slave
|>to Not Installed.
|> 4)Press F10 (or the appropriate function key for that system) to Save
|>Changes and Exit. Enter. Turn off computer (A).
|> 5)Set jumper on corrupt drive, (B) for this example, to Slave.
|> 6)Presuming (B) has already been removed from it's computer, install (B)
|>into (A) in the slave position.
|> 7)Start (A), in Safe Mode. Use Explorer to go to root of (B) drive.
|> 8)Right-click System Volume Information Folder. Security Tab, Add, enter
|>username of (a)'s computer. OK.
|> 9)Open folder. In the folder marked Restore{long-series-of-num-bers} , use
|>View>Detail to find a recent RP folder and open. Open Snapshot folder.
|> 10)Copy these files to a New Folder
|>
|>• _REGISTRY_USER_.DEFAULT • _REGISTRY_MACHINE_SECURITY •
|>_REGISTRY_MACHINE_SOFTWARE • _REGISTRY_MACHINE_SYSTEM • _REGISTRY_MACHINE_SAM
|> [ Don't worry that they may say "Copy of" for now. Save folder.]
|> 11)Go to (B)'s \WINDOWS\SYSTEM32\CONFIG\
|> Rename files default,SAM,SECURITY,software, and system to
|>default.bak,SAM.bak,SECURITY.bak,software.bak, and system.bak.
|> Move them into Windows\Temp folder
|> 12)Rename the files in New Folder (see 10) to default, SAM, SECURITY,
|>software, and system.
|> 13)Move them to (B)'s \WINDOWS\SYSTEM32\CONFIG\
|>
|> 14)Move jumper on (B) back to CS or Master. Put (B) back into computer
|>"B". Reset (A)'s BIOS.
|> 15)Start Windows on "B".
|>
|>Information I used came from here: http://support.microsoft.com/kb/309531/
|> and here:
|>http://support.microsoft.com/default.aspx?scid=kb;en-us;307545
|>
|> What Think Ye ?
|>

If you manage to access the hard drive it would be easier to copy
WINDOWS\repair to WINDOWS\system32\config

If the registry was back'd up recently to WINDOWS\repair - a function
of the Backup Utility (system state Data), not much would be lost.
Click to expand...
 
|> 1st MS article says Repair files are original Setup files.
|> Couldn't find "Easy way", checking on "Workable" way.

WINDOWS\repair to WINDOWS\system32\config
It's what the XP CD repair function does, but your right if the files
haven't been updated they will be those when first installed.

That's why you need to update the Repair directory.

Trying to make up for a bad post :) but replacing the reg files it's
what I plan for, and seeing as I've never read or heard of anyone else
doing it (updating the repair reg files), I could be the only one...

What I do is run the Backup Utility (RUN ntbackup.exe)
Select Backup wizard (advanced) - Next
Then select "Only back up the system State Data"
Save the backup file someplace, and let it run.

Then I delete the backup - as the purpose was to update the Repair
directory (which it does).

One could just copy the files from the Config to Repair directory but
the backup route actually takes less work; and easier to explain to a
point and click user.


|>>
|>> |> A reply to a recent post ["Computer will not start up"- by COOKIE]
|>> |>about the Error Message: "Windows XP could not start because the following
|>> |>file is missing or
|>> |> corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
|>> |>"Computer will not start up"- by COOKIE (This Forum)
|>> |>suggested that without an XP CDrom, a repair could not be made.
|>> |> Although the OP's situation suggests HDD trouble, I would like to know if
|>> |>the following steps would work.
|>> |> (If it wasn't for the damaged drive, and license issues aside.)[And in the
|>> |>case of a desktop computer situation]
|>> |>
|>> |> I use NTFS, for this example.
|>> |>
|>> |> 1) Using a working Single-boot desktop computer, {(A), for this example,}
|>> |>enter into BIOS of (A).
|>> |> 2) Enter Standard CMOS Setup.
|>> |> 3)Presuming (A) is using Primary Master for it's drive, set Primary Slave
|>> |>to Not Installed.
|>> |> 4)Press F10 (or the appropriate function key for that system) to Save
|>> |>Changes and Exit. Enter. Turn off computer (A).
|>> |> 5)Set jumper on corrupt drive, (B) for this example, to Slave.
|>> |> 6)Presuming (B) has already been removed from it's computer, install (B)
|>> |>into (A) in the slave position.
|>> |> 7)Start (A), in Safe Mode. Use Explorer to go to root of (B) drive.
|>> |> 8)Right-click System Volume Information Folder. Security Tab, Add, enter
|>> |>username of (a)'s computer. OK.
|>> |> 9)Open folder. In the folder marked Restore{long-series-of-num-bers} , use
|>> |>View>Detail to find a recent RP folder and open. Open Snapshot folder.
|>> |> 10)Copy these files to a New Folder
|>> |>
|>> |>• _REGISTRY_USER_.DEFAULT • _REGISTRY_MACHINE_SECURITY •
|>> |>_REGISTRY_MACHINE_SOFTWARE • _REGISTRY_MACHINE_SYSTEM • _REGISTRY_MACHINE_SAM
|>> |> [ Don't worry that they may say "Copy of" for now. Save folder.]
|>> |> 11)Go to (B)'s \WINDOWS\SYSTEM32\CONFIG\
|>> |> Rename files default,SAM,SECURITY,software, and system to
|>> |>default.bak,SAM.bak,SECURITY.bak,software.bak, and system.bak.
|>> |> Move them into Windows\Temp folder
|>> |> 12)Rename the files in New Folder (see 10) to default, SAM, SECURITY,
|>> |>software, and system.
|>> |> 13)Move them to (B)'s \WINDOWS\SYSTEM32\CONFIG\
|>> |>
|>> |> 14)Move jumper on (B) back to CS or Master. Put (B) back into computer
|>> |>"B". Reset (A)'s BIOS.
|>> |> 15)Start Windows on "B".
|>> |>
|>> |>Information I used came from here: http://support.microsoft.com/kb/309531/
|>> |> and here:
|>> |>http://support.microsoft.com/default.aspx?scid=kb;en-us;307545
|>> |>
|>> |> What Think Ye ?
|>> |>
|>>
|>> If you manage to access the hard drive it would be easier to copy
|>> WINDOWS\repair to WINDOWS\system32\config
|>>
|>> If the registry was back'd up recently to WINDOWS\repair - a function
|>> of the Backup Utility (system state Data), not much would be lost.
|>>
|>>
|>>
|>> --
|>> Take a game break...
|>> http://games.briankass.com/
|>>
 
Trax said:
That's why you need to update the Repair directory.
Click to expand...
What I do is run the Backup Utility (RUN ntbackup.exe)
Select Backup wizard (advanced) - Next
Then select "Only back up the system State Data"
Save the backup file someplace, and let it run.

Then I delete the backup - as the purpose was to update the Repair
directory (which it does).
Click to expand...

Now, THAT"s good Info! I can use that. (But I "stoop" to ERUNT.)

Unfortunately, I'm looking for an answer for where there was no backup,
no non-MS software, possibly OEM install, and no XP CD.

I thought it worth the challenge.
But, am I correct?
 
|> Unfortunately, I'm looking for an answer for where there was no backup,
|> no non-MS software, possibly OEM install, and no XP CD.
|>
|> I thought it worth the challenge.
|> But, am I correct?

If NTFS is involved then there's really no way to access the hard
drive without the XP CD or a third party CD (Ultimate CD) and or
NTFS4DOS.

There in another way to boot up and that's with a USB thumb drive - I
boot up with Win98 that way. Your Computer (BIOS) must be able to do
it tho. - just another option
 
Back
Top