corrupted registry file

[Dave]

Ok first I know that I should have backed up the registry
file before I began. Too Late for that.

I edited The userinit file in the following section to
the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVers
ion\Winlogon

from C:\WINNT\system32\userinit.exe,
to C:\WINNT\system32\userinit.exe,F:\Program Files\Common
Files\Symantec Shared\SymTray.exe "Norton Systemworks",

to try and fix the system tray for Norton.

Now my computer starts to load my personal settings then
immediately colses and tries to save them and continues
the loop of starting and shutting down.

I can get to a dos prompt and would like to edit the
registry form there. Does anyone know which directory the
SOFTWARE file form the Machine key is kept?

Can I edit it from dos? Where would the previous version
be located so I could just copy over the corrupted one.

 

[Mark V]

Ok first I know that I should have backed up the registry
file before I began. Too Late for that.

But not too late to do so in the future. Religiously.

I edited The userinit file in the following section to
the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVers
ion\Winlogon

from C:\WINNT\system32\userinit.exe,
to C:\WINNT\system32\userinit.exe,F:\Program Files\Common
Files\Symantec Shared\SymTray.exe "Norton Systemworks",

Oops. Not good (as you realize). The wrong place entirely for the
symtray reference.

to try and fix the system tray for Norton.

Now my computer starts to load my personal settings then
immediately colses and tries to save them and continues
the loop of starting and shutting down.

I can get to a dos prompt and would like to edit the
registry form there. Does anyone know which directory the
SOFTWARE file form the Machine key is kept?

There is no "DOS" in NTx systems. There is a "command prompt"
(usually a CMD.EXE prompt), there is Recovery Console and there is
Safe Boot Command Prompt. The first is only available if you can
successfully boot the OS. The RC is useful if you had a made a
backup of the registry in advance with ntbackup.exe or other tool.
The third may not work with your current registry at all. But try
that "F8" startup option just to see.

Can I edit it from dos? Where would the previous version
be located so I could just copy over the corrupted one.

No.
A "Previous version" does not exist. Nothing like in Win98. Only if
you made a registry backup would there be a version stored at
%systemroot%\repair\RegBack\

There is also the default at-OS-installation registry stored in
"\repair\" but nothing since the OS install will be in it.

One possible solution is to do a "parallel install" of the OS and
then use that to edit the SOFTWARE hive file from the damaged
installation via regedt32.exe.

There are other convoluted and relatively advanced methods via
Recovery Console that might be considered.

Is the filesystem FATx or NTFS? Options change somewhat depending on
that and if you have another system with the OS available.

If you can access the partition have you tried renaming the
symtray.exe file? Jut a thought and may not help.

A final option may be to "install over" or "install in-place" the OS
on top of the existing installation. That may or may not work. I'd
wait for more feedback and information before proceeding with this
one.

You say no OS version and SP, which IMO should always be included
along with in theis case the filesystem in use.

 

[Mark V]

Ok first I know that I should have backed up the registry
file before I began. Too Late for that.

But not too late to do so in the future. Religiously.

I edited The userinit file in the following section to
the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVers
ion\Winlogon

from C:\WINNT\system32\userinit.exe,
to C:\WINNT\system32\userinit.exe,F:\Program Files\Common
Files\Symantec Shared\SymTray.exe "Norton Systemworks",

Oops. Not good (as you realize). The wrong place entirely for the
symtray reference.

to try and fix the system tray for Norton.

Now my computer starts to load my personal settings then
immediately colses and tries to save them and continues
the loop of starting and shutting down.

I can get to a dos prompt and would like to edit the
registry form there. Does anyone know which directory the
SOFTWARE file form the Machine key is kept?

There is no "DOS" in NTx systems. There is a "command prompt"
(usually a CMD.EXE prompt), there is Recovery Console and there is
Safe Boot Command Prompt. The first is only available if you can
successfully boot the OS. The RC is useful if you had a made a
backup of the registry in advance with ntbackup.exe or other tool.
The third may not work with your current registry at all. But try
that "F8" startup option just to see.

Can I edit it from dos? Where would the previous version
be located so I could just copy over the corrupted one.

