Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
I have just downloaded the latest trial version 3.1 as users of my products (ascom focusers) are having issues with backyard eos.
I am running windows 10 64bit, my account has admin priviledges.
First time, when trying to run BackyardEOS, it comes with error messages about not being able to access D:\Pictures\BackyardTemp and exits
So I created that folder. Then it has same issue with permission for Pictures\BackyardTemp\Logs and exists. So I created that folder.
Then it runs. I access the ASCOM focuser dialog box, enable trace and guess what - Backyard EOS again generates an exception error about not being able to access Documents\ASCOM\xxxx where the trace logs are. Running as admin makes not difference. It will only work if I disable the trace on the ascom dialogbox (by using a different application first). I have tried removing and reinstalling etc as admin, still the same.
It appears the application is not running as my login account and thus has not access permissions to my folders. This is just crazy. Trying to change compatibility settings and as admin has zero effect - in other words the same errors persist.
I can run any other application without issue, Nebulosity, MaximDL, StarryNight, APT, FocusMax can all access the ASCOM focuser without issue and write to the trace log. Only Backyard EOS fails.
Any insights appreciated.
Link to comment
Share on other sites
6 answers to this question
This topic is now archived and is closed to further replies.