ag - As an alternative to using a floppy, if you store the .txt file within
your %System% directory (or a sub-directory), then you'll be able to cd to
that directory and access it also from the Recovery Console and execute the
batch cmd directly. You might also want to consider using Erdnt/Erunt and
restoring its files using the batch approach:
Get Erunt here for all NT-based computers including XP:
http://www.larshederer.homepage.t-online.de/erunt/ I've set it up to take a
scheduled backup each night at 12:01AM on a weekly round-robin basis, and a
Monthly on the 1st of each month. See here for how to set that up:
http://www.larshederer.homepage.t-online.de/erunt/erunt.txt, and for some
useful information about this subject
The following tutorials are useful:
Installing & Using ERUNT
http://www.silentrunners.org/sr_eruntuse.html
To see an illustrated registry restore procedure
http://www.silentrunners.org/sr_erdntuse.html
This program is one of the best things around - saved my butt on many
occasions, and will also run very nicely from a DOS prompt (in case you've
done something that won't let you boot any more and need to revert to a
previous Registry) IF you're FAT32 OR have a DOS startup disk with NTFS
write drivers in an NTFS system. (There is also a way using the Recovery
Console to get back to being "bootable" even without separate DOS write NTFS
drivers, after which you can do a normal ERDNT restore. See erunt.txt for
detailed instructions. Basically, if you make your backup into a folder
inside your Windows or Winnt folder, you can restore at a Recovery Console
boot by copying the files from that ERDNT folder into the system32\config
folder. After a good boot, then do another normal ERDNT restore to also
restore the user hives also. See below for more detail about doing
Recovery. (BTW, it also includes a Registry defragger program). Free, and
very, very highly recommended.
FYI, quoting from the above document:
Note: The "Export registry" function in Regedit is USELESS (!) to make a
complete backup of the registry. Neither does it export the whole registry
(for example, no information from the "SECURITY" hive is saved), nor can the
exported file be used later to replace the current registry with the old
one. Instead, if you re-import the file, it is merged with the current
registry, leaving you with an absolute mess of old and new registry keys.
Recovery:
You can only do a normal restore (as an 'outside of Windows' recovery) from
a DOS boot if your file system is FAT32 OR you have NTFS drivers.
However, you can do a partial restore to get back to being bootable by using
the Recovery Console if you've installed it, and then do a full restore.
(BTW, remember to re-install the Recovery Console if you slipstream any of
your SP's into a local i386 folder.)
Essentially, the approach is to put the ERDNT folder(s) where your nightly
ERUNT is saved inside %SystemRoot% and then use the Recovery Console to
first back up the existing hives in %SystemRoot%\System32\Config and then
replace them with the ones from an appropriate ERDNT folder. This won't
restore the User hives, but will let you boot so that you can then do a
normal ERDNT restore of all hives. You can do it manually or you can
automate the process by using a batch regcopy1.txt command in
Recovery Console where regcopy1.txt contains something like (in this case
E:\ is the %SystemRoot% for my Win2kProSP4 system, and I save to both a Temp
folder and a nightly named folder each night. Here I'm just using the Temp
which will have the last night's save in it.):
md tmp
copy e:\winnt\system32\config\system e:\winnt\tmp\system.bak
copy e:\winnt\system32\config\software e:\winnt\tmp\software.bak
copy e:\winnt\system32\config\sam e:\winnt\tmp\sam.bak
copy e:\winnt\system32\config\security e:\winnt\tmp\security.bak
copy e:\winnt\system32\config\default e:\winnt\tmp\default.bak
delete e:\winnt\system32\config\system
delete e:\winnt\system32\config\software
delete e:\winnt\system32\config\sam
delete e:\winnt\system32\config\security
delete e:\winnt\system32\config\default
copy e:\winnt\ERDNT\Temp\system e:\winnt\system32\config\system
copy e:\winnt\ERDNT\Temp\software e:\winnt\system32\config\software
copy e:\winnt\ERDNT\Temp\sam e:\winnt\system32\config\sam
copy e:\winnt\ERDNT\Temp\security e:\winnt\system32\config\security
copy e:\winnt\ERDNT\Temp\default e:\winnt\system32\config\default
See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;307545 (Be
very careful about your specific system's ERUNT naming conventions which can
depend upon just how your backup was saved, manually vs. a scheduled task.)
As to your other comment - I think you've experienced very good luck and/or
are very careful in using such cleaners if you haven't had a bad experience.
We see a constant stream of screwed up Registries because of them, and I
don't think I know of an MVP who will recommend their use. YMMV, however.
--
Regards, Jim Byrd, MS-MVP
My, Blog Defending Your Machine, here:
http://defendingyourmachine.blogspot.com/
ag said:
it's been awhile so fogive the question: i assume you create the text
file in notepad on a floppy, then while in the recovery console
switch to the a: drive and type the "batch" command?
kurttrail said:
ag said:
i have read this article
See "How to Recover from a Corrupted Registry"
(
http://support.microsoft.com/?kbid=307545).
any help on how to put together aand run the batch file to automate
step 2?
sorry it this is a duplicate...i first posted a reply to an earlier
thread because i could not get the new new post window to open
"If you have access to another computer, to save time, you can copy
the text in step two [actually shoud be step five], and then create
a text file called "Regcopy1.txt" (for example). To create this
file, run the following command when you start in Recovery Console:
batch regcopy1.txt"
"With the batch command in Recovery Console, you can process all the
commands in a text file sequentially. When you use the batch command,
you do not have to manually type as many commands."
USE NOTEPAD TO COPY THE COMMANDS, AND SAVE THE TEXT FILE.
--
Peace!
Kurt
Self-anointed Moderator
microscum.pubic.windowsexp.gonorrhea
http://microscum.com/mscommunity
"Trustworthy Computing" is only another example of an Oxymoron!
"Produkt-Aktivierung macht frei"