G
George Hester
http://support.microsoft.com/default.aspx?scid=kb;en-us;827729
Can someone please explain to me why, "some third-party programs [that] do not use the registry correctly" has anything to do with this issue? I don't get it. As far as I know if a file type is registered correctly (say gif) then the default data entry for that extension will determine where the open key resides. In a default installation of Windows 2000 anyway the default data will be giffile. So as long as the open key in giffile is correct there is no issue.
Now I know that some "third-party programs" will change this data entry. Say Adobe Photoshop. It will change it to say Adobe.Image. But then Picture Manager ought to do the same thing and set the location in HKCR appropriately. If it doesn't then the symptom of this article will result. And that has nothing to do with "some third-party programs [that] do not use the registry correctly."
Unless of course due to the Windows Installer which can detect the application has broken due to a change in the file association. But then that is an issue with Windows Installer NOT "some third-party programs [that] do not use the registry correctly."
Thanks.
Can someone please explain to me why, "some third-party programs [that] do not use the registry correctly" has anything to do with this issue? I don't get it. As far as I know if a file type is registered correctly (say gif) then the default data entry for that extension will determine where the open key resides. In a default installation of Windows 2000 anyway the default data will be giffile. So as long as the open key in giffile is correct there is no issue.
Now I know that some "third-party programs" will change this data entry. Say Adobe Photoshop. It will change it to say Adobe.Image. But then Picture Manager ought to do the same thing and set the location in HKCR appropriately. If it doesn't then the symptom of this article will result. And that has nothing to do with "some third-party programs [that] do not use the registry correctly."
Unless of course due to the Windows Installer which can detect the application has broken due to a change in the file association. But then that is an issue with Windows Installer NOT "some third-party programs [that] do not use the registry correctly."
Thanks.