Outlook 97 fails to run un Windows XP

[PJH]

Good day all ...

When I run Outlook 97 in Windows XP it fails at a fault window which occurs
when at: "Please wait while Outlook builds the Outlook bar". This leads to a
MS fault report window which states error signature as follows:

AppName: outlook.exe AppVer: 8.3.1.4629 ModName: user32.dll
ModVer: 5.1.2600.1255 Offset: 0001d231

Outlook always used to run fine in Win XP before, but I had to fit a new
hard disc after a crash and reinstall Windows XP.

Anyone any ideas how to get round this. I've twice uninstalled Office 97
completely as directed in MS KB 254250 - OFF97 How to Completely Remove
Office 97 on Windows XP. The same fault occurs on reinstalling and running.

PJH

 

[Brian Tillman]

When I run Outlook 97 in Windows XP it fails at a fault window which
occurs when at: "Please wait while Outlook builds the Outlook bar".
This leads to a MS fault report window which states error signature
as follows:

AppName: outlook.exe AppVer: 8.3.1.4629 ModName: user32.dll
ModVer: 5.1.2600.1255 Offset: 0001d231

The Outlook bar is contained in the file a file profilename.fav. Are you
installing as Administrator? Do you have proper access to the folder in
which the fav file is trying to be created? (I don't remember if OL 97 puts
it in %USERPROFILE%Application Data\Microsoft\Outlook,
%WINDOWSDIR%\Application Data\Microsoft\Outlook, or where, but I can look
when I get home, because I use OL 97 on one of my XP machines, too.)

 

[PJH]

Good day all ...

Checking out the reply from Brian Tillman to my original message gave me the
idea to try curing this fault by copying on old Microsoft Outlook.FAV file
to the Windows folder. There are no Windows\Application Data folders in my
XP setup. It has worked and I now have a fully working setup of Outlook 97
in Windows XP. Why Outlook failed to install properly from the Office 97 CD
I have no idea, it had always installed and run properly before, even after
a
complete reinstall of XP. This latest reinstall was necessary because of a
Hard
Disc failure and consequent new HD. Maybe some clue there for the tech
savvy?

Thanks all ...

PJH