regarding the registry error

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

sometimes the system shows this message.
if we try another time booting its gets booting without errors
i want to know why this happens.
which virus can cause this error.

the error we get
the registry cannot loaad the hive(file)
\systemroot\system32\config\software
or its log or alternate
it is corrupt, absent or not writable
begining dump of physical memory
dumping physical memory to disk

 

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

If the software hive is corrupt, it may be possible to rename the software
hive found in;
%windir%\system32\config\software
to software.old
then copy the most recent backup found in
%windir%\repair\regback
as
%windir%\system32\config\software

If that fails you can copy/ use the file
%windir%\repair\software
This file is an image of the hive at the time the OS was installed, so you'd
have to reinstall all software. This being the case you might just as well
blow it away and start a new install. (note: this would at least allow you
to start the OS to make any necessary backups prior to wiping the drive.)

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"sabapathy" wrote:
| sometimes the system shows this message.
| if we try another time booting its gets booting without errors
| i want to know why this happens.
| which virus can cause this error.
|
| the error we get
| the registry cannot loaad the hive(file)
| \systemroot\system32\config\software
| or its log or alternate
| it is corrupt, absent or not writable
| begining dump of physical memory
| dumping physical memory to disk

 

[Guest]

Archived from groups: microsoft.public.win2000.setup (More info?)

Hi,
You can also use the auto repair function of the registry editor present in
windows xp and windows 2003.

Perform a parallel install of either windows xp or windows 2003 server.

Boot through the parallel installation

Assuming the original installation as c:\winnt and the parallel installation
c:\windows, go the c:\winnt\system32\config and copy software to c:\regbackup
folder(or any other folder to backup the software hive).

Open regedit. Click on hkey_local_machine. Go to File->load hive and browse
to c:\winnt\system32\config and open software. Name it as test.

Once you have loaded it, click on test again and unload the hive.

Try to boot up in the broken installation now.

Lukesh

"sabapathy" wrote:

> sometimes the system shows this message.
> if we try another time booting its gets booting without errors
> i want to know why this happens.
> which virus can cause this error.
>
> the error we get
> the registry cannot loaad the hive(file)
> \systemroot\system32\config\software
> or its log or alternate
> it is corrupt, absent or not writable
> begining dump of physical memory
> dumping physical memory to disk