One of my ideas was indeed RegEdit. I wouldn't want to use it as a backup, but since I can't figure out many other uses for the setting to import or export the
entire registry, I assume that that's what MS intended that function to be used for. (I can actually think of one other use, but it's irrelevant here.)
My other idea, which I do myself, is to use the Windows backup utility (ntbackup.exe on Win2000) to make a backup of the "system state" only on another drive. (I don't think that there's a way to use it to back up the registry only. It's more like creating a system restore point, I think.) Even though I do it, I can see two big disadvantages to it:
1. I don't see why one should have to restore all of one's boot files just to fix a registry problem. It looks to me like looking for trouble.
2. The backup is a lot bigger than the registry alone. My registry (my config folder, really) is about 24MB, but my SysState.bkf is 230MB! Just for comparison, I just used the backup gadget of RegVac, which I imagine is similar or identical to that of WinRescue, to make a registry backup, and it's about 21 MB. Also, Ray's gadget is
a lot faster: about 3 or 4 seconds for RegVac, vs. about 5 minutes for ntbackup.
At least MS definitely considers this a registry backup. See the paragraph "Manual steps to back up the whole registry" in
http://support.microsoft.com/kb/322756 .
By the way, John, it's well known that the search gadget for the MS KB is, um, unhelpful. If you type the word "Microsoft" followed by the words you really want into Google, (producing , for example,
http://www.google.com/search?hl=en&q=microsoft+back+up+registry ), the knowledge base article you need will often be one of the first results. It's funny that the only way to use the MS KB efficiently is by using their arch-enemy's search tool, but that's the way it is.
Thanks.
C.