Archived from groups: microsoft.public.win98.gen_discussion (
More info?)
FM,
I am perfectly familiar with the procedure you describe (and so is Glen.). I
just wanted to be sure we were talking about the same thing. But it is *not* a
Microsoft recommended procedure for Windows 98, AFAIK. It usually works, and has
worked for me on those few occasions I've used it on Win98 Registries, but it's
fraught with potentials for error. (If you have a link to the documentation
you're using for this procedure, I'd like to have a look.) MS developed "Scanreg
/opt /fix" for Win98 to do essentially the same procedure. However, sometimes
that procedure fails, usually due to System.dat size. Perhaps you ran into a
similar problem. Also, you mentioned "changes" to the Registry, and the usual
term for that is "Registry hacking". I intended no insult.
What you seem to have missed in all this, the point I was trying hard to get
across, is that if Windows is rejecting your new Registry and restoring a
backup, then *something* you did was wrong. That Registry has been deemed by
Windows to be faulty. I can't say how or why this would happen, since I don't
know the precise steps you took. But you *seem* to be suggesting that if only
you can stop Windows from performing that Registry check during startup, it will
load your new Registry and run. It won't do that. It will, instead, just fail to
load. If you have previously deleted all the backups, where does that leave you?
Anyway, it's your machine to do with what you want. Here's the info you're
looking for:
SCANREGW.EXE is an optional Startup item that's launched during startup to check
the integrity of the Registry and to make a new backup if one doesn't already
exist for "today". You can disable SCAN REGISTRY in the Startup tab of MSCONFIG.
I'm not sure that this will stop Windows from using Scanreg /restore if it runs
into a fatal error involving the Registry, but I think that may be the case. It
will be looking for these backups in the Hidden folder called
C:\Windows\SYSBCKUP. They're stored in CAB files with the names RBnnn.CAB, where
nnn is a number, (or RBBAD.CAB, which is a backup that's made before running
Scanreg /opt or Scanreg /fix or before restoring a backup.)
I'm sorry you think I was being rude. I simply found myself astounded by the
things you were suggesting. And I'll say it again--if the Registry size is all
that's bugging you, if your intent is to recover some disk space, then you're
really spending a lot of time and effort just to save a few MB.
Whatever, I can assure you that your own best interests were behind what I
wrote. I hope the above has clarified that for you.
--
Gary S. Terhune
MS-MVP Shell/User
"FM" <fm@ncinternet.com> wrote in message
news:O1wMEbOvFHA.1252@TK2MSFTNGP09.phx.gbl...
> Dear Gary and Glen,
>
> For MS-MVP's I'm supprised you're not familar with the regedit
> reconstruction process. Breify stated, done in DOS, Regedit exports the KHLM
> and HKU key structures(the system.dat and user.dat) into two temporay files
> ("Hklm.reg & Hku.reg"), erases the existing registry, then reconstructs it
> from the temporay files.
> The process encompasses safegards via renaming current files "old" and
> saving both the user.dat and system.dat in another location. I'm not trying
> to destroy the recover process. I'm trying to use the current "reconstructed
> registry" and not have the system restore a registry which existed in the
> last 5 backups by the system prior to the reconstruction. Legimate
> corrections were made via the regedit process and should be reflected in the
> registry. They have not been.
>
> To Glen,
> I hope I have correctly explained the process? If not I can post the
> procedure?
>
>
> To Gary
>
> I find it hard to understand your admonishment? The reconstruction option is
> a Microsoft procedure. Reconstruction and Restoration are not necessary
> synonymous. If the registry is in need of reconstruction, rather than
> restoration, for what ever reason, it appears that Microsoft understood that
> need and created a process to handle it. My basic need here is how to "Save
> or backup" a reconstructed registry. Before you belittle those who seek
> advise or accuse someone of hacking, I would suggest you get informed of
> Microsoft's programs. With all due respect to you and all RVP's who labor
> herein, Non Experts are here for help. If that falls outside your realm then
> I would suggest your time would be better spent elsewhere, becuse you have
> not been helpful.
>
> To Brian,
>
> I thank you for your help. I belive I had already done most of what you
> suggested, however I will follow the links and make sure. I'll get back to
> you.
>
> Your assistance is apprecated.
>
> Sincerely,
>
> FM
>
>