0

[This is from the Ascom-Talk group]:

I'm running Windows XP on my Obs computer. Last night, I couldn't connect to the scope for some strange reason and on further investigation the problem seems to be with the ASCOM Chooser. When I am running Version 5.0b, everything works fine, but when I update to 5.5.1 - the chooser comes up with an exception message - it won't let me select anything Telescope/Focusers, it just has an exception message. I have cleared the registry, carried out lots of uninstalls and reinstalls - the problem persists. I have uploaded a Diagnostics log and a screen print of the error it is showing in Profile Explorer (in the folder 'Barry Morton') At first I thought it might be something to do with the new Gemini 1.0.6 Driver, but I don't get that far - before I have installed the driver, I am having the chooser problems. Any help would be much appriciated. Thanks in advance.

Regards,

Barry Morton Worcester - UK

flag

2 Answers

0

The Problem

According to the screenshots, and corroborated by the Diagnostics Log, Profile.xml appears to be the problem. The log shows that it is full of nothing (seriously). And because of that, nothing is registered with the chooser. The exception was thrown because the file is full of nothing.

The Solution

The path to the files is: "D:\Documents and Settings\All Users\Application Data\ASCOM\Profile\Chooser\" In Windows Explorer, delete Profile.xml, then copy ProfileOriginal.xml and change its name to Profile.xml. Make doubly sure that you are in the correct folder.

link|flag
0

Delete the Chooser entry from Profile Explorer, then uninstall/reinstall 5.5.1

Hat tip to Paul Kavensky.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.