Opening a file problem

d'Hude

Member
I have PI installed and working well. However, when I double click on a file to open PI, my windows machine tries to install PI. I will add 5 screen shots which pop up. This path fails to open PI. However, when I open the PU thru the exe file, alls well. I then open the file from inside PI and it opens as normal.
What’s up? I have associate the file type with PI and the purple 3D cube is associated with the file I am opening to work on.
 

Attachments

  • 096A03E2-E52B-4E51-9A07-68D5CE2EA759.jpeg
    096A03E2-E52B-4E51-9A07-68D5CE2EA759.jpeg
    21.5 KB · Views: 44
  • E3CAC786-9376-43F9-8D71-6E7F0FD4ED53.jpeg
    E3CAC786-9376-43F9-8D71-6E7F0FD4ED53.jpeg
    18.3 KB · Views: 40
  • F5CEDD9F-4BAF-4BF4-8315-7C1EFBFEF2C1.jpeg
    F5CEDD9F-4BAF-4BF4-8315-7C1EFBFEF2C1.jpeg
    23 KB · Views: 41
  • 881BAF3A-0871-4AEF-8DB8-3B0374DE09CE.jpeg
    881BAF3A-0871-4AEF-8DB8-3B0374DE09CE.jpeg
    21.9 KB · Views: 47
  • EFB34F9B-9159-4BDB-8B3F-5606312F7553.jpeg
    EFB34F9B-9159-4BDB-8B3F-5606312F7553.jpeg
    25.9 KB · Views: 40
a problem like this was reported against 1.8.8-3, but it was fixed with -4. what version of PI are you using?
 
Here are better screen shots. Sorry for earlier ones. PI is already fully installed and operational. When I open same file (Open a Copy) from inside PI, all works fine. Not the image.
 

Attachments

  • 702B2C5E-3B38-4731-8622-0540CB50CE7A.jpeg
    702B2C5E-3B38-4731-8622-0540CB50CE7A.jpeg
    288.4 KB · Views: 44
  • 9157D9BA-FC11-4F05-8E0E-9D1E2DC23FCB.jpeg
    9157D9BA-FC11-4F05-8E0E-9D1E2DC23FCB.jpeg
    327.1 KB · Views: 41
  • 6EBDF22B-0B53-46D8-B59C-84D8026C7C19.jpeg
    6EBDF22B-0B53-46D8-B59C-84D8026C7C19.jpeg
    309 KB · Views: 41
  • F0BEA362-D65C-4A27-95BB-70CFE5125294.jpeg
    F0BEA362-D65C-4A27-95BB-70CFE5125294.jpeg
    300 KB · Views: 45
juan would have to comment, but this is the kind of stuff that windows pulls from time to time. undoubtedly there's some obscure registry entry that's either associating the files incorrectly with the installer or is otherwise not set properly.

there are probably many articles on the web talking about fixing windows file associations... it might be worth looking into that and seeing if it can be resolved.
 
This is a machine-specific, Windows-specific issue that cannot be reproduced under normal working conditions with the current 1.8.8-5 version of PixInsight. As Rob has pointed out, we had a similar issue after an update to the core application in version 1.8.8-3, but we solved it with a new installation package.

Something is probably wrong or damaged in your Windows registry. These are typical Windows problems. At the risk of stating the obvious:

- Uninstall PixInsight
- Reboot your machine
- Install PixInsight

If the above doesn't work, then your registry issue is more serious and we cannot offer support in such case.
 
Back
Top