PixInsight 1.6.9 Now Available

[Juan Conejero]

Forgot to say, that the other solution is using KDE instead of GNOME. Integration of PixInsight with the latest versions of KDE is perfect and everything works like a dream on this desktop under FreeBSD and Linux, especially if you have hardware acceleration (OpenGL) enabled in your video driver and a compositing manager installed and running on your X11 server.

[Juan Conejero]

Had a go with SCNR , its broken    It adds to the green  

I bet this was only done to test the Automatic Download procedure  

  Haha, I realize this seems to be what you suggest, but no ...  

[Carlos Milovic]

This is odd... I'm using KDE on Fedora 14. PI refuses to select the platform gui style. It just never gets checked, and no changes are applied.

EDIT: The same happens at work and at home.

[astropixel]

The only solution for now, if you want all the icons back, is selecting Window > GUI Style > Plastique. However, by doing so you loose GNOME integration.

No inconvenience, Juan  It doesn't really matter. Interestingly, selecting Plastique has no effect on the menu icons. Furthermore, and I could be imagining it, but the multiplatform dialogues were not present with the core version installed - in-fact the interface was very ugly. Once the PCL package was installed, voila, the multiplatform dialogues showed up and the GNOME dialogues look normal.

Was there an update that would account for the improvement in appearance aside from the PCL package - which was an intuitive approach, because I was using PCL in 1.6.1 and appearance was nice and tight.

[DaveS]

Forgive my ignorance, but now that I've downloaded from:

http://pixinsight.com/download/PCL/PCL-01.00.91.0338-20101220.tar.gz

What do I do with it, as my PC doesn't recognise the tar.gz file type 

From what I have read in this 'thread', it would appear that I have to uninstall my current version of PI, install the new version, uninstall it, then install it again 

All right if you are familiar with PI upgrades, but very confusing if you are not 

Dave

[Carlos Milovic]

Hi Dave
The PCL file is for developers only. You should download the installable file from the sofware distribution system (throught the main page).

BTW, tar.gz is a compressed archive... winrar or winzip should open it.

[DaveS]

Thanks Carlos, that makes sense now 

BTW, I have both Winzip and Winrar, but the download didn't acknowledge that, and wanted to search the internet for a suitable application  .

Not to worry, as it irrelevant now, and I'll go to the Pliedes website and download from there.

Is the 'double install' ritual still necessary?

Dave

[DaveS]

Now I reallly am confused   

I went to the 'main site', then to the 'software distribution' page, entered my 'user name' and 'user ID', attempted to 'log in', and was greeted by 'ACCESS DENIED' 

Dave

[Carlos Milovic]

It is not the user id, it is the password.

[DaveS]

Sorry, my fault Carlos 

Its late, and I'm tired, so not thinking straight. Well that's my excuse anyway 

Ok, software downloaded and installed, but two downloaded 'updates' (documenation and bug-fix) fail to install.

Original version of PI uninstalled. New version installed and uninstalled three times, including PC restart, but although the installation of the core application works fine, the two 'updates' fail to install.

I am now giving up and going to bed!!.

Dave

[rfurman]

I'm getting an update error like Federico after PI x64 or x32 restarts on a Win 7 x64 system. The view log below "thinks" the main PI process did not stop. However, if I create a batch file and launch it, "run as administrator", the update process succeeds. Looks like the UAC settings for the updater do not give it permission to access the protected program directories.

For reference of others, here is my batch file for PI x64,

"C:\Users\RoyF\AppData\Local\Temp\PixInsight64-update\updater1\PixInsightUpdater.exe" 8676 "C:\Program Files\PixInsight" "C:\Users\RoyF\AppData\Local\Temp\PixInsight64-update\contents"

You will need to change the path where the PI updater downloaded the update as well as the target and source directories. You can find these directories for your system by clicking "view log" button on the PI error report when PI restarts. The Program ID (PID) that you pick for the batch file does not matter as long as it is not the PID of an unrelated running process!

--Roy

2010-12-24 00:03:07: Begin updater1
2010-12-24 00:03:07: *******************************************************************************
2010-12-24 00:03:07: This is PixInsight updater stage one program version 01.00.07
2010-12-24 00:03:07: updater1 invocation arguments:
2010-12-24 00:03:07: core application PID : 6800
2010-12-24 00:03:07: target directory     : C:/Program Files/PixInsight
2010-12-24 00:03:07: source directory     : C:/Users/RoyF/AppData/Local/Temp/PixInsight64-update/contents
2010-12-24 00:03:07: *******************************************************************************
2010-12-24 00:03:07: Waiting for the PixInsight Core application to terminate.
2010-12-24 00:04:07: *** Error: Maximum wait time elapsed (60 seconds) - aborting.
2010-12-24 00:04:07: End updater1: ERROR

[Juan Conejero]

OK this time BUT with these notes:
1) If the user is different from Administrator, but with administrator rights, the installer presents a popup asking for the correct user that will perform the upgrade; deselect the chekbox about "prevent unauthorized operations"
2) unchecked the box about automatic PixInsight restart after upgrade (for this last i'm not sure).

1) and 2) are unrelated. Windows XP does not support UAC (User Account Control), which was introduced in Windows Vista. On XP, you must either allow the kind of "unathorized operations" that PixInsight Updater requires to work, or select a user with administrative privileges from the list, then enter his/her password. This is not a problem with the way PixInsight Updater works; this is just Windows XP's own concept of "security".

On Windows Vista and Windows 7, UAC control understands code signatures and informs you that the PixInsight Updater application has been signed by Pleiades Astrophoto S.L. with a VeriSign code signing certificate. This certainly can provide a higher level of confidence to the user.

[Juan Conejero]

Hi Roy,

Welcome to PixInsight Forum.

2010-12-24 00:03:07: Waiting for the PixInsight Core application to terminate.
2010-12-24 00:04:07: *** Error: Maximum wait time elapsed (60 seconds) - aborting.

This should never happen —could never happen, in theory, unless PixInsight Core hangs—, and so far does not happen on any Windows machine we have tested PixInsight 1.6.9 on. If this can be confirmed as a usual behavior on Windows 7, then we have a serious problem.

Anybody else can confirm this?

Trying to diagnose what's happening, could it be some running antivirus/firewall application that is interfering normal operation of the PixInsight Updater application? Could you please try disabling your antivirus software —after disconnecting your computer from the Internet, of course— to see if this makes any difference?

Thank you.

[Harry page]

Hi

I do not know if this is related but when I close pixinsight and restart it if I do not allow say 20 sec between vista 64 thinks I still have the first running and starts a second version , caused me a few problems when I first tried updating 


regards Harry

[Juan Conejero]

Harry,

Could you please try to disable your antivirus/firewall software and check if these problems get fixed?

See for instance similar problems with Firefox:
http://kb.mozillazine.org/Firefox_hangs#Hang_at_exit