No.
A "Previous version" does not exist. Nothing like in Win98. Only if
you made a registry backup would there be a version stored at
%systemroot%\repair\RegBack\

There is also the default at-OS-installation registry stored in
"\repair\" but nothing since the OS install will be in it.

One possible solution is to do a "parallel install" of the OS and
then use that to edit the SOFTWARE hive file from the damaged
installation via regedt32.exe.

There are other convoluted and relatively advanced methods via
Recovery Console that might be considered.

Is the filesystem FATx or NTFS? Options change somewhat depending on
that and if you have another system with the OS available.

If you can access the partition have you tried renaming the
symtray.exe file? Jut a thought and may not help.

A final option may be to "install over" or "install in-place" the OS
on top of the existing installation. That may or may not work. I'd
wait for more feedback and information before proceeding with this
one.

You say no OS version and SP, which IMO should always be included
along with in theis case the filesystem in use.

 

[Guest]

LET'S GO IN ORDER:
1. I Put the symtray there because in looking at the
knowledge base in Norton this is what they instructed.
http://service1.symantec.com/SUPPORT/nsw.nsf/73ca7f4f5b3d25
a68825695800760838/ffde23da3d536f8cc12569670053c52c?
OpenDocument&prod=&ver=&src=sg&pcode=&svy=&csm=no

2. I am running w2k pro and had SP 4 installed and the
filesystem is FAT32.

3. Since writing the original post, I have installed a
parallel OS on drive C:. Boy does it look bare. You
mention the potential of editing the SOFTWARE hive file
from the damaged installation via regedt32.exe. How would
I be able to find/edit the original SOFTWARE?

4. When I boot up in Safe Mode, all I get is a black
screen with "safe mode" around the perimeter. this is
useless to me.

Does any of this get me closer to recovery? Thanks iun
advance....

 

[Guest]

LET'S GO IN ORDER:
1. I Put the symtray there because in looking at the
knowledge base in Norton this is what they instructed.
http://service1.symantec.com/SUPPORT/nsw.nsf/73ca7f4f5b3d25
a68825695800760838/ffde23da3d536f8cc12569670053c52c?
OpenDocument&prod=&ver=&src=sg&pcode=&svy=&csm=no

2. I am running w2k pro and had SP 4 installed and the
filesystem is FAT32.

3. Since writing the original post, I have installed a
parallel OS on drive C:. Boy does it look bare. You
mention the potential of editing the SOFTWARE hive file
from the damaged installation via regedt32.exe. How would
I be able to find/edit the original SOFTWARE?

4. When I boot up in Safe Mode, all I get is a black
screen with "safe mode" around the perimeter. this is
useless to me.

Does any of this get me closer to recovery? Thanks iun
advance....

 

[Mark V]

LET'S GO IN ORDER:
Good.

1. I Put the symtray there because in looking at the
knowledge base in Norton this is what they instructed.
http://service1.symantec.com/SUPPORT/nsw.nsf/73ca7f4f5b3d25
a68825695800760838/ffde23da3d536f8cc12569670053c52c?
OpenDocument&prod=&ver=&src=sg&pcode=&svy=&csm=no

Sorry. I do not use Symantec products and haven't for years. They
are noted for massive registry and system alterations that do often
not get cleaned up at un-installation... That seems a peculiar
recommendation though from my point of view. Your choice of course.

2. I am running w2k pro and had SP 4 installed and the
filesystem is FAT32.

FAT32 does mean that some options (like boot DOS) are available to
get to the file. But see below.

3. Since writing the original post, I have installed a
parallel OS on drive C:. Boy does it look bare. You
mention the potential of editing the SOFTWARE hive file
from the damaged installation via regedt32.exe. How would
I be able to find/edit the original SOFTWARE?

Yes. the System's registry is stored in "hive" files on the disk.
These files are accessible when (that) OS is not running. Look at
old install: <windows directory>\system32\config\
You will see files like SOFTWARE SYSTEM SECURITY SAM and several
others.

First copy these files to an alternate location just as a backup.
RUN..., regedt32.exe (in the new instalation as an Administrator)
From the regedt32 menus:
Note the Help menu and revies the "Load hive" / "Loading hives"
entries

