B
burningthemidniteoil
Hi all
If you are having problems installing Office 2003 on Vista and
Office Setup it just hangs after starting to install components
and the progress meter just sit there- if this sounds like you right?
Check if the Findfast.exe process
is running and end that process
I did that and wella ! Office 2003 installed on Vista (im a genuis i
know) . I only installed MSaccess part.
I had Office 97 on there and 2007 (which i uninstalled). Office 97
will not uninstall on vista
so when you install office 2003 install a new copy do not upgrade.
Now how to kill this process FindFast
1. (open up the task manager) Press Ctrl , Alt , Del buttons
simultaneosly.
2. Select Start Task Manager
3. Select the processes tab
4. Select findfast process scroll down, it should be using 50% of CPU
processing!
5. End Process
6. And office setup progress bar magically comes to life!
Just as well im an old UNIX programmer! Thank god microsoft created a
separate process
and not one giant setup EXE! eh?
I hope that helps because I'm probably the only one who has got around
this problem..
Mike
If you are having problems installing Office 2003 on Vista and
Office Setup it just hangs after starting to install components
and the progress meter just sit there- if this sounds like you right?
Check if the Findfast.exe process
is running and end that process
I did that and wella ! Office 2003 installed on Vista (im a genuis i
know) . I only installed MSaccess part.
I had Office 97 on there and 2007 (which i uninstalled). Office 97
will not uninstall on vista
so when you install office 2003 install a new copy do not upgrade.
Now how to kill this process FindFast
1. (open up the task manager) Press Ctrl , Alt , Del buttons
simultaneosly.
2. Select Start Task Manager
3. Select the processes tab
4. Select findfast process scroll down, it should be using 50% of CPU
processing!
5. End Process
6. And office setup progress bar magically comes to life!
Just as well im an old UNIX programmer! Thank god microsoft created a
separate process
and not one giant setup EXE! eh?
I hope that helps because I'm probably the only one who has got around
this problem..
Mike