Re: [skychart-discussion] ASCOM Control Panel error
Yes I saw it, CdC is generating this message before the Chooser is
called. It's a while since I looked at the CdC sources but my guess is
that it's using some ASCOM component that's 32 bit only - such as
Helper.dll. This is throwing an exception and CdC is deciding that it's
an ASCOM problem. It needs to use the ASCOM Utilities components, they
are 32 or 64 bits.
On 28/02/2012 13:57, Joseph Shuster wrote:
> Thanks. I created a short, unnarrated screen capture video to demonstrate
> the problem. You can see it at
> (I use the free version of Jing -- a product I recommend a lot.)
> The problem happens exactly when I click on "Select" so I never see the
> Chooser list to pick a telescope.
> Like I said, this isn't a pressing problem for me. I was just plinking
> around with telescope connection on my Win7 desktop that never really has a
> telescope attached. So my personal urgency is low. But if there's any need
> for more analysis help, I can include the ASCOM Diagnostics log, or other
> screen video/pictures.
> I did just confirm that using ASCOM Diagnostics I can carry on a normal
> dialogue with all the base telescope drivers. So my ASCOM 6 SP1 RC2
> implementation seems solid.
> On Mon, Feb 27, 2012 at 3:20 PM, Chris Rowland<
> chris_group_mail@...> wrote:
>> The chooser in Platform 6 will work with 64 bit applications. It shows
>> the list of drivers as usual. If the driver you select can work with a
>> 64 bit application you can connect to it in the usual way. If the
>> driver can't work with a 64 bit application then the chooser will detect
>> this and show a message saying so and why. The message is intended to
>> help people report the problem and encourage developers to move to
>> drivers that can work with both 32 and 64 bit applications.
>> It's not clear why CdC is showing an error message; maybe CdC is trying
>> to use a legacy part of ASCOM that's 32 bits only.
>> I put some notes about this when I first found it that may help.
>> Let me know if I can help.
>> On 26/02/2012 23:32, Joseph Shuster wrote:
>>> Thanks for the quick response Patrick.
>>> I'm fine using my current version of CdC. The error problem is on my
>>> desktop computer and I don't connect that to my (real) telescope. I found
>>> the problem only because I was curious how the latest ASCOM (6RC1) works
>>> with the latest CdC.
>>> The netbook I use for "real astoronomy" with the telescope is a 32-bit NT
>>> system, so the problem doesn't happen there.
>>> On Sun, Feb 26, 2012 at 9:57 AM, Patrick Chevalley<pch@...> wrote:
>>>> Hi Joe,
>>>> Thank you for your report and the video that is very useful. It may be
>>>> interesting if you give some information here on how you do it.
>>>> Unfortunately this problem is well know, it is one of the problem that
>>>> prevent the release of a Win64 version. Win64 version is only available
>>>> the beta download page for people that want it for testing.
>>>> This page list the other issues with Win64:
>>>> Using POTH is the only reliable way at the moment. In previous version I
>>>> locked the Select button. Now it try to work and give this message if
>>>> something go wrong, this allow for testing when a new ASCOM version is
>>>> If you need a reliable version to work at the telescope please install
>>>> Win32 version. It work very well with no limitation on a Windows 64
- Hi Chris,
CdC use ASCOM.Utilities.Chooser for some time now and the object creation work on Win64 with ASCOM 6.
If this fail, it fall back to DriverHelper.Chooser for people that still use ASCOM 5 or 4, and this part work correctly.
The current exception is when using the chooser, assigning DeviceType="Telescope" or try to open it with the Choose function.
The error code is 217, this usually meant that the exception handling environment is not initialized.
- Hi Patrick,
I'll download the 64 bit version and give it a go some time; if I can
see it for myself I may be ably to provide help instead of guessing. I
may also have a look at the sources. I won't be instant, life is pretty
busy at present.
On 01/03/2012 07:04, Patrick Chevalley wrote:
> Hi Chris,
> CdC use ASCOM.Utilities.Chooser for some time now and the object creation work on Win64 with ASCOM 6.
> If this fail, it fall back to DriverHelper.Chooser for people that still use ASCOM 5 or 4, and this part work correctly.
> The current exception is when using the chooser, assigning DeviceType="Telescope" or try to open it with the Choose function.
> The error code is 217, this usually meant that the exception handling environment is not initialized.