"BAP" wrote in message
...
| What a relief, MEB! I had been spending considerable amount of time
| collecting issues, suggestions, answers from the replies to the original
and
| subsequent post regarding Microsoft Office 2000 SR-1 Standard and had
several
| pages almost ready for posting, but I am glad that you came thru with your
| recap that, I am sure, would be more to the point than mine would have
been.
| Thank you!

None needed, but YW anyway. It was started in this news group in two other
threads, we should be able to end it here successfully.
Hopefully, I used only the most needed parts so the issues can be resolved.

|
| The Office Applications, following the installation of MS Office 2000 Pro,
| continue to perform as explained in my last reply to your questions.
| To this point, I have not attempted to follow BC's suggestion for cleaning
| up my Registry. I am ready to do so, however, as my confidence grows that
I
| won't mess up the timing and progression of things to do, avoiding the
| dont's.
|
| Your latest comments:
| ?MSRCLR40.DLL is Microsoft Jet Briefcase Reconciler Library [my present
| version is 4.00.2927.2], to partially address BAP's listed error at 3. per
my
| questions.
| ***
| Hopefully this would prompt for answers that could cure "Error 1904 -
Module
| C:\Windows\System\MSRCLR40.DLL had failed to register. HResult-2147023739.
| Contact your Support Personnel".

Let's see if the Shell and other related MVPs, or someone else, provides a
response for this.

|
| Your next comment:
| Note that BAP's registry is filled with old entrees which need removed,
and
| is likely too large for a successful /fix /opt using scanreg unless they
are
| removed [hence the need to clean the registry first].
| ***
|
| By [hence the need to clean the registry first], I assume you mean to
clean
| the registry by running CCleaner, as BC suggests with the following:
|
| 1) CCleaner should always give you a backup option when
| you pick Fix All Selected issues.
|
| 2) I would purge anything CCleaner sees as an issue. It's
| a very conservative registry cleaner.

CCleaner is conservative, however, some programs may have modified the
registry [which may or may not show in the cleaner], which probably should
not be removed. I suggest "may or may not be", related to prior issues which
indicated improper and/or removed registry entries interferring with the
Office uninstallation/installation which indicates other potential issues.

For instance: Running ccleaner on my system turns up a number of entries,
one of which is related to Nero Burning Rom for its language libraries, as
missing shared dlls. However Nero accesses these keys IN CASE there is a
language change. Removing them MIGHT create a program error issue. So this
type of entry [for other programs] may NOT be advisable to remove.

Another relates to createcd50.exe [Adaptec driver for WMPlayer in \common
files\Adaptec] {I post this relationship here, and for another thread
related to CDROM problems, hopefully someone will pick up on what it means}.

Another: If your running SpywareBlaster and/or Spybot S&D; ActiveX entries
may appear which have been disabled. Microsoft may have disabled some of its
own entries as well.

Another relates to the tshoot [trouble shooter/help issues] which was
disabled by Microsoft for security reasons.

Another relates to Front Page Express; disabled entries to negate improper
usage.

Yet another relates to AVG and ActiveX issues.

At minimum, likely the ActiveX, Front Page, and tshoot entries should be
left as they are [pending later review]. Nero, if your running that, should
also be left alone. Check for any issues related to your AV program and
firewall, and leave those for later review also.

What I'm trying to present is: rather than a mass deletion, a careful
removal of "directly related" entries, starting with known invalid entries
[for removed programs, games, etc.] would be best.
You can review the entries while in ccleaner [paths] and search for them
PRIOR to removal.
Back up during the removal [in ccleaner], and shut down/restart after EACH
modification.
PRIOR to each shut down/restart, make a registry backup via Microsoft's
tool [MSInfo - Tools - Registry Checker] so you have an emergency backup to
revert to if necessary. Copy your last good backup BEFORE starting the
removal process to another folder, JUST IN CASE [BC gave you a bat for the
purpose, though you can also do this manually]. This will give you the
tripled ability to monitor for individual problems and errors associated
with the various removals, and potentially revert to a good registry should
you run across problems.
I realize this is long and redundant work, but apparently the registry
hasn't been maintained for several years, so now is "payment" time.

The actual Office entries which will appear, should be left for one of the
last issues to address. When you get to that point, post what you find for
comparison to other's Office entries.

Once you get the registry cleaned to a single shown page [which is where it
should be] or maybe two, then you can post questions, if necessary,
regarding those individual entries.

On a related note: another program which can be used for registry
modifications and cleaning is Hoverdesk RegSeeker. This tool will allow you
to double click on the entry, which then opens it in regedit. It will return
far more entries, and is NOT for the neophyte to registry modification and
clean up, though those with experience will appreciate its extended
abilities. Again, I caution: those not completely familiar with the registry
and its entries; should preferably use some other cleaning program like
ccleaner CAREFULLY as being discussed.

|
| 3) To restore the registry files backed up with regback.bat
| simply means copying the contents of the regback folder,
| especially system.dat and user.dat, into the c:\windows
| folder, overwriting what's already there. You would have
| to use the attrib command to unhide and unprotect the
| active system and user dat files first. The easiest way
| would be to just rename the c:\windows\regback folder
| that was already created to something like regback1 or
| such. Regback.bat will recreate a new regback folder,
| make another copy of the system files, and unprotect
| and unhide the registry files as well.
|
| I would make another backup of the existing system
| files before reusing an older backup.
|

The below should be used only AFTER you have carefully cleaned your
registry and found no errors, or errors which might be corrected BY using
this technique, as final cleanup/compaction. The present registry is too
large and with apparently too many invalid entries for accurate usage. If it
were not so, then this might be a good way to do "house cleaning".
Moreover, it sometimes removes entries from the registry by "mistake"
[doesn't recognize them properly and removes them] so this technique also
needs to be used with caution.

| Once you've cleaned up things with CCleaner as best
| you can, you can use a Microsoft trick to mildly
| optimize the registry:
|
| a) Restart in DOS mode (the prompt doesn't matter)
|
| b) Enter: smartdrv
| (optional, for speed)
|
| c) Then enter: scanreg /fix /opt
|
| ****
|
| MEB, thank you again, for your work!

Well, we're not done yet... and others have already helped and will be
helping... none of us need thanks, we like helping others if we can, though
its always appreciated...

--
MEB
http://peoplescounsel.orgfree.com/
BLOG - http://peoplescounsel.spaces.live.com/ Public Notice or the "real
world"

"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________