Is defragmenting the registry something that needs to be done? I have
been told this by a computer tech friend. Any input would be
appreciated. Also, is there a freeware program that can do this?
Thank you!
After wading through all the responses to your question, I will
assume you are inquiring about 'compacting' the registry. This
subject was examined, cussed and discussed in depth recently in
the more appropriate NG, microsoft.public.win98.gen_discussion.
Following is one of the more thorough positions on this subject:
____________________________
Subject: Re: Scanreg /opt and /fix registry compaction - results
Date: Wed, 28 May 2003 00:47:55 -0700
Newsgroups: microsoft.public.win98.gen_discussion
I know I'm not following the party line, here, but I once did
substantial tests of these operations.
First, the scanreg backups are not really a good indication of
Registry size. It's a compressed archive, subject to variations
in the compression ratio. And the backup/restore functions are
the only ones which involve files other than the Registry DAT
files.
If you read the literature, you'll discover that all the /opt
switch does is remove empty records--it's a simple database
compaction (and perhaps "repair") function, pretty much identical
to any other database compaction facility found all over the place,
even in OE (Compact Folders.) When you delete records in many
databases, the actual space that the record occupied remains in the
structure--it's just empty of useful data. Compacting removes
these empty records and sometimes repairs the table structures and
relational connections, plus re-indexing if indexing is a part of
the database's behavior.
The /fix switch actually inspects for certain types of invalid or
meaningless entries, then rebuilds it from scratch--functionally
similar, or perhaps even exactly the same as, the old Export/Import
routines that used to be done to repair and optimize the Registry,
analogous to defragmenting with file optimization. /Fix also appears
to "align" the DAT files on 4KB sectors, preventing any particular
entry from spanning two pages of RAM. Further indications exist to
suggest that empty space is left where expansion is expected, though
that may be stretching it a bit.
In fact, if you run /opt and then /fix, and then /opt again, then
look at the size, then run /fix again, the Registry grows slightly,
and by quantities that are suspiciously round in binary terms. If
you run /opt again, that extra added file size gets removed. You can
go back and forth like this ad infinitum. But the only time you "may"
get any different figures for /fix or /opt compared to themselves is
comparing an /opt run before /fix to another /opt run after /fix.
Once /fix has been run, that Registry is optimized, and running /opt
will only remove small quantities of empty space that /fix put in
there for the sake of better performance and reliability.
So, for my money, the proper procedure is to boot to a "pure DOS"
situation, load SMARTDRV (or it will take a long, long, long time...)
Then run scanreg /opt to get rid of empty records, then run /fix to
re-write the files in proper order and align the data.
Gary S. Terhune
MS MVP for Windows 9x
__________________
Interesting!
BoB
For the duration, my address is fake.