Hi folks,

Juan beat me to it: you uninstall Guide by deleting the Guide
directory. (Something I will add to the FAQ.) Guide does nothing
to the Windows registry and installs no files outside its own
directory. (This has probably saved me and Guide users all
sorts of grief over the years!)

About ACL: no, at present, Guide has no support for that.
(When it does, it will almost certainly be through the wonders
of ASCOM drivers.) Sometimes, you can evade such troubles
by setting the mount into an LX-200 or Celestron or some other
mode, but I just checked the site for your scope, and it makes
no reference to any compatibility with anything except ACL.

Lawrence, two things can cause trouble for asteroid positions
in Guide. One is where you're using Guide's "built-in" orbital
elements for an object that was, say, observed for a few
weeks ten years ago. Guide's elements were compiled about
a year ago, and obviously don't include subsequent observations.
Click on "more info" for the asteroid and check out the arc
of observations.

You can duck around this by using 'mpcorb.dat'. That brings
us to the second problem: MPC elements are updated at 200
day intervals. Right now, we're almost exactly between epochs,
meaning that up to 100 days of perturbations are being ignored.
Not normally a big source of grief, but NEOs tend to be perturbed
more than most. As Bob Elliott mentioned, one way around this
is use of a little program I wrote not long ago:

http://www.gwi.net/~pluto/integrat.htm

By the way, Bob, Guide does include parallax (a _very_ major
effect for "close-in" objects such as, most noticeably, the Moon
and artificial satellites!) In some cases, where the asteroid is
coming almost right at us or directly away from us, its apparent
motion across the sky is so small that the slight wobble caused
by our rotation becomes apparent: click on that object, make
a trail at hourly intervals, and it makes a sine wave with a period
of about one day.

(And if the trail forms a spiral, prepare for the End of the World;
the object will probably hit us!)

-- Bill