Focus on the child window that is HKEY_LOCAL_MACHINE on Local
Machine
Focus on the "top" entry (HKEY_LOCAL_MACHINE)
From the Registry menu use the Load Hive
Navigate to the _old_ installation's "config" location and select
to load the SOFTWARE (hive) file.
Give it an arbitrary name when prompted.
Navigate in that loaded branch to the WINLOGON key and change the
data back to the default. Then put focus on the top of the loaded
hive branch and,
!!! When finished use the Registry menu to UNLOAD the hive, then
close regedt32. Always "unload hive" before closing regedt32.

Shutdown, reboot to the "old" installation and see if that did in
fact make you again bootable.

It could of course be some other Symantec thing causing the problem.

 

[Mark V]

LET'S GO IN ORDER:
Good.

1. I Put the symtray there because in looking at the
knowledge base in Norton this is what they instructed.
http://service1.symantec.com/SUPPORT/nsw.nsf/73ca7f4f5b3d25
a68825695800760838/ffde23da3d536f8cc12569670053c52c?
OpenDocument&prod=&ver=&src=sg&pcode=&svy=&csm=no

Sorry. I do not use Symantec products and haven't for years. They
are noted for massive registry and system alterations that do often
not get cleaned up at un-installation... That seems a peculiar
recommendation though from my point of view. Your choice of course.

2. I am running w2k pro and had SP 4 installed and the
filesystem is FAT32.

FAT32 does mean that some options (like boot DOS) are available to
get to the file. But see below.

3. Since writing the original post, I have installed a
parallel OS on drive C:. Boy does it look bare. You
mention the potential of editing the SOFTWARE hive file
from the damaged installation via regedt32.exe. How would
I be able to find/edit the original SOFTWARE?

Yes. the System's registry is stored in "hive" files on the disk.
These files are accessible when (that) OS is not running. Look at
old install: <windows directory>\system32\config\
You will see files like SOFTWARE SYSTEM SECURITY SAM and several
others.

First copy these files to an alternate location just as a backup.
RUN..., regedt32.exe (in the new instalation as an Administrator)
From the regedt32 menus:
Note the Help menu and revies the "Load hive" / "Loading hives"
entries

Focus on the child window that is HKEY_LOCAL_MACHINE on Local
Machine
Focus on the "top" entry (HKEY_LOCAL_MACHINE)
From the Registry menu use the Load Hive
Navigate to the _old_ installation's "config" location and select
to load the SOFTWARE (hive) file.
Give it an arbitrary name when prompted.
Navigate in that loaded branch to the WINLOGON key and change the
data back to the default. Then put focus on the top of the loaded
hive branch and,
!!! When finished use the Registry menu to UNLOAD the hive, then
close regedt32. Always "unload hive" before closing regedt32.

Shutdown, reboot to the "old" installation and see if that did in
fact make you again bootable.

It could of course be some other Symantec thing causing the problem.

 

[Guest]

OK, I am up and walking again. There are a couple of
things still lingering.

It is continually asking for the CD that has MSRedist.msi
file on it. I cannot find this anywhere nor what is it
used for. Do you have a clue?

How can I remove the parallel w2k? I believe this will
help me with only having 4MB left on my C drive.

Thanks again

 

[Guest]

OK, I am up and walking again. There are a couple of
things still lingering.

It is continually asking for the CD that has MSRedist.msi
file on it. I cannot find this anywhere nor what is it
used for. Do you have a clue?

How can I remove the parallel w2k? I believe this will
help me with only having 4MB left on my C drive.

Thanks again

 

[Gary Karasik]

Re the MSREDIST message: Try removing Systemworks, then reinstalling.
Failing that, try the Symantec Knowledge Base.

GaryK

 

[Gary Karasik]

Re the MSREDIST message: Try removing Systemworks, then reinstalling.
Failing that, try the Symantec Knowledge Base.

GaryK

 

[Mark V]

OK, I am up and walking again. There are a couple of
things still lingering.

