VintageBigBlue.org

 

Re: PHD2 crash with Gemini Telescope.Net


Apr 22, 2017

 


----------------------------

#59105 Apr 22, 2017

Colleagues....I am running PHD2 on Windows 10. ��When I try and connect to my G11 using the Gemini Telescope.Net driver, PHD2 crashes almost immediately. ��The Computer appears to connect to the mount but by that time PHD2 has crashed and closed. ��Any suggestions?



----------------------------

#59106 Apr 22, 2017

There are many versions now of these programs, and new ones are "improved" but may have introduced a new bug.

I'd suggest you try known "stable" versions or ... if those are the ones failing... the newest versions.

You must also run most of these as "administrator"...try that too.

And... you can tell Windows to run programs as though they were for Win7. .you may try that too!

Good luck,Michael



----------------------------

#59107 Apr 22, 2017

You should see if you can find what causes the PHD2 crash. See if there is logging or tracing that can be turned on that might point to what's causing it. Ask for help from the PHD team -- I'm sure they'll be willing to help you troubleshoot the crash or at least point you in the right direction.

Regards,

�� ��-Paul



----------------------------

#59108 Apr 22, 2017

Logging is automatic in PHD2.

See Documentation at

openphdguiding.org/manual/?section=Tools.htm#Logging_and_Debug_Output



You can post the logs on the PHD2 Google Group atgroups.google.com/forum/#!forum/open-phd-guiding





Bryan

---In Losmandy_users@yahoogroups.com, yh@...> wrote :

You should see if you can find what causes the PHD2 crash. See if there is logging or tracing that can be turned on that might point to what's causing it. Ask for help from the PHD team -- I'm sure they'll be willing to help you troubleshoot the crash or at least point you in the right direction.

Regards,

�� ��-Paul



----------------------------

#59109 Apr 22, 2017

Don't know what is the issue but I'm running same setup and it works fine. You might double-check you have latest version of Gemini ascom driver and ascom is all up to date��

B



----------------------------

#59110 Apr 23, 2017

tuckerjoey,

I'm running my Gemini-2 mini on the latest firmware for the box and hand controller along with:ASCOM 6.3��Gemini.NET 1.0.70.0��PHD2 2.6.3��

Stellarium win64 15.2Stellarium-Scope dated 2016.12.26

And the latest releases of BYEOS, SGP, PoleMaster, QHYCCD camera drivers etc. all is working normally.

Chip



----------------------------

#59111 Apr 24, 2017

Try running everything as an Administrator



----------------------------

#59112 Apr 25, 2017

How does one run an app as an administrator? Thanks.



----------------------------

#59113 Apr 25, 2017

If in Windows, use your mouse to "right-click" the icon.The menu will have a drop down for "Run as Administrator"... give that a try!

- Michael



----------------------------

#59114 Apr 25, 2017

Thank you!



----------------------------

#59115 Apr 26, 2017

If running it as administrator works... right clicking on the desktop icon, opening 'properties' and selecting the compatibility tab provides a way to make this change permanent. The only persistent annoyance is that you will be asked on program startup if it is ok to have the program run with privileges. Problem is, under the current 'security' model administrative privileges are normal for anything that talks to other programs.

greg latiak



----------------------------

#59116 Apr 26, 2017

Actually the best way to set this up is find the exe file in the C:/ProgramFiles directory.�� Then right click it and under the Compatibility tab, check the Run as Administrator radio button.



----------------------------

#59117 Apr 26, 2017

In general you shouldn.t need to run as Admin, (unless you are connecting to another program that IS running with Admin authority).



Dave



----------------------------

#59133 Apr 28, 2017

My experience with these problems on Win 10 and Win 7 is that administrative privileges are required across the board -- at the program level. So either right clicking and 'run as administrator' or set compatibility properties to run as admin. Seems stupid, I know, but even though Windows emulates the granular control of older and more sophisticated OS like VMS, it has been crudely implemented and even more poorly documented. I used to do a lot of work in this area and find Windows security exasperating. It seems anything that does program to program communication needs to run privileged.

greg latiakavalon observatory



----------------------------

#59134 Apr 28, 2017

I.ll repeat what I said earlier, if you run one program with Admin privilege (for whatever reason), then other programs that want to communicate with it must also run with Admin rights. Ideally find out why the first program needed admin rights and fix things so it doesn.t (may need help form supplier). Normally this can the fixed readily, but once one application needs Admin authority, all that talk to it also do.







Dave







From: Losmandy_users@yahoogroups.com [mailto:Losmandy_users@yahoogroups.com]

Sent: 28 April 2017 14:28

To: Losmandy_users@yahoogroups.com

Subject: [Losmandy_users] Re: PHD2 crash with Gemini Telescope.Net











My experience with these problems on Win 10 and Win 7 is that administrative privileges are required across the board -- at the program level. So either right clicking and 'run as administrator' or set compatibility properties to run as admin. Seems stupid, I know, but even though Windows emulates the granular control of older and more sophisticated OS like VMS, it has been crudely implemented and even more poorly documented. I used to do a lot of work in this area and find Windows security exasperating. It seems anything that does program to program communication needs to run privileged.







greg latiak



avalon observatory





















[Non-text portions of this message have been removed]







----------------------------

#59135 Apr 28, 2017

Greg, you don't need to run Gemini.NET 'as administrator'. ��There is also no requirement for ASCOM inter-process protocols to have escalated privileges.

If you're using some old or poorly developed software that for some reason requires privilege escalation, then you might wind up having to run most of the other software that communicates with it this way. This is certainly not a recommended way to run, if you can avoid it.

Regards,

�� �� -Paul



Contact Us
This Site's Privacy Policy
Google's privacy policies

S
e
n
i
o
r
T
u
b
e
.
o
r
g