file association issue

[toddsilva]

Hello,

I am running Win2KPro, SP4, with all current WinUpdates.
I started to see an error when I would double click on a
file to open it, getting this error message:

Cannot find the file {filename}(or one of its components).
Make sure the path and filename are correct and that all
required libraries are available.

My system was fine for two years, this starting happening
about a month ago. I can open most files by double
clicking in Win Explorer, but these are a few that I
cannot: Doc, XLS, GIF, HTM, HTML, PPP (a non-MS
product). Here is specifically what happens: When I
double click the file, the assoc program opens but not the
file, and the above error message appears. However, once
the program is open, I can double click the file once
again and it opens in the program just fine. I am
increasingly confident that this is a file type or file
assocation issue.

I wanted to install new drives and so decided to start
over and re-install Win2K from scratch. I have just done
this, have a brand new system, SP4, all critical updates,
and still have this issue.

Please advise your thoughts on what this is related to.

Thank you.

 

[jasonr@christech]

When that box opens again.Find the program that opens the file.Select
it,then below the program selction window tick the little box "always open
with this program" .
This happens somtimes when a program that used to open those files has been
uninstalled.Therefore it is saying "I used to open this file with this
program but now the program is gone" What do I open it with now?

Good Luck!
J
--
Christech Company
"Quality computer repair on the go"!
http://www.christechcompany.com/
ICQ# 346-151-457
YIM:Christechmemphis
REMOVE NOSPAM FROM EMAIL IF
SENDING A EMAIL TO THIS ADDRESS

 

[toddsilva]

J,

Thanks for your response. I fully understand your
instruction, tried it, and still get the same error. This
is a very odd one, indeed.

Any further suggestions?

Todd

 

[toddsilva]

Jason,

Here's an update for you. I finally recalled when this
issue starting occuring, just after a video driver
update. So I rolled back to an earlier version and have
corrected this issue. Very strange, I would not have
thought to associate this issue with a video driver. I
would like your further comments as to your thoughts on
how these two are related. But for now, I'm back up and
running and in good shape.

Todd