Any idea why it worked flawlessly before?
--
Russ Valentine
[MVP-Outlook]
"Garylk" wrote in message
...
Mr. Tillman had the answer - for reasons unknown, the software does not
copy
the Windows/Installer folder at all if you leave "view protected system
files" unchecked, incompletely if you check it. Maybe running the software
from DOS would solve this, but I don't have time to find out.

Anyway, copying the Windows/Installer folder from the old drive and then
running Detect and Repair solves the problem.


"Russ Valentine [MVP-Outlook]" wrote:

We keep coming back to an error with the transfer, then.
--
Russ Valentine
[MVP-Outlook]
"Garylk" wrote in message
news
Since I can't work with Outlook in a "send only" mode, I removed the
new
drive and put the old one back. There have been no hiccups with
Outlook,
Word, or Excel over the past 5 days, so I don't think anything is
corrupted.


"Russ Valentine [MVP-Outlook]" wrote:

Either of those should be perfectly capable of handling the volume
label
changes. Since this has always worked before, do you think any of the
files
on the old drive might have become corrupted before you did the
transfer?
--
Russ Valentine
[MVP-Outlook]
"Garylk" wrote in message
...
No - this was Western Digital's "Data Lifguard" software. Works just
like
MaxBlast (probably the same program with a different GUI) so I
wouldn't
be
surprised if it's the same problem. I'll reconnect the new drive and
see.





"Brian Tillman" wrote:

Garylk wrote:

Lanwench suggested running "Detect and Repair" (which apparently
worked) or reinstalling Office. Unfortunately I can't do either.

When I try that, I get a message to the effect that the patch I'm
trying to access is unavailable.

Let me guess... You added a Maxtor hard drive and used MaxBlast to
do
the
port. The same thing happened to me back in 2005 and the problem
was
that
MaxBlast did not copy the (hidden) folder \Windows\Installer from
the
old
drive. I manually copied that folder to fix the problem. I
contacted
Maxtor about it, but they denied there was a problem. Since then,
I've
seen
other people also report the issue.
--
Brian Tillman