thanks
Windows Installer 3.1 Redistributable (v2)
http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en
Windows Installer 4.5 Redistributable
(Latest version of Windows Installer)
http://www.microsoft.com/downloads/details.aspx?familyid=5A58B56F-60B6-4412-95B9-54D056D6F9F4&displaylang=en
Also:
Common Windows Installer Problems
http://support.microsoft.com/?kbid=555175
Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301
WBS/Finish Start/Critical Path = Good luck
-- 
JS
http://www.pagestart.com
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:3CFD9DEA-9392-4275...@microsoft.com...
Thanks
The Windows Installer Service Could Not Be Accessed
(The error message when you receive when installing a program in Windows XP)
See: http://support.microsoft.com/?kbid=315353
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:507F3A2E-4174-4E6C...@microsoft.com...
--
All the Best,
Kelly (MS-MVP/DTS&XP)
Taskbar Repair Tool Plus!
http://www.kellys-korner-xp.com/taskbarplus!.htm
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:98181640-7406-4C04...@microsoft.com...
There are some suggestions here for 1402.
"You receive an error message when you install an Office program or open an Office program or document"
http://support.microsoft.com/kb/838687
It is possible to use a Sysinternals program called Process Monitor,
to watch Registry activity. I've managed to fix a registry problem,
by watching a piece of code until it exited, then walking backwards
through the event trace to see what was the last Registry activity.
I actually fixed a sound problem on my machine that way. Due to
the "needle in a haystack" nature of a method like that, I would
rate such an approach as having a low probability of succeeding.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Process Monitor works best, if you start by identifying the program
to be traced, as that reduces the number of captured events you
end up looking at. I had to scroll through about 100,000 of them,
while working on my little problem. I imagine something like
an MS Project installation would be much worse. In cases
where multiple pieces of code may be involved, and they may
start and exit quickly, your odds are much worse then. The
problem then, is figuring out what to trace or filter for.
Paul
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:09218025-E96A-4ABB...@microsoft.com...
"Kerry" <Ke...@discussions.microsoft.com> wrote in message 
news:CEC75EDA-B8A5-474A...@microsoft.com...
Thanks again
Next use regedit any search for any orphaned Office/Project
entries.
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:79F1D1C4-30ED-4CDC...@microsoft.com...
Thanks again
Home page: http://www.getpaint.net/
Download: http://www.dotpdn.com/downloads/pdn.html
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:7CA0151B-0B7F-450D...@microsoft.com...
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:99387256-0EB5-46AD...@microsoft.com...
"Brent" <Br...@discussions.microsoft.com> wrote in message 
news:5397C2BC-D43F-4F15...@microsoft.com...