Hi Ray,

Sounds as if you probably have the previous alignment data hanging
around. When you start up scope control, you specify which type of
scope you have; that's saved with the alignment data. Guide thought
you were adding, not your first alignment star, but your Nth
alignment star. That probably also led to confusion as to which
end was up, since the previous data had no good reason to correlate
with the new.

To get around this, at the beginning of each session, delete the
'align.dat' file from the previous session.

Guide really isn't set up to handle the concept of negative
encoder resolutions. I don't think it will make any difference as
far as the program's math is concerned, because it relies on two
alignment stars anyway to determine which way is which; the sign
you enter would just be ignored. It _will_ confuse the encoder
hardware, though, because Guide will attempt to tell it that one
or both axes have a negative number of encoder steps. I doubt that
most encoders are rigged up to handle such a concept. Anyway, I
can't see any reason it would help, and can see some that would
cause further grief.

-- Bill