It is continually asking for the CD that has MSRedist.msi
file on it. I cannot find this anywhere nor what is it
used for. Do you have a clue?

Sorry I do not. Does not exist here. ".MSI" is however the
extension for the Microsoft Installer files (and others like .mst).
You may need to go to another group. microsoft.public.win2000.msi ?
perhaps ?

How can I remove the parallel w2k? I believe this will
help me with only having 4MB left on my C drive.

Basically two operations.
* Remove the (2nd) windows-install directory and all files and sub-
directories. Be careful you get the correct one!
* Remove the line in BOOT.INI (a hidden file in the root of the
drive) that points to the (2nd) installation. This is usually on
"C:" drive. Be careful that you delete the correct line.!

Do this soon as 4MB free space is way to little (and dangerous).

Thanks again

YW
Glad you got it all back.

[ ]

 

[Mark V]

OK, I am up and walking again. There are a couple of
things still lingering.

It is continually asking for the CD that has MSRedist.msi
file on it. I cannot find this anywhere nor what is it
used for. Do you have a clue?

Sorry I do not. Does not exist here. ".MSI" is however the
extension for the Microsoft Installer files (and others like .mst).
You may need to go to another group. microsoft.public.win2000.msi ?
perhaps ?

How can I remove the parallel w2k? I believe this will
help me with only having 4MB left on my C drive.

Basically two operations.
* Remove the (2nd) windows-install directory and all files and sub-
directories. Be careful you get the correct one!
* Remove the line in BOOT.INI (a hidden file in the root of the
drive) that points to the (2nd) installation. This is usually on
"C:" drive. Be careful that you delete the correct line.!

Do this soon as 4MB free space is way to little (and dangerous).

Thanks again

YW
Glad you got it all back.

[ ]

 

[Mark V]

Re the MSREDIST message: Try removing Systemworks, then reinstalling.
Failing that, try the Symantec Knowledge Base.

[ ]

Thanks for jumping in. ...ah, another "Symantec Thing". <sigh>

 

[Mark V]

Re the MSREDIST message: Try removing Systemworks, then reinstalling.
Failing that, try the Symantec Knowledge Base.

[ ]

Thanks for jumping in. ...ah, another "Symantec Thing". <sigh>

 

[Gary Karasik]

What I *really* wanted to say (but you can't make jokes when someone's
having a problem) was, "Remove Systemworks, then use the Systemworks CD and
any other Symantec CDs as skeet-shooting targets."

I shouldn't pick on Symantec. They're no worse than many others.

GaryK

Re the MSREDIST message: Try removing Systemworks, then reinstalling.
Failing that, try the Symantec Knowledge Base.

[ ]

Thanks for jumping in. ...ah, another "Symantec Thing". <sigh>

 

[Gary Karasik]

What I *really* wanted to say (but you can't make jokes when someone's
having a problem) was, "Remove Systemworks, then use the Systemworks CD and
any other Symantec CDs as skeet-shooting targets."

I shouldn't pick on Symantec. They're no worse than many others.

GaryK

Re the MSREDIST message: Try removing Systemworks, then reinstalling.
Failing that, try the Symantec Knowledge Base.

[ ]

Thanks for jumping in. ...ah, another "Symantec Thing". <sigh>

 

[Mark V]

What I *really* wanted to say (but you can't make jokes when
someone's having a problem)

Me too.

was, "Remove Systemworks, then use the
Systemworks CD and any other Symantec CDs as skeet-shooting
targets."

And then spend an age trying to clean up after the mess.

I shouldn't pick on Symantec. They're no worse than many others.

True, but they _are_ a long way from Peter Nortons products...

And did you hear, they just scooped up PowerQuest.
(moment of silence)

Cheers

 

[Mark V]

What I *really* wanted to say (but you can't make jokes when
someone's having a problem)

Me too.

was, "Remove Systemworks, then use the
Systemworks CD and any other Symantec CDs as skeet-shooting
targets."

And then spend an age trying to clean up after the mess.

I shouldn't pick on Symantec. They're no worse than many others.

True, but they _are_ a long way from Peter Nortons products...

And did you hear, they just scooped up PowerQuest.
(moment of silence)

Cheers